-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update gcc/gdb version #548
base: master
Are you sure you want to change the base?
Conversation
@@ -16,3 +16,6 @@ workspace.code-workspace | |||
*.pro.shared | |||
|
|||
.vscode | |||
*.log | |||
null.d |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is null.d?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's generated by the makefile extension.
https://marketplace.visualstudio.com/items?itemName=ms-vscode.makefile-tools
I can't figure out how to suppress it's generation so it goes into the gitignore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't find any reference to null.d on the help page. It is strange that they choose NUL.D is a reserved filename on msdos / command.com. https://answers.microsoft.com/en-us/windows/forum/all/unable-to-rename-a-folder-to-com-errorthe/ff48c793-ab97-4881-952a-df195321c11c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah. i haven't been able to figure it out. i just know it gets generated when they generate the list of make options. and it's not consistent either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove from PR then, and complain to microsoft :)
I gave it a try now on the same hw. As the last time I tried, the code got larger and slightly slower. For now I would prefer to stay with the old compiler for that reason. It would be great to know what is going on. Compiler : 7.3.1
LBM speed test 3x: ADC interrupt test 3x with motor running: Compiler : 10.3.1
LBM speed test 3x: ADC interrupt test 3x with motor running: |
It would be good to check how the binary size and performance changes with later versions of gcc. Last time I tried the binary would get quite a bit larger and the code got slightly slower. |
looking at the notes on releases since the gcc-arm-none-eabi-7-2018-q2-update release, There is this which could be increasing the memory size. Otherwise the other notes seem nonrelevant. And it's mainly changes to mainline gcc that are getting pulled in. Which would be exploit vulnerability fixes, memory safety improvements, bux fixes and tool improvements. |
Not a candidate for the fw6.0 release. |
We can leave this one open for now and revisit it later. |
Some tools have depreciated the older version of gdb we use and the issue causing #210 on newer versions of gcc have been fixed. So it may be worth upgrading toolchains now.
Tested with vesc 6.0 mk4 in windows. Detecting and running a motor works.
Also successfully tested compilation in wsl linux. Mac not tested.
One things with the newer gcc version is it throws a lot more warnings about casts and implicit conversions.
closes #210