public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90597] [9/10/11 Regression] FAIL: gcc.dg/attr-vector_size.c (internal compiler error)
Date: Tue, 01 Sep 2020 11:04:54 +0000	[thread overview]
Message-ID: <bug-90597-4-J5H1i9Ryko@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90597-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

https://gcc.gnu.org/g:b61eaa25b0812a5996024e0ddb3535dde5a89c88

commit r11-2965-gb61eaa25b0812a5996024e0ddb3535dde5a89c88
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Tue Sep 1 12:03:21 2020 +0100

    PR middle-end/90597: gcc_assert ICE in layout_type

    This patch fixes the default implementation of TARGET_VECTOR_ALIGNMENT,
    known as default_vector_alignment, using the same logic as my earlier
    nvptx patch, as the ICE caused by TYPE_SIZE(type) being zero during
    error handling in gcc.dg/attr-vector_size.c is common among backends,
    and is known in bugzilla as PR middle-end/90597, apparently a recent
    regression.

    2020-09-01  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/ChangeLog:
            PR middle-end/90597
            * targhooks.c (default_vector_alignment): Return at least the
            GET_MODE_ALIGNMENT for the type's mode.

  parent reply	other threads:[~2020-09-01 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90597-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` [Bug middle-end/90597] [9/10 " jakub at gcc dot gnu.org
2020-09-01 11:04 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-01  8:14 ` [Bug middle-end/90597] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-03-06 13:50 ` roger at nextmovesoftware dot com

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