https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111017
--- Comment #5 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:1dc65003b66e5a97200f454eeddcccfce34416b3
commit r14-3332-g1dc65003b66e5a97200f454eeddcccfce34416b3
Author: Tobias Burnus
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111072
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111072
Bug ID: 111072
Summary: Splicing at the end fails
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111071
Andrew Pinski changed:
What|Removed |Added
Keywords||testsuite-fail
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111071
--- Comment #1 from Thiago Jung Bauermann
---
Created attachment 55761
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55761=edit
gcc.log from commit a32de58c9e63, parent of e7a36e4715c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111071
Bug ID: 111071
Summary: gcc.target/aarch64/sve/acle/aarch64-sve-acle-asm.exp
has new failures since commit e7a36e4715c7
Product: gcc
Version: unknown
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106537
--- Comment #6 from Eric Gallager ---
Would it be possible to add a fix-it hint to this warning, too, while you're at
it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111060
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111060
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:27d0cfcb2b33de07351d9cb26f62d04d7416716c
commit r14-3329-g27d0cfcb2b33de07351d9cb26f62d04d7416716c
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111049
--- Comment #2 from Mark Pizzolato ---
> Looks like this is fixed for GCC 11.
The latest Raspberry Pi OS is still packaging gcc 10.2.1.
How was this tested with gcc 11?
Was there a specific change that addressed the problem? If so, can we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86646
Arthur O'Dwyer changed:
What|Removed |Added
CC||arthur.j.odwyer at gmail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065
--- Comment #5 from Tommy Murphy ---
Thanks for the comments Palmer and Kito.
However I'm still a bit confused. Is it the case that the multilib patterns
(for the "base" lib and reuse patterns) are interpreted/used differently in the
context
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59660
--- Comment #17 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #12)
> (In reply to Jan Hubicka from comment #4)
> > > Not all testcases can be handled at gimplification time IIRC. Which
> > > means "testcases welcome" first, so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111070
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
:8899
0xfbfefd ifcombine_ifandif(basic_block_def*, bool, basic_block_def*, bool,
bool)
../../trunk.year/gcc/tree-ssa-ifcombine.cc:0
$ ~/gcc/results/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/home/dcb38/gcc/results/bin/gcc
COLLECT_LTO_WRAPPER=/home/dcb38/gcc/results.20230818.asan.ubsan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111069
Jakub Jelinek changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111069
--- Comment #3 from Jakub Jelinek ---
Yes, though this PR has more info.
grep 1[ik]1[jl] pr111069-2.s | grep :
_ZZ6freddyvEDC1i1jE:
_ZGVZ6freddyvEDC1i1jE:
_ZZ6freddyvEDC1k1lE:
_ZGVZ6freddyvEDC1k1lE:
_ZZ6freddyvEDC1i1jE_0:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111069
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111069
--- Comment #1 from Jakub Jelinek ---
Apparently my fault as I've done r10-720-gb7f0df71a9de2354fcb7 which enabled
it,
but am not really sure what is the correct mangling.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111069
Bug ID: 111069
Summary: Mangling of static structured bindings
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110349
Jakub Jelinek changed:
What|Removed |Added
Attachment #55757|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #7 from joseph at codesourcery dot com ---
There shouldn't be such a thing as an unsupported constant payload; both
__builtin_nan and __builtin_nans should rather be made consistent with
parsing of payloads by glibc's nan
x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-3320-20230818093638-g7f8d730a563-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20230818 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111067
Andrew Pinski changed:
What|Removed |Added
Component|c++ |testsuite
--- Comment #1 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111066
--- Comment #2 from Andrew Pinski ---
The wording of the warning is different from what dg-warning directive in the
testcase expects.
diff --git a/gcc/testsuite/g++.dg/special/initpri3.C
b/gcc/testsuite/g++.dg/special/initpri3.C
index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110070
Francois-Xavier Coudert changed:
What|Removed |Added
CC||fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111067
Francois-Xavier Coudert changed:
What|Removed |Added
Known to fail||14.0
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111067
Bug ID: 111067
Summary: g++.dg/opt/icf{1,2,3}.C tests fail on darwin
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111066
Francois-Xavier Coudert changed:
What|Removed |Added
Ever confirmed|0 |1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111066
Bug ID: 111066
Summary: g++.dg/special/initpri3.C fails on darwin
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111023
--- Comment #6 from CVS Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:4123b5609da53c8f8ac01c90aef127ad6375e9df
commit r14-3327-g4123b5609da53c8f8ac01c90aef127ad6375e9df
Author: Uros Bizjak
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065
--- Comment #4 from Kito Cheng ---
I guess I skip too much detail here, the multilib for linux isn’t really honor
to the reause rule in the multilib config file for a while.
That just control how multilib build, e.g. build ilp32 with which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110349
--- Comment #6 from Jason Merrill ---
(In reply to Jakub Jelinek from comment #4)
> "A member shall not be declared twice in the member-specification, except
> that"
> and nothing mentioning the name-independent exception in either case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111040
--- Comment #3 from qinzhao at gcc dot gnu.org ---
a summary of the discussion:
We have two different sources to get the size information for subobjects:
A. The TYPE information of the subobject in the IR;
B. The initialization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065
palmer at gcc dot gnu.org changed:
What|Removed |Added
CC||palmer at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111040
--- Comment #2 from qinzhao at gcc dot gnu.org ---
the discussion on this bug is at:
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627631.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93176
Peter Bergner changed:
What|Removed |Added
URL|https://gcc.gnu.org/piperma |https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065
--- Comment #2 from Tommy Murphy ---
Thanks @Kito Cheng - but I don't really understand how your comment relates to
the specific issue of the t-linux-multilib reuse "mappings" being incorrect
(and possibly the reverse of what was originally
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110753
Aldy Hernandez changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110753
--- Comment #4 from CVS Commits ---
The master branch has been updated by Aldy Hernandez :
https://gcc.gnu.org/g:53fcd3bdbc9104a8acdc79134d8d272d7eead0fd
commit r14-3326-g53fcd3bdbc9104a8acdc79134d8d272d7eead0fd
Author: Aldy Hernandez
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110349
--- Comment #5 from Jakub Jelinek ---
Also, is the structured binding in
void corge ()
{
static int a[2];
static auto [_, _] = a;
}
inhabitating namespace scope (so it is correct to reject it? clang does, the
WIP patch does as well).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110349
Jakub Jelinek changed:
What|Removed |Added
Attachment #55725|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065
Kito Cheng changed:
What|Removed |Added
Version|og13 (devel/omp/gcc-13) |14.0
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111060
--- Comment #3 from Sergei Trofimovich ---
The patch fixed gcc buid on i686-linux for me. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111048
--- Comment #8 from prathamesh3492 at gcc dot gnu.org ---
(In reply to rsand...@gcc.gnu.org from comment #7)
> = ((q1 & 0) == 0) ? VECTOR_CST_NPATTERNS (arg0)
> : VECTOR_CST_NPATTERNS (arg1);
>
> should be q1 &
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109253
--- Comment #2 from Jose E. Marchesi ---
A patch to fix this was sent
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627864.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48783
Jose E. Marchesi changed:
What|Removed |Added
CC||jemarch at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #6 from Xi Ruoyao ---
(In reply to jos...@codesourcery.com from comment #5)
> We should absolutely *not* generate calls to a non-existent function
> "nans" based on a long-obsolescent standard proposal. The modern way to
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065
Bug ID: 111065
Summary: [RISCV] t-linux-multilib specifies incorrect multilib
reuse patterns
Product: gcc
Version: og13 (devel/omp/gcc-13)
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #5 from joseph at codesourcery dot com ---
We should absolutely *not* generate calls to a non-existent function
"nans" based on a long-obsolescent standard proposal. The modern way to
generate a signaling NaN with given payload,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111064
--- Comment #2 from Richard Biener ---
might be - parest is the test that improved with emulated gather on Zen.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111019
Richard Biener changed:
What|Removed |Added
Summary|[12/13/14 Regression] |[12/13 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111019
--- Comment #10 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:745ec2135aabfbe2c0fb7780309837d17e8986d4
commit r14-3325-g745ec2135aabfbe2c0fb7780309837d17e8986d4
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111060
--- Comment #2 from Jonathan Wakely ---
Created attachment 55756
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55756=edit
Revert pre-C++23 support for 16-bit float types
I'll test this patch as soon as I can get an i686 system set up.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111064
--- Comment #1 from Jan Hubicka ---
Maybe
commit 3064d1f5c48cb6ce1b4133570dd08ecca8abb52d
Author: liuhongt
Date: Thu Aug 10 11:41:39 2023 +0800
Software mitigation: Disable gather generation in vectorization for GDS
affected Intel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111010
--- Comment #7 from Richard Biener ---
diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
index f3a3305ac4f..d38b9d764d8 100644
--- a/gcc/config/i386/i386.md
+++ b/gcc/config/i386/i386.md
@@ -11511,7 +11511,7 @@
})
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111010
Richard Biener changed:
What|Removed |Added
CC||uros at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111064
Bug ID: 111064
Summary: 5-10% regression of parest on icelake between
g:d073e2d75d9ed492de9a8dc6970e5b69fae20e5a (Aug 15
2023) and g:9ade70bb86c8744f4416a48bb69cf4705f00905a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111060
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111023
--- Comment #5 from Richard Biener ---
So for gcc.dg/vect/pr65947-7.c the main difference is that aarch64 succeeds
with
t.c:12:21: note: * Re-trying analysis with vector mode V4HI
t.c:12:21: note: === vect_analyze_data_refs ===
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111010
Rainer Orth changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111063
Bug ID: 111063
Summary: [UBSAN] Implement "-inf is outside the range of
representable values of type 'unsigned long'" to be on
par with Clang
Product: gcc
f-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20230818 (experimental) (GCC)
linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-3320-20230818093638-g7f8d730a563-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20230818 (exp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111021
Kewen Lin changed:
What|Removed |Added
Summary|[14 Regression] Serial |[14 Regression] Serial
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111021
--- Comment #18 from CVS Commits ---
The master branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:8353b9c5f5af0e65cb04fcbb7325d6a566006cd4
commit r14-3322-g8353b9c5f5af0e65cb04fcbb7325d6a566006cd4
Author: Kewen Lin
Date: Fri Aug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111060
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111023
--- Comment #4 from Uroš Bizjak ---
Created attachment 55753
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55753=edit
Proposed patch
Patch that implements zero/sign extend of <= 64byte vector modes to a wider
vector mode also for SSE2.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111023
Uroš Bizjak changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111060
Bug ID: 111060
Summary: [14 Regression] i686-linux bootstrap failure:
i686-unknown-linux-gnu/libstdc++-v3/include/limits:198
6:1: error: SSE register return with SSE2 disabled
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111048
--- Comment #7 from rsandifo at gcc dot gnu.org
---
= ((q1 & 0) == 0) ? VECTOR_CST_NPATTERNS (arg0)
: VECTOR_CST_NPATTERNS (arg1);
should be q1 & 1 :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111048
--- Comment #6 from prathamesh3492 at gcc dot gnu.org ---
Sorry for the breakage, I will take a look.
Thanks,
Prathamesh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78790
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #4 from chenxiaolong ---
(In reply to chenxiaolong from comment #3)
> //test.c
> #include
>
> int main(void)
> {
> _Float128 ret=__builtin_nansf128("NAN");
> printf("ret=%Lf\n",ret);
>
> return 0;
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111043
--- Comment #4 from David Binderman ---
$ git bisect bad ef28aadad6e5cff3
ef28aadad6e5cff3d7494f3c97d435a6579a2e2d is the first bad commit
commit ef28aadad6e5cff3d7494f3c97d435a6579a2e2d
Author: Jan Hubicka
Date: Thu Jul 20 15:41:39 2023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
chenxiaolong changed:
What|Removed |Added
CC||chenxiaolong at loongson dot cn
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111043
--- Comment #3 from David Binderman ---
I have a bisection running. Current range is g:23ad5ed7432bea7c ..
g:85a4e4f93ff251f2,
some 8 commits.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111048
--- Comment #5 from Richard Biener ---
Worked around on x86_64-linux, I think the code that's now not reached is still
buggy somehow - deferring to Pratamesh for this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111048
--- Comment #4 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:f5f47cc1ce75b00427756939a2dab94d3d125f6a
commit r14-3319-gf5f47cc1ce75b00427756939a2dab94d3d125f6a
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
--- Comment #2 from Andrew Pinski ---
Newer version of that paper:
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1011.htm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111059
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111043
--- Comment #2 from David Binderman ---
Reduced code is
i_1;
*func_14_ptr_4;
short func_14_s_8;
func_14() {
int i_2;
int *ptr_6 = _1;
*ptr_6 = 8;
for (; *ptr_6 <= 9; *ptr_6 += 1)
i_2 = *ptr_6;
func_14_s_8 = 1;
for (;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111059
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-18
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111059
--- Comment #1 from Andrew Pinski ---
(gdb) p debug_tree(*expr_p)
unit-size
align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x776215e8 precision:32 min max
pointer_to_this >
readonly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111051
--- Comment #5 from Sergei Trofimovich ---
The change fixed highway-1.0.6 build for me. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111059
Bug ID: 111059
Summary: ICE: in gimplify_expr, at gimplify.cc:17253
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111051
--- Comment #4 from CVS Commits ---
The master branch has been updated by Haochen Jiang :
https://gcc.gnu.org/g:68f7cb6cf9e8b9f2254855507f3b479552adda5f
commit r14-3318-g68f7cb6cf9e8b9f2254855507f3b479552adda5f
Author: Haochen Jiang
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111048
Richard Biener changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83662
--- Comment #14 from Jonathan Wakely ---
This bug report is only about declaring it in namespace std if it's already
available in the global namespace in stdlib.h
If your OS doesn't provide it in stdlib.h then that's not a gcc bug, and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-18
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111058
Bug ID: 111058
Summary: __builtin_nans (and its friends) compiles to an
external call to __builtin_nans for unsupported tag
Product: gcc
Version: 14.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83662
--- Comment #13 from Jonathan Wakely ---
Snow Leopard is *ancient*, it didn't support aligned_alloc. According to Bug
92143 you need macOS 10.15 i.e. Catalina.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83662
--- Comment #12 from Jonathan Wakely ---
See Bug 69680
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100080
--- Comment #3 from Andrew Pinski ---
I am thinking we should mark this as won't fix.
In VRP2 we have:
[local count: 105119324]:
_7 = l_20(D) | 1;
_8 = (unsigned int) _7;
if (_8 <= 1)
goto ; [41.00%]
else
goto ;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111050
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111047
--- Comment #4 from Richard Biener ---
unfortunately inform() wasn't designed for this, I suppose using warning()
would have been better here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99987
Andrew Pinski changed:
What|Removed |Added
Known to fail||7.5.0
--- Comment #6 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93176
--- Comment #12 from Jiu Fu Guo ---
Thanks a lot for asking!
The patch which handles this is submitted at:
https://gcc.gnu.org/pipermail/gcc-patches/2023-July/623519.html
I would ping this patch again. If ok, I will commit to trunk.
(And the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99987
--- Comment #5 from Andrew Pinski ---
Note turning off ivopts, DOM3 can't optimize away the call either ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111051
--- Comment #3 from Haochen Jiang ---
See patch:
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627829.html
1 - 100 of 102 matches
Mail list logo
