in this
function warnings when using __builtin_setjmp
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: hackbunny at reactos dot
--- Comment #1 from hackbunny at reactos dot com 2007-04-25 23:28 ---
Created an attachment (id=13442)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13442action=view)
Preprocessor output
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31707
--- Comment #2 from hackbunny at reactos dot com 2007-04-25 23:29 ---
Created an attachment (id=13443)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13443action=view)
GIMPLE source for the test case
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31707
--- Comment #3 from hackbunny at reactos dot com 2007-04-25 23:30 ---
Created an attachment (id=13444)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13444action=view)
Final tree dump for the test case
By going through the tree dump, it appears the warning has no reason
--- Comment #4 from hackbunny at reactos dot com 2007-04-25 23:33 ---
A couple more notes:
* no warning if setjmp is used instead of __builtin_setjmp
* no warning if the call to bar() is removed
* no warning in GCC 4.1.2
--
hackbunny at reactos dot com changed:
What
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: hackbunny at reactos dot com
GCC build triplet: mingw32
GCC host triplet: mingw32
GCC target triplet: mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37981
--- Comment #1 from hackbunny at reactos dot com 2008-10-31 16:24 ---
Created an attachment (id=16598)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16598action=view)
compiler output
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37981
--- Comment #2 from hackbunny at reactos dot com 2008-10-31 16:25 ---
Created an attachment (id=16599)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16599action=view)
preprocessed input
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37981
--- Comment #3 from hackbunny at reactos dot com 2008-10-31 16:31 ---
Created an attachment (id=16600)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16600action=view)
compiler output (PCH disabled)
--
hackbunny at reactos dot com changed:
What|Removed
--- Comment #4 from hackbunny at reactos dot com 2008-10-31 16:34 ---
Created an attachment (id=16601)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16601action=view)
preprocessed input (PCH disabled)
sorry about compression, the file is too big to attach
--
hackbunny
--- Comment #31 from hackbunny at reactos dot com 2008-11-24 04:32 ---
Created an attachment (id=16755)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16755action=view)
testcase.c:10: warning: y renamed after being referenced in assembly
Compile test case with -funit-at-a-time
gcc
--- Comment #32 from hackbunny at reactos dot com 2008-11-24 04:32 ---
I've been told that this is related to the test case I just attached
--
hackbunny at reactos dot com changed:
What|Removed |Added
--- Comment #7 from hackbunny at reactos dot com 2008-11-24 10:24 ---
Created an attachment (id=16756)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16756action=view)
Smaller test case
gcc -c -v -funit-at-a-time -nostdinc testcase.c
Using built-in specs.
Target: mingw32
--- Comment #8 from hackbunny at reactos dot com 2008-11-24 10:29 ---
I have added a test case that shows a closely related issue with nested
functions, -funit-at-a-time and unreferenced file-scope externs (yes, if you
remove int x = 0; the warning goes away)
The %D renamed after being
ReportedBy: hackbunny at reactos dot com
GCC build triplet: mingw32
GCC host triplet: mingw32
GCC target triplet: mingw32
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38269
--- Comment #1 from hackbunny at reactos dot com 2008-11-25 21:56 ---
Created an attachment (id=16770)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16770action=view)
test case (1 of 2)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38269
--- Comment #2 from hackbunny at reactos dot com 2008-11-25 21:56 ---
Created an attachment (id=16771)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16771action=view)
test case (2 of 2)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38269
--- Comment #4 from hackbunny at reactos dot com 2008-11-25 22:12 ---
Yes and no, we are resisting upgrading due to PR 31707 (which we are attempting
to workaround, and the workaround led to this bug...). I will try ASAP anyway
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38269
18 matches
Mail list logo