https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:50bc94898fac1bd9cc1dabf227208fb5d369c4c4
commit r11-4282-g50bc94898fac1bd9cc1dabf227208fb5d369c4c4
Author: Jakub Jelinek
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
--- Comment #9 from Jan Smets ---
Thanks for the quick resolution everyone. Our codebase apparenty has a handful
of these issues.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
--- Comment #8 from Richard Biener ---
(In reply to Jakub Jelinek from comment #7)
> 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
--- Comment #7 from Jakub Jelinek ---
With additional
--- libgcc/config/libbid/bid_functions.h.jj 2020-01-14 20:02:48.619582332
+0100
+++ libgcc/config/libbid/bid_functions.h2020-09-23 01:12:02.672546190
+0200
@@ -81,7 +81,7 @@ ALIGN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
--- Comment #6 from Jakub Jelinek ---
Created attachment 49260
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49260&action=edit
gcc11-pr97164.patch
I've tried the above patch overnight, unfortunately libbid uses such construct,
so it broke
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
--- Comment #5 from Jakub Jelinek ---
Indeed, if in the above testcase one uses b[40] instead of b[64], then it is
rejected with that error message.
Note, this isn't a FE diagnostics, but stor-layout.c one.
We won't be able to diagnose this if th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
Richard Biener changed:
What|Removed |Added
CC||jsm28 at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97164
Richard Biener changed:
What|Removed |Added
Summary|incorrect offset on |[8/9/10/11 Regression]
