public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/28437] [4.2 Regression] multiple fno-builtin-* flags broken Date: Mon, 24 Jul 2006 22:14:00 -0000 [thread overview] Message-ID: <20060724221357.23773.qmail@sourceware.org> (raw) In-Reply-To: <bug-28437-11334@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from steven at gcc dot gnu dot org 2006-07-24 22:13 ------- Created an attachment (id=11932) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11932&action=view) Don't prune options that can be "Joined" Seems to me like pruning Joined options is always wrong. But, HJ, since you're more into this option stuff and you caused the bug, I suppose you can tell whether my patch makes sense... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28437
next prev parent reply other threads:[~2006-07-24 22:14 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-19 15:21 [Bug c/28437] New: " mike at codeweavers dot com 2006-07-19 15:31 ` [Bug c/28437] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-07-20 22:29 ` pinskia at gcc dot gnu dot org 2006-07-24 5:46 ` steven at gcc dot gnu dot org 2006-07-24 5:55 ` [Bug driver/28437] " pinskia at gcc dot gnu dot org 2006-07-24 5:56 ` pinskia at gcc dot gnu dot org 2006-07-24 15:42 ` hjl at lucon dot org 2006-07-24 20:52 ` steven at gcc dot gnu dot org 2006-07-24 21:46 ` steven at gcc dot gnu dot org 2006-07-24 21:47 ` [Bug driver/28437] [4.2 " steven at gcc dot gnu dot org 2006-07-24 21:51 ` steven at gcc dot gnu dot org 2006-07-24 22:14 ` steven at gcc dot gnu dot org [this message] 2006-07-24 22:15 ` pinskia at gcc dot gnu dot org 2006-07-25 0:36 ` hjl at lucon dot org 2006-07-27 21:27 ` hjl at gcc dot gnu dot org 2006-07-31 23:32 ` mmitchel at gcc dot gnu dot org 2006-07-31 23:33 ` pinskia at gcc dot gnu dot org
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=20060724221357.23773.qmail@sourceware.org \ --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: 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).