This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/9958] [x86] Compiling for 'new' target causes a "Segmentation Error" in Libgcc2.c
- From: "marty dot hauff at rmit dot edu dot au" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Aug 2003 10:50:49 -0000
- Subject: [Bug target/9958] [x86] Compiling for 'new' target causes a "Segmentation Error" in Libgcc2.c
- References: <20030305011601.9958.marty.hauff@rmit.edu.au>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9958
------- Additional Comments From marty dot hauff at rmit dot edu dot au 2003-08-24 10:50 -------
Subject: Re: [x86] Compiling for 'new' target causes
a "Segmentation Error" in Libgcc2.c
This is OK to close. I suspect the bug was more a result of yours truly not knowing how to correctly format a MD file. Thanks for your persistence.
I had no idea this was still floating in the system. I'm still getting used to the GCC development community and its processes. It appears that I have been emailed during the process of this bug tracking but I have not realised this amongst the 50-100 odd GCC mailing list emails I get each day. I'll watch more closely next time!
Thanks again.
Marty Moose
>>> "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> 08/24/03 10:26 AM >>>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9958
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |INVALID
------- Additional Comments From pinskia at gcc dot gnu dot org 2003-08-24 00:26 -------
No feedback in 3 months (T+9 - T-6 days depending on which question you count).
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.