public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97164] [8/9/10/11 Regression] incorrect offset on structure member where type of that member has aligned attribute
Date: Wed, 23 Sep 2020 08:01:17 +0000 [thread overview]
Message-ID: <bug-97164-4-PjuJnt4jPl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97164-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
With additional
--- libgcc/config/libbid/bid_functions.h.jj 2020-01-14 20:02:48.619582332
+0100
+++ libgcc/config/libbid/bid_functions.h 2020-09-23 01:12:02.672546190
+0200
@@ -81,7 +81,7 @@ ALIGN (16)
#define SQRT80 sqrtw
#endif
- typedef ALIGN (16)
+ typedef ALIGN (8)
struct {
UINT64 w[3];
} UINT192;
it bootstrapped on x86_64-linux, with
gcc.c-torture/execute/pr36093.c and gcc.c-torture/execute/pr43783.c tests that
use the same things regressing (guess they'd need to be removed).
Is libgcc always compiled with the new compiler rather than with system
compiler though? If not, that might be a blocker for building older gcc
versions with the new one.
next prev parent reply other threads:[~2020-09-23 8:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 12:20 [Bug tree-optimization/97164] New: " jan.smets at nokia dot com
2020-09-22 12:28 ` [Bug tree-optimization/97164] " jakub at gcc dot gnu.org
2020-09-22 12:51 ` jakub at gcc dot gnu.org
2020-09-22 13:59 ` [Bug tree-optimization/97164] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-09-22 14:21 ` rguenth at gcc dot gnu.org
2020-09-22 14:35 ` jakub at gcc dot gnu.org
2020-09-23 7:56 ` jakub at gcc dot gnu.org
2020-09-23 8:01 ` jakub at gcc dot gnu.org [this message]
2020-09-23 8:20 ` rguenth at gcc dot gnu.org
2020-09-23 10:08 ` jan.smets at nokia dot com
2020-10-12 11:49 ` rguenth at gcc dot gnu.org
2020-10-23 8:08 ` cvs-commit at gcc dot gnu.org
2021-01-25 13:56 ` [Bug tree-optimization/97164] [8/9/10 " jakub at gcc dot gnu.org
2021-05-14 9:53 ` [Bug tree-optimization/97164] [9/10 " jakub at gcc dot gnu.org
2021-06-01 8:18 ` rguenth at gcc dot gnu.org
2022-05-27 9:43 ` [Bug tree-optimization/97164] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2023-07-07 9:05 ` rguenth 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-97164-4-PjuJnt4jPl@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).