public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/47547] [4.5/4.6 Regression] WHOPR, can't use /dev/null as an output file
Date: Tue, 01 Feb 2011 14:42:00 -0000	[thread overview]
Message-ID: <bug-47547-4-PZ8jafbrKD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47547-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47547

--- Comment #5 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> 2011-02-01 14:42:16 UTC ---
Author: hjl
Date: Tue Feb  1 14:42:08 2011
New Revision: 169479

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169479
Log:
Check HOST_BIT_BUCKET when settting dump base/dir.

2011-02-01  H.J. Lu  <hongjiu.lu@intel.com>

    PR driver/47547
    * lto-wrapper.c (run_gcc): Don't add -dumpdir if linker_output
    is HOST_BIT_BUCKET.

    * opts.c (finish_options): Don't add x_aux_base_name if it is
    HOST_BIT_BUCKET.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/lto-wrapper.c
    trunk/gcc/opts.c


  parent reply	other threads:[~2011-02-01 14:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31  5:13 [Bug driver/47547] New: " d.g.gorbachev at gmail dot com
2011-01-31 14:27 ` [Bug driver/47547] " rguenth at gcc dot gnu.org
2011-01-31 15:06 ` hjl.tools at gmail dot com
2011-01-31 17:35 ` hjl.tools at gmail dot com
2011-01-31 17:41 ` hjl.tools at gmail dot com
2011-01-31 20:08 ` [Bug driver/47547] [4.5/4.6 Regression] " hjl.tools at gmail dot com
2011-02-01 14:42 ` hjl at gcc dot gnu.org [this message]
2011-02-01 14:43 ` [Bug driver/47547] [4.5 " hjl.tools at gmail dot com
2011-02-02 18:27 ` dnovillo at gcc dot gnu.org
2011-03-08 13:27 ` rguenth at gcc dot gnu.org
2011-04-10 10:16 ` rguenth at gcc dot gnu.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=bug-47547-4-PZ8jafbrKD@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).