Full Disclosure mailing list archives
RE: gcc: Internal compiler error: program cc1 g ot fatal signal 11
From: John.Airey () rnib org uk
Date: Fri, 9 Jan 2004 16:13:26 -0000
-----Original Message----- From: Kurt Schreiner [mailto:ks () ub uni-mainz de] Sent: 09 January 2004 08:43 To: Valdis.Kletnieks () vt edu Cc: guninski () guninski com; full-disclosure () lists netsys com Subject: Re: [Full-disclosure] gcc: Internal compiler error: program cc1 got fatal signal 11 Hi,3) This is why it *will* segfault at runtime. If it*fails* to segfault at runtime,you have a *very* weird system indeed (or possibly veryweird compiler flags ;) just tried this on solaris9/sparc:-349: uname -aSunOS sb1001 5.9 Generic_112233-05 sun4u sparc SUNW,Sun-Blade-1000 using:-333: gcc -vReading specs from /opt/nb/gcc-3.3/lib/gcc-lib/sparc-sun-solaris2/3.3/specs Configured with: ./configure --prefix=/opt/nb/gcc-3.3 --host=sparc-sun-solaris2 --enable-languages=c,c++,f77,objc,ada --enable-shared Thread model: posix gcc version 3.3-339: cat gcc-muell.cint main(void) { printf("%c","msux"[0xcafebabe]); }-340: gcc gcc-muell.c[Compiles w/o compaints!]
Guys, this is getting to be a peeing contest. Can anyone confirm that the gcc maintainers are aware of this, and are they able to make a statement as to which compilers need their optimisation code sorted? I mean, if we did this kind of gross dissection of every bug, we'd be deleting messages all day and not doing any work. Full-disclosure doesn't mean full-boredom! To be specific: 1. Feel free to report a bug 2. Wait for a fix or provide one yourself. 3. Go back to 1 if 2 doesn't fix it. Thank you. - John Airey, BSc (Jt Hons), CNA, RHCE Internet systems support officer, ITCSD, Royal National Institute of the Blind, Bakewell Road, Peterborough PE2 6XU, Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 John.Airey () rnib org uk Even if you win the rat race, that will still only make you a rat. - DISCLAIMER: NOTICE: The information contained in this email and any attachments is confidential and may be privileged. If you are not the intended recipient you should not use, disclose, distribute or copy any of the content of it or of any attachment; you are requested to notify the sender immediately of your receipt of the email and then to delete it and any attachments from your system. RNIB endeavours to ensure that emails and any attachments generated by its staff are free from viruses or other contaminants. However, it cannot accept any responsibility for any such which are transmitted. We therefore recommend you scan all attachments. Please note that the statements and views expressed in this email and any attachments are those of the author and do not necessarily represent those of RNIB. RNIB Registered Charity Number: 226227 Website: http://www.rnib.org.uk _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- RE: gcc: Internal compiler error: program cc1 g ot fatal signal 11 John . Airey (Jan 09)
- <Possible follow-ups>
- RE: gcc: Internal compiler error: program cc1 g ot fatal signal 11 John . Airey (Jan 09)
- Re: gcc: Internal compiler error: program cc1 g ot fatal signal 11 Valdis . Kletnieks (Jan 09)
- Re: gcc: Internal compiler error: program cc1 g ot fatal signal 11 Jedi/Sector One (Jan 09)
- Re: gcc: Internal compiler error: program cc1 g ot fatal signal 11 Valdis . Kletnieks (Jan 09)