public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: thomas@koeller.dyndns.org To: gcc-gnats@gcc.gnu.org Subject: other/6870: ld built using gcc-3.1 crashes Date: Thu, 30 May 2002 09:26:00 -0000 [thread overview] Message-ID: <20020530154854.28856.qmail@sources.redhat.com> (raw) >Number: 6870 >Category: other >Synopsis: ld built using gcc-3.1 crashes >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu May 30 08:56:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Thomas Koeller >Release: 3.1 >Organization: >Environment: cygwin under WinXP >Description: When I build binutils-2.12 or binutils-2.12.1 using gcc-3.1 on a cygwin system running on WinXP, the resulting ld.exe executable crashes immediatly upon invocation, even if invoked as 'ld --help' or without any arguments at all. I used '-pipe -O3 -march=i686 -fomit-frame-pointer' to build. When building with gcc-3.0.4 using the same options, the problem does not occur. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-30 15:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-30 9:26 thomas [this message] 2003-03-25 2:20 bangerth
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=20020530154854.28856.qmail@sources.redhat.com \ --to=thomas@koeller.dyndns.org \ --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).