public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/54911] lto-wrapper fails when compiling gcc with -flto -fuse-linker-plugin
Date: Mon, 15 Oct 2012 20:19:00 -0000	[thread overview]
Message-ID: <bug-54911-4-BlSyTjRDZf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54911-4@http.gcc.gnu.org/bugzilla/>


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

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |ebotcazou at gcc dot
                   |                            |gnu.org
         Resolution|                            |DUPLICATE

--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-10-15 20:18:45 UTC ---
> make
> ...
> gcc -flto -fuse-linker-plugin   -march=i486 -mtune=i686 -Os -pipe -DIN_GCC   > -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes
> -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long
> -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition
> -Wc++-compat   -DHAVE_CONFIG_H  -o cc1 c-lang.o c-family/stub-objc.o attribs.o
> c-errors.o c-decl.o c-typeck.o c-convert.o c-aux-info.o c-objc-common.o
> c-parser.o tree-mudflap.o c-family/c-common.o c-family/c-cppbuiltin.o
> c-family/c-dump.o c-family/c-format.o c-family/c-gimplify.o c-family/c-lex.o
> c-family/c-omp.o c-family/c-opts.o c-family/c-pch.o c-family/c-ppoutput.o
> c-family/c-pragma.o c-family/c-pretty-print.o c-family/c-semantics.o
> c-family/c-ada-spec.o i386-c.o default-c.o \
>   cc1-checksum.o main.o  libbackend.a libcommon-target.a libcommon.a
> ../libcpp/libcpp.a ../libdecnumber/libdecnumber.a libcommon.a
> ../libcpp/libcpp.a   ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a 
> -lcloog-isl -lisl -lppl_c -lppl  -lgmpxx -lmpc -lmpfr -lgmp -rdynamic -ldl  -lz
> In file included from ../../gcc-4.7.2/gcc/dse.c:4414:0,
>                  from insn-automata.c:31491,
>                  from :3612:
> ../../gcc-4.7.2/libcpp/lex.c: In function 'search_line_sse2':
> ../../gcc-4.7.2/libcpp/lex.c:370:15: internal compiler error: in convert_move,
> at expr.c:327

This is a known issue.  You cannot LTO bootstrap on x86 without -msse2.

*** This bug has been marked as a duplicate of bug 45475 ***


  parent reply	other threads:[~2012-10-15 20:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 14:49 [Bug lto/54911] New: " j-frankish at slb dot com
2012-10-15  9:56 ` [Bug lto/54911] " rguenth at gcc dot gnu.org
2012-10-15 15:19 ` j-frankish at slb dot com
2012-10-15 15:21 ` j-frankish at slb dot com
2012-10-15 15:22 ` j-frankish at slb dot com
2012-10-15 20:19 ` ebotcazou at gcc dot gnu.org [this message]
2012-10-16 17:12 ` j-frankish at slb dot com
2015-07-20 23:14 ` isomorphisms at sdf 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=bug-54911-4-BlSyTjRDZf@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).