[Bug c++/115192] [11/12/13/14/15 regression] -O3 miscompilation on x86-64 (loops with vectors and scalars) since r11-6380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115192
--- Comment #8 from Jakub Jelinek ---
(In reply to Richard Biener from comment #7)
> int main()
> {
> const int n = 3;
> float d[n*n];
> float4_t a[n*n];
I'd recommend using #define n 3 or enum { n = 3 }; instead of const int n = 3;
so that the arrays aren't unnecessary VLAs.
[Bug tree-optimization/115199] [15 regression] gettext (libtextstyle) testsuite miscompiled since r15-579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115199 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org Priority|P3 |P1 Summary|[15 regression] gettext |[15 regression] gettext |(libtextstyle) testsuite|(libtextstyle) testsuite |miscompiled |miscompiled since r15-579 --- Comment #5 from Jakub Jelinek --- r15-579-ga9251ab3c91c8c559d0306838575a666ae62dff4
[Bug c++/115192] [14/15 regression] -O3 miscompilation on x86-64 (loops with vectors and scalars) since r14-2117
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115192 Jakub Jelinek changed: What|Removed |Added CC||rsandifo at gcc dot gnu.org --- Comment #5 from Jakub Jelinek --- The #c4 testcase changed behavior with r11-6380-g9fa5b473b5b8e289b6542adfd5cfaddfb3036048
[Bug c++/115192] [14/15 regression] -O3 miscompilation on x86-64 (loops with vectors and scalars) since r14-2117
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115192 Jakub Jelinek changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed||2024-05-22 Target Milestone|--- |14.2 CC||jakub at gcc dot gnu.org, ||rguenth at gcc dot gnu.org Priority|P3 |P2 Status|UNCONFIRMED |NEW Summary|[14/15 regression] -O3 |[14/15 regression] -O3 |miscompilation on x86-64|miscompilation on x86-64 |(loops with vectors and |(loops with vectors and |scalars)|scalars) since r14-2117 --- Comment #3 from Jakub Jelinek --- Since r14-2117-gdd86a5a69cbda40cf76388a65d3317c91cb2b501
[Bug fortran/115107] f951: internal compiler error: Segmentation fault 0xcf878f crash_signal toplev.cc:314
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115107 --- Comment #13 from Jakub Jelinek --- So provide fixes upstream and hope they apply them soon.
[Bug sanitizer/115172] Invalid -fsanitize=bool sanitization of variable from named address space
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115172 --- Comment #11 from Jakub Jelinek --- Fixed for 13.4+/14.2+/15.1+ so far.
[Bug tree-optimization/115152] [13/14/15 Regression] wrong code at -O3 with "-fno-tree-fre -fno-tree-dominator-opts -fno-tree-loop-im" on x86_64-linux-gnu since r13-455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115152 Jakub Jelinek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #12 from Jakub Jelinek --- Fixed for 13.4+/14.2+/15.1+.
[Bug target/115161] [15 Regression] highway-1.0.7 miscompilation of some SSE2 intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161 --- Comment #19 from Jakub Jelinek --- (In reply to Alexander Monakov from comment #18) > No, allowing value-changing transformations under -ftrapping-math is really > not appropriate. Invoking the intrinsic on a large floating-point value is > not UB. If we guarantee that we never constant fold FIX/UNSIGNED_FIX with -ftrapping-math (we shouldn't, as the exceptions should be raised), then using FIX/UNSIGNED_FIX is ok in flag_trapping_math guarded patterns even if the intrinsics have some specific value they want in those cases, because they will never be folded. While for !flag_trapping_math, we should use UNSPEC because FIX/UNSIGNED_FIX can be folded and would be folded to whatever the generic code decides, which might disagree to what the intrinsics need.
[Bug target/115161] [15 Regression] highway-1.0.7 miscompilation of some SSE2 intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161 --- Comment #17 from Jakub Jelinek --- I don't think the cost of using UNSPEC would be significant if the backend tried to constant fold more target builtins. Anyway, with the proposed changes perhaps you could keep using FIX/UNSIGNED_FIX for flag_trapping_math case even for the intrinsics and use UNSPECs only for !flag_trapping_math.
[Bug fortran/115107] f951: internal compiler error: Segmentation fault 0xcf878f crash_signal toplev.cc:314
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115107 --- Comment #11 from Jakub Jelinek --- You want to fix the code as described in e.g. https://gcc.gnu.org/gcc-14/porting_to.html , not find workarounds. The code was apparently never valid C99+.
[Bug target/115161] [15 Regression] highway-1.0.7 miscompilation of some SSE2 intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161 Jakub Jelinek changed: What|Removed |Added CC||jsm28 at gcc dot gnu.org --- Comment #13 from Jakub Jelinek --- (In reply to Hongtao Liu from comment #11) > (In reply to Jakub Jelinek from comment #10) > > Any of the floating point to integer intrinsics if they have out of range > > value (haven't checked whether floating point to unsigned intrinsic is a > > problem too or not). > > No matter if it is float or double (dunno if _Float16 too, or __bf16), and > > no matter if it is scalar intrinsic (ss/sd etc.) or vector and how many > > vector elements. > > But, this isn't really a regression, GCC has always behaved that way, the > > only thing that actually changed is that perhaps we can constant fold more > > than we used to do in the past. > > When not using intrinsics, IMNSHO we should keep doing what we did before. > > Can we restrict them under flag_trapping_math? If we do that, we should do it on the fold-const.cc side as well. There we fold it but add TREE_OVERFLOW flag in the overflow cases to the resulting tree, whether it prevents folding or not during GIMPLE passes would need to be figured out. C23 in F.4 says: If the integer type is bool, 6.3.1.2 applies and the conversion raises no floating-point exceptions if the floating-point value is not a signaling NaN. Otherwise, if the floating value is infinite or NaN or if the integral part of the floating value exceeds the range of the integer type, then the "invalid" floating-point exception is raised and the resulting value is unspecified. Otherwise, the resulting value is determined by 6.3.1.4. Conversion of an integral floating value that does not exceed the range of the integer type raises no floating-point exceptions; whether conversion of a non-integral floating value raises the "inexact" floating-point exception is unspecified. That said, this change really won't help the backend which supposedly should have the same behavior regardless of -fno-trapping-math, because in that case it is the value of the result (which is unspecified by the standards) rather than whether an exception is triggered or not.
[Bug sanitizer/115172] Invalid -fsanitize=bool sanitization of variable from named address space
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115172 --- Comment #7 from Jakub Jelinek --- (In reply to Fedor Pchelkin from comment #6) > (In reply to Uroš Bizjak from comment #5) > > (In reply to Jakub Jelinek from comment #4) > > > Created attachment 58261 [details] > > > gcc15-pr115172.patch > > > > > > Full untested patch. > > > > I can confirm that this patch fixes boot for the kernel config from > > PR115172#43. > > Yep. I may confirm, too. Thanks for the prompt fix! > > If all goes well, is it expected to land in 14.2 and 13.4? If it is approved yes. 14.2 is expected likely in July this year, but 13.4 roughly in a year from now, as it just missed 13.3 (released today).
[Bug target/115161] [15 Regression] highway-1.0.7 miscompilation of some SSE2 intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161 --- Comment #10 from Jakub Jelinek --- Any of the floating point to integer intrinsics if they have out of range value (haven't checked whether floating point to unsigned intrinsic is a problem too or not). No matter if it is float or double (dunno if _Float16 too, or __bf16), and no matter if it is scalar intrinsic (ss/sd etc.) or vector and how many vector elements. But, this isn't really a regression, GCC has always behaved that way, the only thing that actually changed is that perhaps we can constant fold more than we used to do in the past. When not using intrinsics, IMNSHO we should keep doing what we did before.
[Bug target/115161] [15 Regression] highway-1.0.7 miscompilation of some SSE2 intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161 --- Comment #9 from Jakub Jelinek --- In that case we should separate *.md patterns which are used for C conversions from the patterns used by the intrinsics, keep using what we are right now for the former and either use UNSPEC (the quickest but not best code generating variant) or something more complex. If UNSPEC is used, we could get some constant folding back by adding gimple_fold handling for those and the like of __builtin_ia32_psubusb128 or __builtin_ia32_pminub128. For __builtin_ia32_cvttps2dq etc. obviously the folding should either punt folding if some argument is out of range or fold those to what the hw does.
[Bug target/115161] [15 Regression] highway-1.0.7 miscompilation of some SSE2 intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161 --- Comment #6 from Jakub Jelinek --- The standard GCC behavior is that out of range floating conversions to integers result in signed integer maximum if the floating point value sign is clear and signed integer minimum otherwise (including infinities/nans).
[Bug target/115161] [15 Regression] highway-1.0.7 miscompilation of some SSE2 intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
--- Comment #5 from Jakub Jelinek ---
Trying
#include
int
main ()
{
float f = 0x0.8p+33f;
float __attribute__((vector_size (16))) vf = { 0x0.8p+33f, 0x0.8p+33f,
0x0.8p+33f, 0x0.8p+33f };
int a = f;
int __attribute__((vector_size (16))) vi = __builtin_convertvector (vf, int
__attribute__((vector_size (16;
int __attribute__((vector_size (16))) vi2 = (int __attribute__((vector_size
(16 _mm_cvttps_epi32 ((__m128) vf);
__builtin_printf ("%d\n", a);
__builtin_printf ("{%d, %d, %d, %d}\n", vi[0], vi[1], vi[2], vi[3]);
__builtin_printf ("{%d, %d, %d, %d}\n", vi2[0], vi2[1], vi2[2], vi2[3]);
}
with gcc and clang both with -O0 and -O2, this prints
-2147483648
{-2147483648, -2147483648, -2147483648, -2147483648}
{-2147483648, -2147483648, -2147483648, -2147483648}
with both compilers at -O0, clang at -O2 prints
-1720305736
{8524448, 0, 1, 135169}
{-2147483648, -2147483648, -2147483648, -2147483648}
i.e. complete garbage for the non-intrinsic cases, but what the HW does for the
intrinsic cases, while gcc at -O2 prints
2147483647
{2147483647, 2147483647, 2147483647, 2147483647}
{2147483647, 2147483647, 2147483647, 2147483647}
i.e. treats intrinsics and non-intrinsics the same.
GCC behaves this way consistently since GCC 9 (before __builtin_convertvector
hasn't been supported), but if the vi related lines are commented out, even GCC
4.7 works that way.
[Bug target/115161] [15 Regression] highway-1.0.7 miscompilation of some SSE2 intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115161
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek ---
(In reply to Sergei Trofimovich from comment #3)
> Looking at -O2's bug.cc.265t.optimized tree optimizations come up with
> unfolded saturated sub8:
>
> _12 = __builtin_ia32_psubusb128 ({ -65, 0, 0, 0, -65, 0, 0, 0, -65, 0, 0,
> 0, -65, 0, 0, 0 }, { -99, 0, 0, 0, -99, 0, 0, 0, -99, 0, 0, 0, -99, 0, 0, 0
> });
> _13 = __builtin_ia32_pminub128 (_12, { 32, 0, 0, 0, 32, 0, 0, 0, 32, 0, 0,
> 0, 32, 0, 0, 0 });
> ...
>
>
> bug.cc.272r.cse1 still has that subtraction:
>
> 5: r119:V16QI=[`*.LC0']
> REG_EQUAL const_vector
> 6: r120:V16QI=[`*.LC1']
> REG_EQUAL const_vector
> 7: r118:V16QI=us_minus(r119:V16QI,r120:V16QI)
>
> bug.cc.273r.fwprop1 does not anymore:
>
> 3: NOTE_INSN_BASIC_BLOCK 2
> 2: NOTE_INSN_FUNCTION_BEG
> 9: r122:V16QI=[`*.LC2']
> REG_EQUAL const_vector
>13: r123:V4SI=r122:V16QI#0<<0x17
> REG_EQUAL const_vector
>16: r128:SI=0x5f80
>15: r127:V4SI=vec_duplicate(r128:SI)
>
> Could it be that constant folder "forgot" to generate anything for
> unsupported saturated-sub instead of leaving it as is?
No. It is normal constant folding on RTL (not done on GIMPLE because
the i386 backend doesn't try to gimple fold __builtin_ia32_psubusb128
or __builtin_ia32_psubusb128). 0xbf - 0x9d is 0x22, so the us_minus works
actually in this case exactly like minus and because 0x20 is smaller than that,
the minimum is a vector with 0x20 elements (plus min (0 - 0, 0) = 0 elements).
The reason the testcase FAILs is the same as in the other PRs, it is trying to
convert
{0x0.8p+33f, 0x0.8p+33f, 0x0.8p+33f, 0x0.8p+33f}
V4SFmode vector to V4SImode, and because the backend sees the constant operand
of the
fix, it folds it to the unspecified value as with scalar conversion.
Consider:
int
main ()
{
volatile float f = 0x0.8p+33f;
volatile float __attribute__((vector_size (16))) vf = { 0x0.8p+33f,
0x0.8p+33f, 0x0.8p+33f, 0x0.8p+33f };
int a = f;
int __attribute__((vector_size (16))) vi = __builtin_convertvector (vf, int
__attribute__((vector_size (16;
__builtin_printf ("%d\n", a);
__builtin_printf ("{%d, %d, %d, %d}\n", vi[0], vi[1], vi[2], vi[3]);
}
This prints
-2147483648
{-2147483648, -2147483648, -2147483648, -2147483648}
at -O0 or -O2, but with -O2 -Dvolatile= prints
2147483647
{2147483647, 2147483647, 2147483647, 2147483647}
instead.
Either is IMHO fine, the C standard doesn't specify what should be the result
of the conversion.
Now, whether for _mm_cvttps_epi32 etc. such cases are also unspecified or not
is debatable. The Intel spec obviously specifies what the CPU instructions do
even in those otherwise unspecified cases, the question is if the intrinsic
must behave the same or if those invalid conversions are still unspecified.
If they'd be well defined when using the intrinsics, arguably the backend
shouldn't use FIX RTL but some UNSPEC, or should use the FIX RTL conditionally
(if_then_else:SI (argument_is_in_bounds) (fix arg) (const_int 0x800)).
[Bug c++/115160] Enabling undefined behaviour sanitizer causes or'ed bit shift to report wrong result
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115160
--- Comment #6 from Jakub Jelinek ---
There is no inc in the last term.
Anyway, simplified example would be
int deref (int *);
int *inc (int *&);
int
baz (int *p)
{
return deref (inc (p)) | (deref (inc (p)) << 8) | (deref (inc (p)) << 16) |
(deref (p) << 24);
}
and while without the sanitization GCC chooses to evaluate this left to right,
with
sanitization it first turns it into essentially:
return deref (inc (p)) | ((tmp1 = deref (inc (p))), check_shift (tmp1, 8),
tmp1 << 8) | ((tmp2 = deref (inc (p))), check_shift (tmp2, 16), tmp2 << 16) |
((tmp3 = deref (p)), check_shift (tmp3, 24), tmp3 << 24);
but then further optimizations move the comma expression left hand sides before
the whole |, so it first evaluates the second deref+inc + checks the shift by
8, then
the third deref+inc + checks the shift by 16 etc. and then only the |
expressions and this is still valid due to the unspecified order of | operand
evaluations.
[Bug tree-optimization/115152] [13/14/15 Regression] wrong code at -O3 with "-fno-tree-fre -fno-tree-dominator-opts -fno-tree-loop-im" on x86_64-linux-gnu since r13-455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115152 --- Comment #8 from Jakub Jelinek --- Created attachment 58262 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58262=edit gcc15-pr115152.patch Untested fix.
[Bug sanitizer/115172] Invalid -fsanitize=bool sanitization of variable from named address space
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115172 Jakub Jelinek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek --- Created attachment 58261 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58261=edit gcc15-pr115172.patch Full untested patch.
[Bug sanitizer/115172] Invalid -fsanitize=bool sanitization of variable from named address space
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115172 --- Comment #2 from Jakub Jelinek --- That said, --- gcc/ubsan.cc.jj 2024-03-22 09:23:37.695296775 +0100 +++ gcc/ubsan.cc2024-05-21 12:10:24.261454107 +0200 @@ -1776,13 +1776,17 @@ instrument_bool_enum_load (gimple_stmt_i || TREE_CODE (gimple_assign_lhs (stmt)) != SSA_NAME) return; + addr_space_t as = TYPE_ADDR_SPACE (TREE_TYPE (rhs)); + if (as != TYPE_ADDR_SPACE (utype)) +utype = build_qualified_type (utype, TYPE_QUALS (utype) +| ENCODE_QUAL_ADDR_SPACE (as)); bool ends_bb = stmt_ends_bb_p (stmt); location_t loc = gimple_location (stmt); tree lhs = gimple_assign_lhs (stmt); tree ptype = build_pointer_type (TREE_TYPE (rhs)); tree atype = reference_alias_ptr_type (rhs); gimple *g = gimple_build_assign (make_ssa_name (ptype), - build_fold_addr_expr (rhs)); + build_fold_addr_expr (rhs)); gimple_set_location (g, loc); gsi_insert_before (gsi, g, GSI_SAME_STMT); tree mem = build2 (MEM_REF, utype, gimple_assign_lhs (g), seems to fix that. But wonder how many of the other ~180 spots that create MEM_REFs don't need similar fixes.
[Bug sanitizer/115172] Invalid -fsanitize=bool sanitization of variable from named address space
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115172
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed||2024-05-21
--- Comment #1 from Jakub Jelinek ---
Reduced testcase for -O2 -fsanitize=address,bool --param
asan-instrumentation-with-call-threshold=100:
extern struct S { _Bool b; } s;
void bar (void);
void
foo (void)
{
if (*(volatile _Bool __seg_gs *) (__UINTPTR_TYPE__) )
bar ();
}
What the kernel does is terrible, why they just don't declare the extern with
__seg_gs attribute?
[Bug c++/115160] Enabling undefined behaviour sanitizer causes or'ed bit shift to report wrong result
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115160 --- Comment #3 from Jakub Jelinek --- There is no sequence point analyzer in any compiler I'm aware of and I think it would be extremely hard to implement that. GCC has -Wsequence-point warning, which can handle lots of cases, but with the C++ abstractions the front-end can't really know what the different function calls will do and whether they have some undesirable side-effects or not. With the pointers, the compiler sees the post-increment operations, with overloaded operators it doesn't, it sees calls to some operator and it doesn't know what the operator will do. Those functions could be pure and not change anything on the shared object, or they can change it.
[Bug tree-optimization/115154] [13/14/15 Regression] wrong code at optimization levels -O2, -O3, -Os since r13-7434-g682bbd364708fe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115154 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #15 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/115152] [13/14/15 Regression] wrong code at -O3 with "-fno-tree-fre -fno-tree-dominator-opts -fno-tree-loop-im" on x86_64-linux-gnu since r13-455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115152 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #7 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug analyzer/114677] [13/14/15 Regression] -Wanalyzer-fd-leak false positive writing to int * param
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114677 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #2 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/114992] [13/14/15 Regression] ICE during IPA pass: targetclone in add_to_same_comdat_group with calling a target clone with a lamdba in a comdat function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114992 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #2 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/115143] [11/12/13 Regression] tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115143 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #14 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/114619] [13/14/15 regression] ICE with -fno-elide-constructors in C++14 mode for non-constant initializer in array new since r13-3175-g6ffbf87ca66f4e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114619 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #2 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug rtl-optimization/114788] [13/14/15 Regression] ICE on valid code at -O{2,3} on x86_64-linux-gnu (during RTL pass: sched2): in move_exprs_to_boundary, at sel-sched.cc:5236
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114788 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #2 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/114865] [13/14/15 Regression] std::atomic::compare_exchange_strong seems to hang under GCC 13 for C++11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114865 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #20 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug ada/114398] [13/14/15 regression] Storage_Error with 'Access of primitive function returning limited type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114398 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #3 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug rtl-optimization/114261] [13/14/15 Regression] Scheduling takes excessive time (97%) since r13-5154-g733a1b777f1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114261 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #11 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/114772] [13/14/15 Regression] pragma GCC target applied to earlier template function with __attribute__((warn_unused_result)) since r12-6904
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114772 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #3 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/114244] Need to use round when parsing fractional seconds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114244 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug analyzer/114159] [13 Regression] ICE: in call_info, at analyzer/call-info.cc:143 with -fanalyzer -fanalyzer-call-summaries --param=analyzer-max-svalue-depth=0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114159 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #4 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/114578] [13/14/15 Regression] memory hog, virtual memory exhausted, building a c++ file on arm-linux-gnueabihf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114578 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #6 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/114018] std::nexttoward is not implemented for C++23-FP-Types
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114018 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #19 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/113835] [13/14/15 Regression] compiling std::vector with const size in C++20 is slow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113835 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #7 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug target/114432] [13/14/15 Regression] ICE in connect_traces, at dwarf2cfi.cc:3079 on s390x-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114432 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #5 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug target/113690] [13 Regression] ICE: in as_a, at machmode.h:381 with -O2 -fno-dce -fno-forward-propagate -fno-split-wide-types -funroll-loops
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113690 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug target/113641] [13/14/15 regression] 510.parest_r with PGO at O2 slower than GCC 12 (7% on Zen 3&2, 4% on CascadeLake) since r13-4272-g8caf155a3d6e23
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113641 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #1 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/114324] [13/14/15 Regression] AVX2 vectorisation performance regression with gfortran 13/14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114324 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #6 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/111163] signed integer overflow in std::format("{:%S}",std::chrono::duration....)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #5 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/113434] [13/14/15 Regression] VRP misses conditional in loop is always false sometimes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113434 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #3 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug target/113994] [13/14/15 Regression] Probable C++ code generation bug with -O2 on s390x platform
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113994 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #12 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/113360] [13/14/15 Regression] Truncated constexpr error messages with -std=c++23/26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113360 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #3 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug analyzer/111099] [13/14/15 Regression] -fanalyzer -Os segmentation fault due to infinite recursion in ana::constraint_manager::eval_condition
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111099 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #4 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/113662] [13/14/15 Regression] Wrong code for std::sort with fancy pointer since r13-6945-g429a7a88438cc8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113662 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #6 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug rtl-optimization/113048] [13 Regression] ICE: in lra_split_hard_reg_for, at lra-assigns.cc:1862 (unable to find a register to spill) {*andndi3_doubleword_bmi} with -march=cascadelake since r13-17
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113048 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #11 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug fortran/115070] [13/14/15 Regression] ICE using IEEE_ARITHMETIC in a derived type method with class, intent(out)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115070 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug middle-end/112710] [13/14/15 Regression] ICE: in write_type, at cp/mangle.cc:2226 with -fdump-go-spec=filename -flto -fno-use-linker-plugin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112710 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #4 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/111073] [13/14/15 regression] False-positive -Wstringop-overflow when building gdb from trunk with -D_GLIBCXX_ASSERTIONS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111073 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #3 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/112453] : __take_of_repeat_view/__drop_of_repeat_view should forwards __r._M_value
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112453 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #3 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug rtl-optimization/113546] [13/14/15 Regression] aarch64: bootstrap-debug-lean broken with -fcompare-debug failure since r13-2921-gf1adf45b17f7f1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113546 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #6 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/114826] [13 Regression] Bogus -Warray-bounds warning for 32-byte array with certain march flags
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114826 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #5 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/110992] [13/14/15 Regression] missed VRP optimization due to transformation of `a & -zero_one_valued_p` into `a * zero_one_valued_p`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110992 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #15 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug debug/112703] [13/14/15 Regression] -fcompare-debug failure at -O1 and above
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112703 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #2 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/113239] [13/14/15 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #9 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/111471] Incorrect NTTP printing in the error messages
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111471 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #4 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/114770] std::chrono::locate_zone("Asia/Chungking") fails on Debian Sid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114770 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #2 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug sanitizer/110835] [13/14/15 Regression] -fsanitize=address causes huge runtime slowdown from std::rethrow_exception not called
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110835 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug middle-end/112305] [11/12/13 Regression] Wrong code at -O1/2/3/s on x86_64-pc-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112305 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #6 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug target/111165] [13 regression] builtin strchr miscompiles on Debian/x32 with dietlibc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #19 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug rtl-optimization/112657] [13/14/15 Regression] missed optimization: cmove not used with multiple returns
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112657 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #9 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug fortran/114373] [12/13 Regression] BLOCK construct not correctly analyzed with -fopenmp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114373 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #2 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug rtl-optimization/110390] [13/14/15 regression] ICE on valid code on x86_64-linux-gnu with sel-scheduling: in av_set_could_be_blocked_by_bookkeeping_p, at sel-sched.cc:3609 since r13-3596-ge7310e2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110390 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug analyzer/111266] [13 Regression] Missing -Wanalyzer-out-of-bounds for concrete offset overwrite.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111266 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #4 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/110997] [13 Regression] internal compiler error: in cxx_eval_constant_expression, at cp/constexpr.cc:8005
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110997 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug regression/111709] [13/14/15 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #14 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug middle-end/114196] [13 Regression] Fixed length vector ICE: in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9454
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114196 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug ipa/110334] [13/14 Regresssion] unused functions not eliminated before LTO streaming
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110334 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #28 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug analyzer/111305] [13/14/15 Regression] GCC Static Analyzer -Wanalyzer-out-of-bounds false postive
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111305 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #5 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/110501] [13/14/15 regression] Invalid -Wuse-after-free / realloc with a store/load happening
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110501 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #10 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/110829] [13/14/15 Regression] FAIL: gcc.dg/pr56837.c scan-tree-dump-times optimized "memset ..c, 68, 16384.;" 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110829 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #4 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/111077] atomic_ref compare_exchange_strong doesn't properly ignore padding bits
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111077 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #9 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/110269] [13 Regression] Missed Dead Code Elimination when using __builtin_unreachable since r13-4607-g2dc5d6b1e7e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110269 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #6 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/110251] [13 Regression] Hang at -O3 on x86_64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #17 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c/109828] [13/14/15 Regression] static compound literal with flexible array in initializer leads to invalid size and ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109828 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #12 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/111075] [13/14/15 Regression] ICE on g++.dg/torture/tail-padding1.C on darwin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111075 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #6 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/110503] [13/14/15 Regression] Dead Code Elimination Regression at -O3 since r13-322-g7f04b0d786e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110503 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/110145] 20_util/to_chars/double.cc fails for -m32 -fexcess-precision=standard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110145 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #10 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/109966] [13 Regression] ICE in gimplify_var_or_parm_decl, à gimplify.cc:3058
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109966 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/110382] [13 Regression] internal compiler error: in verify_ctor_sanity
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110382 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #7 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/109814] [13/14/15 Regression] freestanding using cmath does not compile anymore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109814 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #14 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/109889] [13/14/15 Regression] Segfault in __run_exit_handlers since r13-5309-gc3c6c307792026
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109889 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #14 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug analyzer/110285] [13/14/15 Regression] -Wanalyzer-infinite-recursion false positive involving floating-point values
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110285 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #5 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/109943] [13/14/15 Regression] Missed Dead Code Elimination when using __builtin_unreachable since r13-6834-g41ade3399bd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109943 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #7 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/109772] [13 Regression] Memory layout optimization of std::chrono::hh_mm_ss is wrong
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109772 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #7 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/110361] [13/14/15 Regression] Missed Dead Code Elimination when using __builtin_unreachable since r13-2020-g16b013c9d9b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110361 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #3 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/109683] [13/14/15 Regression] False cyclic dependency error reported for constraint
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109683 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #4 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug analyzer/110014] -Wanalyzer-allocation-size mishandles realloc (..., .... * sizeof (object))
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110014 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #8 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/110173] [13/14/15 Regression] Missed Dead Code Elimination when using __builtin_unreachable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110173 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #9 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug analyzer/109802] [13 Regression] ICE using dubious flexible arrays in unions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109802 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #7 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/109083] [11/12/13/14/15 Regression] Incorrect static_assert shown in diagnostics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109083 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #9 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug libstdc++/109857] Debian stable's tzdata 2021a has bad data that cannot be parsed by libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109857 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #7 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/109410] [13/14/15 Regression] ICE: verify_flow_info failed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109410 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #19 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug c++/110114] [13 Regression] ICE on calling overloaded function in case of incomplete argument type and C++ designated initializers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110114 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #9 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug middle-end/109727] [13/14/15 Regression] -Warray-bounds false positive with -fsanitize=undefined
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109727 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #2 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
[Bug tree-optimization/109213] [13/14/15 Regression] -Os generates significantly more code since r13-723
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109213 Jakub Jelinek changed: What|Removed |Added Target Milestone|13.3|13.4 --- Comment #11 from Jakub Jelinek --- GCC 13.3 is being released, retargeting bugs to GCC 13.4.
