public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45754] Driver core dump when duplicating -Wall command line option
Date: Wed, 08 Dec 2010 05:57:00 -0000 [thread overview]
Message-ID: <bug-45754-4-kb7dDO5ucC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45754-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45754
Dave Korn <davek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |davek at gcc dot gnu.org
Resolution| |FIXED
--- Comment #3 from Dave Korn <davek at gcc dot gnu.org> 2010-12-08 05:57:07 UTC ---
(In reply to comment #2)
> Subject: Re: Driver core dump when duplicating -Wall
> command line option
>
> Unless this can be reproduced with trunk I'd guess it was fixed by:
>
> 2010-06-09 Dave Korn <dave.korn.cygwin@gmail.com>
>
> * opts-common.c (prune_options): Ensure replacement argv array
> is correctly terminated by a NULL entry.
Yes, I confirmed that the bug is fixed on head. Martin, it is also fixed in
the cygwin gcc-4.5.0-1 test release.
BTW, use 'g++', not 'gcc', when compiling C++, or you will run into link
errors vs. libstdc!
next parent reply other threads:[~2010-12-08 5:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45754-4@http.gcc.gnu.org/bugzilla/>
2010-12-08 5:57 ` davek at gcc dot gnu.org [this message]
2010-09-23 0:21 [Bug driver/45754] New: Driver core dump (when " Martin dot Weitzel at t-online dot de
2010-09-23 9:12 ` [Bug target/45754] Driver core dump when " rguenth at gcc dot gnu dot org
2010-09-23 15:13 ` joseph at codesourcery dot com
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=bug-45754-4-kb7dDO5ucC@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: link
Be 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).