public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nheghathivhistha at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60568] lto1: internal compiler error: in insn_min_length, at config/i386/i386.md:1599
Date: Wed, 19 Mar 2014 18:36:00 -0000	[thread overview]
Message-ID: <bug-60568-4-3CxwC30u9W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60568-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from David Kredba <nheghathivhistha at gmail dot com> ---
This is the command line that is enough to get the crash:

/usr/bin/x86_64-pc-linux-gnu-g++  -m32 -fPIC -flto=4 -fuse-linker-plugin -O2
-ggdb -pipe -march=core2 -mtune=core2 -mno-3dnow -mno-sse4.2 -mno-avx 
-Wl,-Bsymbolic,-znoexecstack  -flto=4 -fuse-linker-plugin -Wl,--as-needed
-Wl,-O2 -Wl,-flto -O2 -ggdb -pipe -march=core2 -mtune=core2 -mno-3dnow
-mno-sse4.2 -mno-avx -o libx265.so.0.8 
encoder/CMakeFiles/encoder.dir/__/Lib/TLibEncoder/TEncSbac.cpp.o  -r -nostdlib

When I ran it with

/usr/bin/x86_64-pc-linux-gnu-g++  -m32 -fPIC -flto=4 -fuse-linker-plugin -O2
-ggdb -pipe -march=core2 -mtune=core2 -mno-3dnow -mno-sse4.2 -mno-avx 
-Wl,-Bsymbolic,-znoexecstack  -flto=4 -fuse-linker-plugin -Wl,--as-needed
-Wl,-O2 -Wl,-flto -O2 -ggdb -pipe -march=core2 -mtune=core2 -mno-3dnow
-mno-sse4.2 -mno-avx -o libx265.so.0.8 -fpreprocessed ./TEncSbac.ii  -r
-nostdlib

(or without -fpreprocessed) it does link the library!

I attached gzipped object file got using -march/tune=core2.


  parent reply	other threads:[~2014-03-19 18:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 19:33 [Bug lto/60568] New: " nheghathivhistha at gmail dot com
2014-03-19 15:57 ` [Bug target/60568] " ubizjak at gmail dot com
2014-03-19 16:53 ` jakub at gcc dot gnu.org
2014-03-19 18:01 ` nheghathivhistha at gmail dot com
2014-03-19 18:34 ` nheghathivhistha at gmail dot com
2014-03-19 18:36 ` nheghathivhistha at gmail dot com [this message]
2014-03-19 19:22 ` jakub at gcc dot gnu.org
2014-03-19 22:20 ` ubizjak at gmail dot com
2014-03-19 22:37 ` jakub at gcc dot gnu.org
2014-03-20 16:06 ` jakub at gcc dot gnu.org
2014-03-20 16:11 ` jakub at gcc dot gnu.org
2014-03-20 16:35 ` jakub at gcc dot gnu.org
2014-03-20 16:38 ` jakub at gcc dot gnu.org
2014-03-20 19:52 ` nheghathivhistha at gmail dot com
2014-03-20 20:22 ` jakub at gcc dot gnu.org
2014-03-20 20:49 ` trippels 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-60568-4-3CxwC30u9W@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).