[Bug target/41799] New: __enable_execute_stack introduced for mingw32 in r134089 doesn't work for kernel-mode components

2009-10-22 Thread colin at reactos dot org 
The __enable_execute_stack code introduced for the target "mingw32" in r134089
doesn't work for kernel-mode components. These components can link to libgcc,
but never link to kernel32.
It would be good if there was a way to turn off this code, for example by a
-f/-fno compiler flag.


-- 
   Summary: __enable_execute_stack introduced for mingw32 in r134089
doesn't work for kernel-mode components
   Product: gcc
   Version: 4.5.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
AssignedTo: unassigned at gcc dot gnu dot org
    ReportedBy: colin at reactos dot org
GCC target triplet: mingw32


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41799

[Bug target/41799] __enable_execute_stack introduced for mingw32 in r134089 doesn't work for kernel-mode components

2009-10-24 Thread colin at reactos dot org 


--- Comment #2 from colin at reactos dot org  2009-10-24 18:31 ---
Already said on IRC but for the record: The patch works well and setting
-fno-set-stack-executable fixes the problem for me.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41799

[Bug regression/42145] New: Incorrect "may be used uninitialized warning" for a very specific test case

2009-11-22 Thread colin at reactos dot org 
I'm compiling the attached test case with "gcc version 4.5.0 20091018
(experimental) [trunk revision 152966] (Ubuntu 20091018-0ubuntu1)".
When using the command line "gcc -Wuninitialized -Os -o test test_gccbug.c",
I'm getting the following incorrect warning:

test_gccbug.c: In function 'main':
test_gccbug.c:17:6: warning: 'ret' may be used uninitialized in this function

Same happens with different builds of GCC 4.4.2, 4.4.1 and 4.3.4.
No such warning occurs with builds of GCC 4.2.4 and 4.1.3.

This problem does not occur if one or more of the following is done:
- You change the optimization level to -O0 or -O1 (-O2 and -O3 still trigger
the bug in this GCC 4.5.0 version, but not always in older versions I've
tested)
- You comment out line 10 of the test case
- You change line 22 of the test case to just 'if (!argc)'


-- 
   Summary: Incorrect "may be used uninitialized warning" for a very
specific test case
   Product: gcc
   Version: 4.5.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: regression
    AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: colin at reactos dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42145

[Bug regression/42145] Incorrect "may be used uninitialized warning" for a very specific test case

2009-11-22 Thread colin at reactos dot org 


--- Comment #1 from colin at reactos dot org  2009-11-22 14:43 ---
Created an attachment (id=19084)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19084&action=view)
The test case


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42145

[Bug regression/42145] Incorrect "may be used uninitialized warning" for a very specific test case

2009-11-22 Thread colin at reactos dot org 


--- Comment #2 from colin at reactos dot org  2009-11-22 14:44 ---
Created an attachment (id=19085)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19085&action=view)
The preprocessed test case


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42145