https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
--- Comment #1 from Tomasz Konojacki ---
(In reply to Tomasz Konojacki from comment #0)
> The error below occurs only with -Od.
Sorry, -Og.
PS. It seems that moving the definition of fun4 to the first line
makes the error disappear.
On Tue, Nov 29, 2022 at 7:10 PM Arthur Cohen wrote:
>
> Hi Richard,
>
> (...)
>
> +
> + unsigned HOST_WIDE_INT ltype_length
> += wi::ext (wi::to_offset (TYPE_MAX_VALUE (ltype_domain))
> +- wi::to_offset (TYPE_MIN_VALUE (ltype_domain)) + 1,
> >>>
> >>>
On Tue, Nov 29, 2022 at 7:10 PM Arthur Cohen wrote:
>
> Hi Richard,
>
> (...)
>
> +
> + unsigned HOST_WIDE_INT ltype_length
> += wi::ext (wi::to_offset (TYPE_MAX_VALUE (ltype_domain))
> +- wi::to_offset (TYPE_MIN_VALUE (ltype_domain)) + 1,
> >>>
> >>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
Bug ID: 107931
Summary: [12 Regression] -Od causes always_inline to fail
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Tue, Nov 29, 2022 at 4:41 PM James K. Lowden
wrote:
>
> I don't understand how to access in a front end the arguments to the -I
> option on the command line.
>
> Cobol has a feature similar to the C preprecessor, known as the
> Compiler Directing Facility (CDF). The CDF has a COPY statement
On Tue, Nov 29, 2022 at 11:05 AM Manolis Tsamis wrote:
>
> When using SWAR (SIMD in a register) techniques a comparison operation within
> such a register can be made by using a combination of shifts, bitwise and and
> multiplication. If code using this scheme is vectorized then there is
>
On Thu, Nov 24, 2022 at 4:27 PM Iskander Shakirzyanov
wrote:
>
> How did you test the patch? If you bootstrapped it and ran the
> testsuite then it's OK.
>
> Yes, i ran testsuite and bootstrapped and everything seemed OK, but i missed
> fail of tests gcc.dg/Warray-bounds-34.c and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103011
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103769
Andrew Pinski changed:
What|Removed |Added
CC||unlvsur at live dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102739
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102553
--- Comment #9 from Andrew Pinski ---
Full backtrace:
0x121ce0f crash_signal
/home/apinski/src/upstream-gcc/gcc/gcc/toplev.cc:314
0x14e5890 strip_array_types(tree_node*)
/home/apinski/src/upstream-gcc/gcc/gcc/tree.cc:7262
Update in V2:
Add documentation for -mlam={none,u48,u57} to x86 options in invoke.texi.
gcc/ChangeLog:
* doc/invoke.texi (x86 options): Document
-mlam={none,u48,u57}.
* config/i386/i386-opts.h (enum lam_type): New enum.
* config/i386/i386.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102553
--- Comment #8 from Andrew Pinski ---
Reduced all the way:
struct s1{};
template inline constexpr s1 ch{};
template struct s2{};
template using alias1 = s2;
template
void general(int n)
{
alias1>{};
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102553
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #7 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102550
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
Thanks for your comment!
Date: Wed, 30 Nov 2022 12:30:02 +0800
Message-ID: <7ebkopxdx1@pike.rch.stglabs.ibm.com>
Segher Boessenkool writes:
>> > + else if ((ud4 == 0x && ud3 == 0x)
>> > + && ((ud1 & 0x8000) || (ud1 == 0 && !(ud2 & 0x8000
>> > +{
>> > + temp =
Ping.
> -Original Message-
> From: Tamar Christina
> Sent: Monday, October 31, 2022 12:00 PM
> To: gcc-patches@gcc.gnu.org
> Cc: nd ; Richard Earnshaw ;
> Marcus Shawcroft ; Kyrylo Tkachov
> ; Richard Sandiford
>
> Subject: [PATCH 7/8]AArch64: Consolidate zero and sign extension
Ping x3
> -Original Message-
> From: Tamar Christina
> Sent: Tuesday, November 22, 2022 4:01 PM
> To: Tamar Christina ; Richard Sandiford
>
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; Marcus Shawcroft
> ; Kyrylo Tkachov
> Subject: RE: [PATCH 5/8]AArch64 aarch64: Make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107413
--- Comment #16 from Rama Malladi ---
(In reply to Wilco from comment #15)
> (In reply to Rama Malladi from comment #14)
> > This fix also improved performance of 538.imagick_r by 15%. Did you have a
> > similar observation? Thank you.
>
> No,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107872
--- Comment #5 from Jerry DeLisle ---
Except WARNING: program timed out.
FAIL: gfortran.dg/merge_1.f90 -O0 execution test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107872
--- Comment #4 from Jerry DeLisle ---
Pauls patch regression tests fine. Thanks Paul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107930
Bug ID: 107930
Summary: wchar_t may not be the native character type for
windows
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107929
cqwrteur changed:
What|Removed |Added
CC||unlvsur at live dot com
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107929
Bug ID: 107929
Summary: std::experimental::simd needs to be reimplemented with
GCC's vector extension
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #11 from Andrew Pinski ---
(In reply to piliu from comment #10)
> (In reply to Andrew Pinski from comment #7)
> > I am trying to understand this. Is it ok to use the SSE registers inside
> > purgatory or not?
> >
>
> SSE can speed
> > "Joel" == Joel Brobecker via Gdb-patches
> > writes:
>
> Joel> ChangeLog:
>
> Joel> * src-release.sh (GDB_SUPPORT_DIRS): Add libsframe.
>
> Joel> Ok to apply to master?
>
> Looks good to me.
> I think we recently agreed that gdb and binutils maintainers can approve
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105134
--- Comment #10 from piliu at redhat dot com ---
(In reply to Andrew Pinski from comment #7)
> I am trying to understand this. Is it ok to use the SSE registers inside
> purgatory or not?
>
SSE can speed up the program, and if possible it is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107926
--- Comment #3 from Andrew Pinski ---
Note we reference char array still with:
unsigned short s[5] = {u"abc",1};
__WCHAR_TYPE__ s1[5] = {L"abc", 1};
But I also notice clang does too so maybe it is not so bad ...
Just for reference the C++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107928
Bug ID: 107928
Summary: ICE in on_bind, at analyzer/sm-fd.cc:1869
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Hi,
This patch is just using a more readable pattern for "rldicl x,x,0,32"
to clean high 32bits.
Old pattern looks like: r118:DI=zero_extend(r120:DI#0)
new pattern looks like: r118:DI=r120:DI&0x
Bootstrap and regtest pass on ppc64{,le}.
Is this ok for trunk?
BR,
Jeff (Jiufu)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107927
Bug ID: 107927
Summary: vector::push_back gives array bounds warning with
optimization and undefined sanitizer
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107926
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On Wed, Nov 30, 2022 at 3:12 AM H.J. Lu wrote:
>
> On Mon, Nov 28, 2022 at 11:04 PM Hongtao Liu wrote:
> >
> > On Mon, Nov 28, 2022 at 9:06 PM liuhongt wrote:
> > >
> > > For __builtin_ia32_vec_set_v16qi (a, -1, 2) with
> > > !flag_signed_char. it's transformed to
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107801
--- Comment #16 from Jonathan Wakely ---
Already fixed on trunk, see g:a7b97a1f6b9d4993545525fd5cb334ae640ddf45
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107926
Andrew Pinski changed:
What|Removed |Added
Known to fail||12.1.0, 4.1.2
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107569
Romain Geissler changed:
What|Removed |Added
CC||romain.geissler at amadeus dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107926
Bug ID: 107926
Summary: wrong error message for excess elements in array
initializer using a string literal
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103546
--- Comment #7 from David Malcolm ---
As it notes, the above patch reduces the number of false positives on
flex-generated scanners, but doesn't fix them all. Keeping this bug open to
track fixing them.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105784
David Malcolm changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
PR analyzer/103546 tracks various false positives seen on
flex-generated lexers.
Whilst investigating them, I noticed an ICE with
-fanalyzer-call-summaries due to attempting to store sm-state
for an UNKNOWN svalue, which this patch fixes.
This patch also provides known_function implementations
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-4400-g84046b192e568e.
gcc/analyzer/ChangeLog:
* region-model-impl-calls.cc (class kf_fgets): Move to sm-file.cc.
(kf_fgets::impl_call_pre): Likewise.
(class kf_fread): Likewise.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-4398-g3a32fb2eaa761a.
gcc/analyzer/ChangeLog:
PR analyzer/105784
* region-model-manager.cc
(region_model_manager::maybe_fold_binop): For POINTER_PLUS_EXPR,
PLUS_EXPR and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103546
--- Comment #6 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:78a17f4452db9514da7cc8706c654cb98ba0a8e6
commit r13-4399-g78a17f4452db9514da7cc8706c654cb98ba0a8e6
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105784
--- Comment #1 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:3a32fb2eaa761aac13ffe5424748d5839038ef66
commit r13-4398-g3a32fb2eaa761aac13ffe5424748d5839038ef66
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107801
--- Comment #15 from Jan Dubiec ---
I have applied the patch manually to 12.2 tree and this time got following
error message:
/bin/sh ../../libtool --tag CXX --tag disable-shared --mode=compile
/d/Works/xcomp/gcc-build/./gcc/xgcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107542
Patrick Palka changed:
What|Removed |Added
Target Milestone|--- |12.3
--- Comment #6 from Patrick Palka
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107542
--- Comment #5 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:000e9863120cbc75a0f8d497264519974c97669f
commit r13-4397-g000e9863120cbc75a0f8d497264519974c97669f
Author: Patrick Palka
Date:
On Tue, Nov 29, 2022 at 9:54 AM wrote:
>
> From: Sören Tempel
>
> On glibc, there are two versions of strerror_r: An XSI-compliant and a
> GNU-specific version. The latter is only available on glibc. In order
> to avoid duplicating the post-processing code of error messages, this
> commit
On Tue, Nov 29, 2022 at 04:38:50PM -0500, Jason Merrill wrote:
> > --- gcc/testsuite/g++.dg/gomp/for-21.C.jj 2020-01-12 11:54:37.178401867
> > +0100
> > +++ gcc/testsuite/g++.dg/gomp/for-21.C 2022-11-29 13:06:59.038410557
> > +0100
> > @@ -54,9 +54,9 @@ void
> > f6 (S ()[10])
> > {
>
Weitergeleitete Nachricht
Betreff: [PATCH] libstdc++: Add error handler for
Datum: Tue, 29 Nov 2022 22:41:07 +0100
Von: Björn Schäpers
An: gcc-patc...@gc.gnu.org, libstd...@gcc.gnu.org
From: Björn Schäpers
Not providing an error handler results in a nullpointer
On 11/29/22 07:32, Jakub Jelinek wrote:
Hi!
The PR84469 patch I've just posted regresses the for-21.C testcase,
when in OpenMP loop there are at least 2 associated loops and
in a template outer structured binding with non type dependent expression
is used in the expressions of some inner loop,
On 11/29/22 15:03, Patrick Palka wrote:
In a SFINAE context composite_pointer_type returns error_mark_node if
the given pointer types are incompatible, but the SPACESHIP_EXPR case of
cp_build_binary_op wasn't prepared to handle error_mark_node, which led
to an ICE (from spaceship_comp_cat) for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107925
--- Comment #4 from Andrew Pinski ---
Maybe related to r8-4520-g1bad9c1806ac51 ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107925
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107925
--- Comment #2 from Martin Liška ---
Created attachment 53987
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53987=edit
gcda file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107925
--- Comment #1 from Martin Liška ---
Created attachment 53986
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53986=edit
test-case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107925
Bug ID: 107925
Summary: ICE in update_specialized_profile at
gcc/ipa-cp.cc:5082 for 531.deepsjeng_r benchmark
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
--- Comment #8 from Andrew Pinski ---
There is another question, how does this folding interact with
-fnon-call-exceptions and is it still correct?
E.g. compile at -O1 -march=armv8-a+sve2 -fnon-call-exceptions:
#include "arm_sve.h"
svint8_t
Hi Iain,
On Tue, 29 Nov 2022, Iain Buclaw via Gcc-patches wrote:
> This looks obvious, however I don't know how things are generated for
> the online documentation site in order to say this won't cause any
> problems for whatever process is building these pages.
>> maintainer-scripts/ChangeLog:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
--- Comment #7 from Andrew Pinski ---
Something like this should fix the issue (note setting the location should be
done also):
diff --git a/gcc/config/aarch64/aarch64-sve-builtins-base.cc
b/gcc/config/aarch64/aarch64-sve-builtins-base.cc
index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107922
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
In a SFINAE context composite_pointer_type returns error_mark_node if
the given pointer types are incompatible, but the SPACESHIP_EXPR case of
cp_build_binary_op wasn't prepared to handle error_mark_node, which led
to an ICE (from spaceship_comp_cat) for the below testcase where we form
a <=> with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107627
--- Comment #6 from Jakub Jelinek ---
(In reply to Jakub Jelinek from comment #5)
> On the other side, split_double_concat needs to take into account when the
> destination
> and/or source are MEMs and some registers are used in their
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
--- Comment #5 from Andrew Pinski ---
Note I tried with (same options):
void
f (void)
{
int t = 16;
int t1 = 4;
int t2 = 8;
int t3 = 0;
__builtin_aarch64_im_lane_boundsi (t, t1, t3);
}
But since we are removing the vdef via
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107905
--- Comment #4 from Andrew Pinski ---
(In reply to Alexander Monakov from comment #3)
> LLVM does a better job at code layout, and massively wins on the amount of
> executed branches (in particular unconditional jumps). With
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107542
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107905
Alexander Monakov changed:
What|Removed |Added
Keywords|ra |
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
--- Comment #4 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> Which was added by r13-1055-g494bec025002df .
>
> The question becomes is gimple folding allowed to add MEM references here or
> not?
No other target (or even
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107627
--- Comment #5 from Jakub Jelinek ---
(In reply to Roger Sayle from comment #4)
> Perhaps:
> (define_insn_and_split "*concat3_1"
> [(set (match_operand: 0 "nonimmediate_operand" "=ro,r,r")
> (any_or_plus:
> (ashift:
On Mon, Nov 28, 2022 at 11:04 PM Hongtao Liu wrote:
>
> On Mon, Nov 28, 2022 at 9:06 PM liuhongt wrote:
> >
> > For __builtin_ia32_vec_set_v16qi (a, -1, 2) with
> > !flag_signed_char. it's transformed to
> > __builtin_ia32_vec_set_v16qi (_4, 255, 2) in the gimple,
> > and expanded to (const_int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846
--- Comment #10 from James Hilliard ---
(In reply to Jakub Jelinek from comment #8)
> (In reply to James Hilliard from comment #7)
> > (In reply to Jakub Jelinek from comment #6)
> > > Created attachment 53984 [details]
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846
--- Comment #9 from Andrew Pinski ---
(In reply to James Hilliard from comment #7)
> This appears to fix error, the warning is still present:
> progs/test_tc_tunnel.c: In function '__encap_ipv4':
> progs/test_tc_tunnel.c:228:31: warning: taking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55899
--- Comment #3 from joseph at codesourcery dot com ---
C2x provides type-generic versions of various such operations,
in addition to type-specific versions (but the type-specific versions are
for unsigned char through unsigned long long, so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846
--- Comment #8 from Jakub Jelinek ---
(In reply to James Hilliard from comment #7)
> (In reply to Jakub Jelinek from comment #6)
> > Created attachment 53984 [details]
> > gcc13-pr107846.patch
> >
> > Untested fix.
>
> This appears to fix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107846
--- Comment #7 from James Hilliard ---
(In reply to Jakub Jelinek from comment #6)
> Created attachment 53984 [details]
> gcc13-pr107846.patch
>
> Untested fix.
This appears to fix error, the warning is still present:
progs/test_tc_tunnel.c:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104546
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> It is specifically svld1rq_s8 folding into:
> # VUSE <.MEM>
> _5 = MEM [(signed char * {ref-all})x_3(D)];
>
>
> Which is done by svld1rq_impl::fold
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
--- Comment #2 from Andrew Pinski ---
It is specifically svld1rq_s8 folding into:
# VUSE <.MEM>
_5 = MEM [(signed char * {ref-all})x_3(D)];
Which is done by svld1rq_impl::fold (aarch64-sve-builtins-base.cc:1214).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107850
--- Comment #10 from Charles-Henri Gros ---
I'd be happy with any algorithm that meets my needs, though the presence of a
different algorithm that does the same thing that the existing algorithm
currently does, or at least subsumes all the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105746
--- Comment #4 from Jonathan Wakely ---
(In reply to Richard Biener from comment #3)
> Fixed by r13-4393-gcca06f0d6d76b0 on trunk?
Yes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105823
Richard Biener changed:
What|Removed |Added
Keywords||needs-bisection
--- Comment #2 from
Ping.
This looks obvious, however I don't know how things are generated for
the online documentation site in order to say this won't cause any
problems for whatever process is building these pages.
Excerpts from Iain Buclaw's message of November 21, 2022 11:29 am:
> Hi,
>
> This patch adds gdc
Hi PA, hi Andrew, hi Jakub, hi all,
On 29.11.22 16:56, Paul-Antoine Arras wrote:
This patch adds support for 'gfx803' as an alias for 'fiji' in OpenMP
context selectors, [...]
I think this should be documented somewhere. We have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105746
Richard Biener changed:
What|Removed |Added
Known to work||13.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106149
Richard Biener changed:
What|Removed |Added
Target|powerpc64-linux-gnu |powerpc64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107004
Richard Biener changed:
What|Removed |Added
Known to fail|13.0|
Summary|[12/13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107874
--- Comment #7 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:3832c6f7e672e76bba74a508bf3a49740ea38046
commit r13-4394-g3832c6f7e672e76bba74a508bf3a49740ea38046
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105918
--- Comment #4 from Richard Biener ---
(In reply to Andrew Pinski from comment #1)
> Shorter testcase (still need to reduce it futher):
> #include
> void toChars(int number) {
> char temp[1];
> std::to_chars(temp, temp + 1, number);
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107924
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524
Bug 103524 depends on bug 107924, which changed state.
Bug 107924 Summary: ICE in trees_out::tree_node with fsanitize=undefined and
modules
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107924
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98735
Andrew Pinski changed:
What|Removed |Added
CC||gs...@t-online.de
--- Comment #2 from
Hi Richard,
(...)
+
+ unsigned HOST_WIDE_INT ltype_length
+= wi::ext (wi::to_offset (TYPE_MAX_VALUE (ltype_domain))
+- wi::to_offset (TYPE_MIN_VALUE (ltype_domain)) + 1,
TYPE_MIN_VALUE is not checked to be constant, also the correct
check would be to use TREE_CODE (..)
Hi Richard,
(...)
+
+ unsigned HOST_WIDE_INT ltype_length
+= wi::ext (wi::to_offset (TYPE_MAX_VALUE (ltype_domain))
+- wi::to_offset (TYPE_MIN_VALUE (ltype_domain)) + 1,
TYPE_MIN_VALUE is not checked to be constant, also the correct
check would be to use TREE_CODE (..)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107924
Bug ID: 107924
Summary: ICE in tree_node, at cp/module.cc:9260
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107699
--- Comment #8 from Carlos Galvez ---
I see!
In that case may I suggest to split the diagnostic into "Warray-bounds" and
"Wmaybe-array-bounds"? That way we could enable the first and disable the
second. The way it is today, we need to disable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107923
G. Steinmetz changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107923
Bug ID: 107923
Summary: ICE in lookup_function_fuzzy_find_candidates /
check_interface0
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
1 - 100 of 250 matches
Mail list logo
