public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "costamagnagianfranco at yahoo dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67989] New: [REGRESSION] g++ ICE on armel valid code
Date: Fri, 16 Oct 2015 15:57:00 -0000	[thread overview]
Message-ID: <bug-67989-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67989

            Bug ID: 67989
           Summary: [REGRESSION] g++ ICE on armel valid code
           Product: gcc
           Version: 5.2.1
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: costamagnagianfranco at yahoo dot it
  Target Milestone: ---

Hi, some regression has happened between
   * Update to SVN 20150903 (r227431, 5.2.1) from the gcc-5-branch.
and
   * Update to SVN 20151003 (r228449, 5.2.1) from the gcc-5-branch.

because with Debian gcc-5.2.1-16 llvm was building fine on armel, while with
gcc5.2.1-21 it is FTBFS with an ICE.

you can see the Debian bug [1] the build logs [2], a valid log [3], the same
source but with the ICE

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801862
[2] https://buildd.debian.org/status/logs.php?pkg=llvm-toolchain-3.4&arch=armel
[3]
https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-3.4&arch=armel&ver=1%3A3.4.2-15&stamp=1439243604
[4]
https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-3.4&arch=armel&ver=1%3A3.4.2-15%2Bb1&stamp=1444483187

I'm attaching here the preprocessed source.

I'm not sure about providing everything necessary to look at the issue, please
let me know if you need anything more.

(the same failure is happening e.g. with llvm-3.5)

thanks

G.


             reply	other threads:[~2015-10-16 15:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 15:57 costamagnagianfranco at yahoo dot it [this message]
2015-10-16 15:58 ` [Bug c++/67989] " costamagnagianfranco at yahoo dot it
2015-10-20 15:29 ` paolo.carlini at oracle dot com
2015-10-22  6:51 ` sylvestre at debian dot org
2015-10-22  8:52 ` [Bug target/67989] [5/6 Regression] " rguenth at gcc dot gnu.org
2015-10-22 10:20 ` ktkachov at gcc dot gnu.org
2015-10-22 12:06 ` ktkachov at gcc dot gnu.org
2015-10-22 12:14 ` [Bug target/67989] [4.9/5/6 " ktkachov at gcc dot gnu.org
2015-10-22 13:11 ` [Bug middle-end/67989] " ktkachov at gcc dot gnu.org
2015-10-26 10:28 ` ktkachov at gcc dot gnu.org
2015-10-26 10:31 ` ktkachov at gcc dot gnu.org
2015-10-27 14:04 ` ktkachov at gcc dot gnu.org
2015-10-27 14:07 ` ktkachov at gcc dot gnu.org
2015-10-27 14:08 ` ktkachov at gcc dot gnu.org
2015-10-27 14:18 ` costamagnagianfranco at yahoo dot it

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-67989-4@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).