public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/44464] ICE during linux kernel whopr build
Date: Wed, 09 Jun 2010 13:42:00 -0000	[thread overview]
Message-ID: <20100609134205.1596.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44464-7834@http.gcc.gnu.org/bugzilla/>



------- Comment #14 from andi-gcc at firstfloor dot org  2010-06-09 13:42 -------
I found this code in lto.c which seems to disagree:

/* Read the options saved from each file in the command line.  Called
   from lang_hooks.post_options which is called by process_options
   right before all the options are used to initialize the compiler.
   This assumes that decode_options has already run, so the
   num_in_fnames and in_fnames are properly set.

   Note that this assumes that all the files had been compiled with
   the same options, which is not a good assumption.  In general,
   options ought to be read from all the files in the set and merged.
   However, it is still unclear what the merge rules should be.  */

void
lto_read_all_file_options (void)

Still remains to be seen if it DTRT though (e.g. for -pg vs no -pg)


-- 


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


  parent reply	other threads:[~2010-06-09 13:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08  9:05 [Bug lto/44464] New: " andi-gcc at firstfloor dot org
2010-06-08  9:39 ` [Bug lto/44464] " andi-gcc at firstfloor dot org
2010-06-08  9:40 ` andi-gcc at firstfloor dot org
2010-06-08  9:55 ` rguenth at gcc dot gnu dot org
2010-06-09 10:56 ` andi-gcc at firstfloor dot org
2010-06-09 10:56 ` andi-gcc at firstfloor dot org
2010-06-09 11:22 ` andi-gcc at firstfloor dot org
2010-06-09 12:09 ` rguenth at gcc dot gnu dot org
2010-06-09 12:15 ` rguenth at gcc dot gnu dot org
2010-06-09 12:16 ` rguenth at gcc dot gnu dot org
2010-06-09 12:16 ` andi-gcc at firstfloor dot org
2010-06-09 12:18 ` andi-gcc at firstfloor dot org
2010-06-09 13:01 ` rguenth at gcc dot gnu dot org
2010-06-09 13:03 ` rguenth at gcc dot gnu dot org
2010-06-09 13:35 ` andi-gcc at firstfloor dot org
2010-06-09 13:42 ` andi-gcc at firstfloor dot org [this message]
2010-06-09 13:56 ` andi-gcc at firstfloor dot org
2010-06-10 13:21 ` andi-gcc at firstfloor dot org
2010-06-10 13:22 ` andi-gcc at firstfloor dot org
2010-06-11 16:49 ` jamborm at gcc dot gnu dot org
2010-06-11 17:09 ` andi-gcc at firstfloor dot org
2010-06-15 11:09 ` jamborm at gcc dot gnu dot org
2010-06-16 17:01 ` jamborm at gcc dot gnu dot org
2010-06-16 17:02 ` jamborm 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=20100609134205.1596.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: 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).