Pelles C forum
Pelles C => Announcements => Topic started by: Pelle on June 29, 2020, 02:23:44 PM
-
Pelles C version 10.00 (Release Candidate #2) is now available for download:
http://www.smorgasbordet.com/pellesc/download.htm
Major changes:
http://www.smorgasbordet.com/pellesc/changes_900_1000.htm
Changes for RC2:
- Added atomic floating-point add/sub/mul/div/exchange for X64 targets (missing atomic floating-point post-increment/decrement may be added in a future version).
- Fixed IDE problem with environment variables when switching a project between 32 bits and 64 bits.
- Fixed compiler problem with missing /arch option check for idiomatic popcount loop, and also added a minor enhancement.
- Fixed compiler problem with call unnesting for intrinsic function argument(s).
- Fixed compiler problem processing atomic post-increment/decrement on small integer type (< int).
- Fixed minor IDE problem with properties for a generic text file.
- Fixed IDE problem with missing ES_MULTILINE for some fields in project Options.
- Fixed problem with path construction when enough parent references (..) took it above the 'root' of the 'current' directory.
/Pelle
-
Thanks again :)
Now Add-In PrjObjPODmp64 should work too.
EDIT:
It shows podump.exe result from an object file in Output window.
-
Pelles C version 10.00 (Release Candidate #2) is now available for download:
http://www.smorgasbordet.com/pellesc/download.htm
Thanks very much for all of your hard work.
John
-
Pelles C version 10.00 (Release Candidate #2) is now available for download:
Thank you very much Pelle!
-
Thank you all!
-
_
|)`
| |
| |____
/ (]__)
/ (]___)
/ (]___)
___(]_)
/
-
_
_| |
_| | |
| | | |
| | | | __
| | | |/ \
| /\ \
| / \/
| \ /\
| \/ /
\ /
| /
| |
-
ˊ ` ` ` ` ` ` ` ` ` ` ` ` ` ` `'F'¯'''''L ` ` ` ` ` ` ` ` ` ` ` `
` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `'[``…'¾`` ``` ``` ``` ```
` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `'[```…ʹ[` ` ` ` ``` ``` ```
` ` ` ` ` ` ` ` ` ` ` ` ` ` ` `#````ˆ[```` ``` ``` ``` ``
` ` ` ` ` ` ` ` ` ` ` ` ` ` `'#``…``'[`… ` ` ` ` ` ` ` ` `
` ` ` ` ` ` ` ` ` ` ` ` ` ` #…`````'F`` ` ` ` `` ``` ```
` ` ` ` ` ` ` ` ` ` ` ` ` ƒ¯```````'[__` ` ` ` ` ` ` ``` ``
` ` ` ` ` ` ` ` ` ` ` ` ƒ¯````````ʹ¯¯¯¯''''''''''''¯¯¯¯¯¯™[ `
gµµµµµµµµµµµµµµ_µ™`````````````````````````'# `
'₫₫₫₫₫₫₫₫₫₫₫₫₫F¯…`````````````````````` ` ²q[¯ ` `
ʹ₫₫₫₫₫₫₫₫₫₫₫₫¾````````````````````````````ʹ} … `
›₫₫₫₫₫₫₫₫₫₫₫₫#`````````````````````````__µr… ` `
³₫₫₫₫₫₫₫₫₫₫₫₫₫…`````````````````````````¯[ … ` `
`₫₫₫₫₫₫₫₫₫₫₫₫$``````````````````````````_F … ` `
`]₫₫₫₫₫₫₫₫₫₫₫#````````````````````````ʹ''''[… … ` `
`'₫₫₫₫₫₫₫F''''']₫#___`````````````````````` '# … ` `
…₫₫₫₫₫₫₫bµ₫₫₫₫$¯''''¹uuuuuɷuɷuɷuɷuɷuɷµ#¯ ` ` ` ` `
…'''''''™''''™'''™''''™™ … … ` ` ` ` ` ` ` ` ` ` ` ` … … ` ` `
` … ` ` ` ` ` ` ` ` … ` … ` ` ` ` ` ` ` ` ` ` ` … ` ` ` ` `.
-
Since everyone is being silly ... ;D
-
Hi,
This is not strictly Version 10 RC2. Both version 9 and version 10 become basically inoperable - when this error is encountered.
When this error "Context_links.h(257): warning #1039: [ISO] No newline at end of file." occurs the IDE hangs. The project status stays in building and 'Project - Stop build' does nothing to recover the normal state. The only way to get out this state is to use the Process Viewer to kill the poide.exe. File - Close Project is disabled, File - Exit does not work, and using the window X does not help. This happens in version 9 as well as version 10 RC2. I think the IDE is in two states simultaneously because one can open edit and save code but nothing else. It is easy to test ....
Regards,
John
-
A small project to test that.
Stop build doesn't work.
-
A small project to test that.
Thanks! I will have a look...
-
Thanks TimoVJL - I should have done that. I will in the future.
Regards,
John Z
-
Hi,
Back on RC1 I mentioned a possible bug using optimizations. V10 was/is giving me different results compared to V9. I have a small portion of code, from a huge program, that either demonstrates the possible bug, or demonstrates I need to be a better programmer (undoubtedly true regardless ;) ).
This program will run 'correctly' using no optimizations, optimize for size, and optimize for size more in V10 RC2. However it will fail to run correctly when using optimize for speed or optimize for speed more in V10 RC2. Using V9.009 it always works with all original code as written and any optimization desired. I have stripped out many, many, lines of code to get a small example for V10.
It 'appears' that a pointer changes. A statement
memset(p_ext,0,49); // clear extension storage is clearing a different pointer space that belonging to p_LineIn.
If I change this one line to clear by writing nothing
swprintf(p_ext,49,L"%s",""); // clear extension storage then the optimizations ALL work and the program runs correctly.
There are other lines of code that can be removed and the result changes as well, but they seem unrelated to clearing p_ext. Also using wmemset has the same issue as memset. If there is a programmer pointer error I've gone blind to it.....
At the top of mainc. there are some instructions on what lines to comment out to try it. When it works correctly two message boxes will show with identical strings and the program will quit. When it fails the second message box is blank, a third box will indicate that it failed.
I will really appreciate any help, or tips, and your time to look this over, hopefully I won't be too embarrassed!
John
-
It's a compiler bug, due to imprecise alias/liveness info. The compiler thinks ext[] and LineIn[] can share stack space, which they can't.
The quick fix is to add
#pragma pack_stack(off)but a proper fix looks much harder. I'm out of ideas at the moment...
-
Thanks Pelle,
I appreciate you taking a look at this and figuring it out.
Saves my sanity looking for where I went wrong :)
I'll implement your suggestion.
Thanks again,
John
-
Good news - this looks to be resolved in RC3. The test program works under all conditions and the original full program operates correctly. Perhaps this : •Fixed compiler problem with aggregate stack interference graph and pointer aliasing. resolved it.
John Z
-
Good news - this looks to be resolved in RC3. The test program works under all conditions and the original full program operates correctly.
Great!
Perhaps this : •Fixed compiler problem with aggregate stack interference graph and pointer aliasing. resolved it.
Yes (I could have stated it less technical, but I wanted to be precise).