Download Pelles C here: http://www.smorgasbordet.com/pellesc/
Quote from: John Z on May 22, 2025, 07:50:59 PMQuote from: Robert on May 22, 2025, 07:27:56 PMHi John:
I'm compiling from command-line and from Pelles 13.00.7 IDE on Windows 24H2 OS Build 26100.4061. No problems.
Do you get Error code: -1073741819 when compiling the Hello example in the IDE ? What and how are you compiling to throw that error ?
John Z
Check this link for details.
https://forum.pellesc.de/index.php?PHPSESSID=v5g18cvn3a2h9saqduujeabqfr&topic=11433.0
QuoteThe COMM directive declares name as a communal symbol with the size of either a type or a constant expression. An optional naming convention may be specified for the name.
Communal symbols will be assigned storage space at link time, unless it has been explicitly defined in a module. The memory space may not be assigned until load time, so using communal symbols may reduce the size of the executable.
Examples:
COMM BuffSize:256
COMM MaxInt:DWORD
COMM Var1:DWORD, Var2:MYSTRUCT
Quote from: Robert on May 22, 2025, 07:27:56 PMHi John:
I'm compiling from command-line and from Pelles 13.00.7 IDE on Windows 24H2 OS Build 26100.4061. No problems.
Do you get Error code: -1073741819 when compiling the Hello example in the IDE ? What and how are you compiling to throw that error ?
Quote from: Pelle on May 22, 2025, 07:01:53 PMHow can it be a bug when it's not even supported?! The download page says nothing about Windows 11 for version 13.
Quote from: John Z on May 22, 2025, 05:30:45 PMYikes!
The version 13 final release shows the Error code: -1073741819 issue!![]()
Stay with RC3 if you are on WIN11 24H2 !!
I thought it was safe because my desktop on RC3 and WIN 11 24H2 ran without issue.
So I upgraded the laptop for Pelle C to WIN11 24H2. Ran V13 final release (which ran fine under win 11 23H2) and immediately get the Error code: -1073741819. Checked Desktop again, ran fine on RC3 Win 11 24H2.
Uninstalled V13 final version completely from the laptop, manually deleted anything left over then
reinstalled RC3 now it runs fine on WIN 11 24H2.
John Z
Quote from: Marco on May 22, 2025, 05:50:16 PMHaving performed several tests, I can confirm that this bug has been fixed! Well done, Pelle!Very good. Thank you!
Quote from: Pelle on May 21, 2025, 02:32:12 PMFixed compiler problem with __declspec(selectany) sometimes placing the immediately following data object(s) in the same (wrong) section. May pass unnoticed, but could trigger an exception if a read/write object was placed in a read-only section (and later written to). Ugh.
Page created in 3.689 seconds with 15 queries.