public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/54952] New: Program crash on M32C when stack frame is more then 128 bytes
@ 2012-10-17 14:54 m.galante at centrosistemi dot it
2012-10-18 6:03 ` [Bug target/54952] " dj at redhat dot com
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: m.galante at centrosistemi dot it @ 2012-10-17 14:54 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54952
Bug #: 54952
Summary: Program crash on M32C when stack frame is more then
128 bytes
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: m.galante@centrosistemi.it
Created attachment 28461
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28461
Test case
m32c-elf-gcc (GCC) 4.7.2 hosted on Windows XP.
If I compile and run the attached program with:
m32c-elf-gcc -msim -mcpu=m32c -O1 -DDATASIZE=126 stack.c
m32c-elf-run a.out
it works well. But if I increase DATASIZE to 127:
m32c-elf-gcc -msim -mcpu=m32c -O1 -DDATASIZE=127 stack.c
m32c-elf-run a.out
the program crashes.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/54952] Program crash on M32C when stack frame is more then 128 bytes
2012-10-17 14:54 [Bug c/54952] New: Program crash on M32C when stack frame is more then 128 bytes m.galante at centrosistemi dot it
@ 2012-10-18 6:03 ` dj at redhat dot com
2012-10-18 7:44 ` m.galante at centrosistemi dot it
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: dj at redhat dot com @ 2012-10-18 6:03 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54952
DJ Delorie <dj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dj at redhat dot com
--- Comment #1 from DJ Delorie <dj at redhat dot com> 2012-10-18 06:03:14 UTC ---
FYI this looks like an assembler bug, not a gcc bug... The "add.l #128,sp"
opcode is being assembled as "add.l #-128,sp" instead.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/54952] Program crash on M32C when stack frame is more then 128 bytes
2012-10-17 14:54 [Bug c/54952] New: Program crash on M32C when stack frame is more then 128 bytes m.galante at centrosistemi dot it
2012-10-18 6:03 ` [Bug target/54952] " dj at redhat dot com
@ 2012-10-18 7:44 ` m.galante at centrosistemi dot it
2012-12-09 2:12 ` pinskia at gcc dot gnu.org
2012-12-09 10:54 ` steven at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: m.galante at centrosistemi dot it @ 2012-10-18 7:44 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54952
Michele Galante <m.galante at centrosistemi dot it> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |http://sourceware.org/bugzi
| |lla/show_bug.cgi?id=14739
--- Comment #2 from Michele Galante <m.galante at centrosistemi dot it> 2012-10-18 07:44:28 UTC ---
(In reply to comment #1)
> FYI this looks like an assembler bug, not a gcc bug... The "add.l #128,sp"
> opcode is being assembled as "add.l #-128,sp" instead.
Thank you very much.
I just submitted the bug to the binutils Bugzilla (bug 14739).
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/54952] Program crash on M32C when stack frame is more then 128 bytes
2012-10-17 14:54 [Bug c/54952] New: Program crash on M32C when stack frame is more then 128 bytes m.galante at centrosistemi dot it
2012-10-18 6:03 ` [Bug target/54952] " dj at redhat dot com
2012-10-18 7:44 ` m.galante at centrosistemi dot it
@ 2012-12-09 2:12 ` pinskia at gcc dot gnu.org
2012-12-09 10:54 ` steven at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu.org @ 2012-12-09 2:12 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54952
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |normal
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug target/54952] Program crash on M32C when stack frame is more then 128 bytes
2012-10-17 14:54 [Bug c/54952] New: Program crash on M32C when stack frame is more then 128 bytes m.galante at centrosistemi dot it
` (2 preceding siblings ...)
2012-12-09 2:12 ` pinskia at gcc dot gnu.org
@ 2012-12-09 10:54 ` steven at gcc dot gnu.org
3 siblings, 0 replies; 5+ messages in thread
From: steven at gcc dot gnu.org @ 2012-12-09 10:54 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54952
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #3 from Steven Bosscher <steven at gcc dot gnu.org> 2012-12-09 10:54:29 UTC ---
Not a GCC bug -> INVALID
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-12-09 10:54 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-10-17 14:54 [Bug c/54952] New: Program crash on M32C when stack frame is more then 128 bytes m.galante at centrosistemi dot it
2012-10-18 6:03 ` [Bug target/54952] " dj at redhat dot com
2012-10-18 7:44 ` m.galante at centrosistemi dot it
2012-12-09 2:12 ` pinskia at gcc dot gnu.org
2012-12-09 10:54 ` steven at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).