public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: s.ryll@web.de To: gcc-gnats@gcc.gnu.org Subject: c/4317: main() {return 0;} does not compile correctly Date: Thu, 13 Sep 2001 08:46:00 -0000 [thread overview] Message-ID: <20010913154436.10284.qmail@sourceware.cygnus.com> (raw) >Number: 4317 >Category: c >Synopsis: main() {return 0;} does not compile correctly >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Sep 13 08:46:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Steffen Ryll >Release: GCC 3.0.1 >Organization: >Environment: GCC version: Reading specs from /usr/local/gcc-3.0.1/lib/gcc-lib/i586-pc-linux-gnu/3.0.1/specs Configured with: ../gcc-3.0.1/configure --with-gnu-ld --with-gnu-as --prefix=/usr/local/gcc-3.0.1 Thread model: single gcc version 3.0.1 System environment: i586-pc-linux-gnu >Description: Background: I wondered, why several configure-scripts regarded gcc-3.0.1 as a cross compiler. The attached _simple_ program demonstrates that. It compiles without errors, but at runtime the program exits with a segmentation fault. Somewhat strange... Compiler output: none Preprocessor file: see attachment Options given at GCC compile-time: Configured with: ../gcc-3.0.1/configure --with-gnu-ld --with-gnu-as --prefix=/usr/local/gcc-3.0.1 Built with: make bootstrap >How-To-Repeat: /usr/local/gcc-3.0.1/bin/gcc -o conftest conftest.c >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="conftest.i" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="conftest.i" IyAxICJjb25mdGVzdC5jIgoKIyA4ODkgImNvbmZpZ3VyZSIKCiMgMSAiY29uZmRlZnMuaCIgMQoK IyA4OTAgImNvbmZpZ3VyZSIgMgoKCm1haW4oKXsKcmV0dXJuIDA7Cn0K
next reply other threads:[~2001-09-13 8:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-13 8:46 s.ryll [this message] 2001-09-28 20:52 aoliva 2001-10-02 22:19 aoliva
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20010913154436.10284.qmail@sourceware.cygnus.com \ --to=s.ryll@web.de \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).