public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikulas at artax dot karlin.mff.cuni.cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/60310] New: internal compiler error due to excessive alignment
Date: Sat, 22 Feb 2014 00:52:00 -0000	[thread overview]
Message-ID: <bug-60310-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60310
           Summary: internal compiler error due to excessive alignment
           Product: gcc
           Version: 4.8.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mikulas at artax dot karlin.mff.cuni.cz
              Host: arm-linux-gnueabihf
            Target: arm-linux-gnueabihf
             Build: arm-linux-gnueabihf

When compiling this piece of code with or without optimizations, gcc crashes
with
an internal error:

int f(void)
{
        struct { __attribute__((aligned(1 << 28)))double a; } x;
        return 0;
}

alignof.c: In function 'f':
alignof.c:3:9: internal compiler error: in round_up_loc, at fold-const.c:16748
  struct { __attribute__((aligned(1 << 28)))double a; } x;
         ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
Preprocessed source stored into /tmp/ccQIqkJl.out file, please attach this to
your bugreport.

I reproduced the bug on gcc-4.6.4, gcc-4.7.2, gcc-4.7.3, gcc-4.8.2.


             reply	other threads:[~2014-02-22  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-22  0:52 mikulas at artax dot karlin.mff.cuni.cz [this message]
2014-02-22  1:33 ` [Bug middle-end/60310] " glisse 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-60310-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).