https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102182
Hongtao.liu changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102182
Bug ID: 102182
Summary: Runtime error for
gcc.dg/torture/fp-int-convert-float16.c
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83060
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |7.4
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96280
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102166
--- Comment #12 from CVS Commits ---
The releases/gcc-11 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:259945a0a4880b66f93f71eebe70f78c91e02d5e
commit r11-8953-g259945a0a4880b66f93f71eebe70f78c91e02d5e
Author: liuhongt
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102166
--- Comment #11 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:de6795bbf58c7085933a1f86a88d8193ea72e26b
commit r12-3323-gde6795bbf58c7085933a1f86a88d8193ea72e26b
Author: liuhongt
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101157
--- Comment #6 from seurer at gcc dot gnu.org ---
The stack limit test case mostly has worked since just after this was opened
(one short span where it failed again) but I don't know what fixed it. The
other test case has worked fine since just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24049
Bug 24049 depends on bug 21805, which changed state.
Bug 21805 Summary: loop optimizers are not GC safe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21805
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21805
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101157
--- Comment #5 from Peter Bergner ---
Are the ppc tests and s390 bootstrap still broken?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97142
--- Comment #15 from luoxhu at gcc dot gnu.org ---
Patch updated:
https://gcc.gnu.org/pipermail/gcc-patches/2021-September/578740.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101849
Peter Bergner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101849
--- Comment #8 from CVS Commits ---
The releases/gcc-10 branch has been updated by Peter Bergner
:
https://gcc.gnu.org/g:de2114d2f1792beae55dccb512c4c521b934e72b
commit r10-10091-gde2114d2f1792beae55dccb512c4c521b934e72b
Author: Peter Bergner
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
Andrew Pinski changed:
What|Removed |Added
Known to fail||11.2.0
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 98908, which changed state.
Bug 98908 Summary: [11 Regression] arithmetic involving struct members into
operating on the entire struct fails at -O3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
Andrew Pinski changed:
What|Removed |Added
Summary|Failure to optimize |[11 Regression] arithmetic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
--- Comment #9 from Gabriel Ravier ---
PS: I had missed at the time that the bug wasn't present in GCC 10/9/8 though,
so perhaps it should be considered as having been a GCC 11 regression that got
fixed in trunk ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
--- Comment #8 from Gabriel Ravier ---
Well, fixing a bug filed in 2021 in GCC 9 seems quite hard. Are you confused
about the nature of the bug ? The first example in the description *is* the one
whose optimization the bug is about, and it is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 98908, which changed state.
Bug 98908 Summary: Failure to optimize arithmetic involving struct members into
operating on the entire struct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88697
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82477
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |8.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66831
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53665
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53981
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53981
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |4.8.0
--- Comment #1 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
--- Comment #6 from Gabriel Ravier ---
Also the second example wasn't misoptimized, on the contrary it was the most
reasonable portable function I could write that would work equivalently to the
first *and* that GCC would optimize ideally.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
--- Comment #5 from Gabriel Ravier ---
It may have been doing it in GCC 8 (and 9, and 10), but it didn't in 11, and
presumably this was also the case in trunk back in February.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
--- Comment #4 from Andrew Pinski ---
The second function is able to be optimized since GCC 9 with bswap producing:
load_dst_16 = MEM [(unsigned char *)];
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
Andrew Pinski changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #3 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41666
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |4.6.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908
--- Comment #2 from Gabriel Ravier ---
This seems to have been fixed in trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100917
--- Comment #8 from sandra at gcc dot gnu.org ---
There is a workaround for this included in commit
93b6b2f614eb692d1d8126ec6cb946984a9d01d7
that doesn't fully solve the problem: when "long double" and "float128" are
different types with the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100914
sandra at gcc dot gnu.org changed:
What|Removed |Added
CC||sandra at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68969
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98874
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-09-02
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90720
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100914
--- Comment #7 from CVS Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:93b6b2f614eb692d1d8126ec6cb946984a9d01d7
commit r12-3321-g93b6b2f614eb692d1d8126ec6cb946984a9d01d7
Author: Sandra Loosemore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100917
--- Comment #7 from CVS Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:93b6b2f614eb692d1d8126ec6cb946984a9d01d7
commit r12-3321-g93b6b2f614eb692d1d8126ec6cb946984a9d01d7
Author: Sandra Loosemore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100907
--- Comment #8 from CVS Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:93b6b2f614eb692d1d8126ec6cb946984a9d01d7
commit r12-3321-g93b6b2f614eb692d1d8126ec6cb946984a9d01d7
Author: Sandra Loosemore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100916
--- Comment #4 from CVS Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:93b6b2f614eb692d1d8126ec6cb946984a9d01d7
commit r12-3321-g93b6b2f614eb692d1d8126ec6cb946984a9d01d7
Author: Sandra Loosemore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100911
--- Comment #4 from CVS Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:93b6b2f614eb692d1d8126ec6cb946984a9d01d7
commit r12-3321-g93b6b2f614eb692d1d8126ec6cb946984a9d01d7
Author: Sandra Loosemore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100915
--- Comment #4 from CVS Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:93b6b2f614eb692d1d8126ec6cb946984a9d01d7
commit r12-3321-g93b6b2f614eb692d1d8126ec6cb946984a9d01d7
Author: Sandra Loosemore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102181
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=96791
--- Comment #25 from Segher Boessenkool ---
(In reply to Peter Bergner from comment #24)
> (In reply to Segher Boessenkool from comment #23)
> > Anyway, patch in testing.
>
> Did your patch fix the problem or do we need to take another run at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97142
--- Comment #14 from Segher Boessenkool ---
(In reply to Peter Bergner from comment #13)
> (In reply to luoxhu from comment #12)
> > Patch submitted:
> >
> > https://gcc.gnu.org/pipermail/gcc-patches/2021-April/568143.html
>
> Looks like Will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95969
Andrew Pinski changed:
What|Removed |Added
Attachment #51397|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96791
--- Comment #24 from Peter Bergner ---
(In reply to Segher Boessenkool from comment #23)
> Anyway, patch in testing.
Did your patch fix the problem or do we need to take another run at this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102181
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97142
Peter Bergner changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102181
--- Comment #4 from Jonathan Wakely ---
https://en.cppreference.com/w/cpp/iterator/advance says "InputIt must meet the
requirements of LegacyInputIterator."
https://en.cppreference.com/w/cpp/named_req/InputIterator gives a sample
concept you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102181
--- Comment #3 from Raffael Casagrande ---
thanks for the fast response. I can switch over to std::ranges::advance.
MSVC compiles the snippet without problems...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102181
--- Comment #2 from Jonathan Wakely ---
You need to use std::ranges::advance here, because iota_view is "special".
The reason std::advance doesn't work is that the type of v.begin() does not
meet the Cpp17InputIterator requirements, because
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102181
--- Comment #1 from Jonathan Wakely ---
It compiles with -std=gnu++20 but not -std=c++20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102173
Andrew Pinski changed:
What|Removed |Added
Keywords||patch
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95969
--- Comment #7 from Andrew Pinski ---
Testcases that fail:
gcc.target/aarch64/vmov_n_1.c
at -O1:t.c: In function ‘test_vmov_n_f32’:
t.c:165:10: error: missing definition
for SSA_NAME: .MEM_161 in statement:
# VUSE <.MEM_161>
_162 =
::ranges::iota_view(static_cast(0),
static_cast(100));
auto b = v.begin();
std::advance(b, static_cast(1));
}
gcc version: 12.0.0 20210901 (experimental)
Error messages:
/opt/compiler-explorer/gcc-trunk-20210902/include/c++/12.0.0/bits/stl_iterator_base_funcs.h:
In instantiation of 'constexpr void
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102180
Bug ID: 102180
Summary: Improve checking of assume size array spec
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102173
--- Comment #3 from Andrew Pinski ---
(In reply to Christophe Lyon from comment #2)
> Appeared after r12-3278 g:823685221de986afb729910a6f2237f07a377f17
Yes caused by r12-3278.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 102179, which changed state.
Bug 102179 Summary: ICE during dom: tree check: expected ssa_name, have
integer_cst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102179
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102152
Andrew Pinski changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102179
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102179
Bug ID: 102179
Summary: ICE during dom: tree check: expected ssa_name, have
integer_cst
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101849
--- Comment #7 from CVS Commits ---
The releases/gcc-11 branch has been updated by Peter Bergner
:
https://gcc.gnu.org/g:585667735e9fb7a38357a84d4d25206a8ccec576
commit r11-8951-g585667735e9fb7a38357a84d4d25206a8ccec576
Author: Peter Bergner
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93834
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|anlauf at gcc dot gnu.org |unassigned at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102154
--- Comment #14 from Segher Boessenkool ---
(In reply to Jonathan Wakely from comment #13)
> Is this also the cause of several libstdc++ FAILs on ppc64le?
Yes.
I have asked for reversion of g:d2874d905647:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102177
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:dba1ab212292839572fda60df00965e094a11252
commit r12-3317-gdba1ab212292839572fda60df00965e094a11252
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71934
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87198
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102154
--- Comment #13 from Jonathan Wakely ---
Is this also the cause of several libstdc++ FAILs on ppc64le?
/home/jwakely/build/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/bits/random.h:2936:
error: unrecognizable insn:
(insn 11 10 12 2 (set
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96127
--- Comment #3 from Jonathan Wakely ---
Andreas, do you need to backport this, or should it be closed as fixed for
11.0?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96615
--- Comment #3 from Gabriel Ravier ---
It seems to be optimized into nothing as of right now
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102178
Bug ID: 102178
Summary: SPECFP 2006 470.lbm regressions on AMD Zen CPUs after
r12-897-gde56f95afaaa22
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95187
--- Comment #3 from Gabriel Ravier ---
Seems to be fixed since GCC 11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17506
--- Comment #37 from CVS Commits ---
The master branch has been updated by Martin Sebor :
https://gcc.gnu.org/g:9695e1c23be5b5c55d572ced152897313ddb96ae
commit r12-3315-g9695e1c23be5b5c55d572ced152897313ddb96ae
Author: Martin Sebor
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37182
--- Comment #6 from CVS Commits ---
The master branch has been updated by Martin Sebor :
https://gcc.gnu.org/g:9695e1c23be5b5c55d572ced152897313ddb96ae
commit r12-3315-g9695e1c23be5b5c55d572ced152897313ddb96ae
Author: Martin Sebor
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102177
--- Comment #2 from Jakub Jelinek ---
Created attachment 51406
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51406=edit
gcc12-pr102177.patch
Untested patch to remove the warning and just use maximum for success if weaker
than failure
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102177
Jakub Jelinek changed:
What|Removed |Added
CC||dje at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61359
--- Comment #7 from Larkin Nickle ---
For anyone finding this in the future, I'm guessing 32-bit builds of GCC on
HP-UX+PA-RISC were just broken for a while. Building 5.5.0 with libquadmath
enabled worked fine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102177
Jakub Jelinek changed:
What|Removed |Added
Last reconfirmed||2021-09-02
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102177
Bug ID: 102177
Summary: Implement C++17 P0418R2
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102162
--- Comment #31 from deller at gmx dot de ---
Richard suggested that adding a compiler optimization barrier (__asm__ ("" :
"+r" (__pptr))) might fix the problem.
I tested the attached patch and it works nicely.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102162
--- Comment #30 from deller at gmx dot de ---
Created attachment 51405
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51405=edit
Linux kernel patch to add compiler optimization barrier
Linux kernel boots sucessfully with this patch on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71934
Iain Sandoe changed:
What|Removed |Added
CC||iains at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96286
--- Comment #8 from Jonathan Wakely ---
(In reply to Jason Merrill from comment #5)
> I get better results if I add the static_assert to __uninitialized_copy_a,
> so we hit it before queuing any further instantiations.
I actually need to check
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102176
--- Comment #2 from Richard Biener ---
Created attachment 51404
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51404=edit
patch
This brute-force approach of re-computing something like PURE_SLP_STMT minus
the set of defs used in extern
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102173
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96286
--- Comment #7 from Jason Merrill ---
Created attachment 51403
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51403=edit
patch to stop compiling a function after static_assert
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96286
--- Comment #6 from Jason Merrill ---
Created attachment 51402
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51402=edit
patch to silence constexpr issues with erroneous functions
Here are a couple of other commits I tried to reduce error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102176
--- Comment #1 from Richard Biener ---
So in this case we have _2 = _1 * a_11(D) still pure_slp even though it does
not participate in any vectorized SLP node.
Unfortunately marking of PURE_SLP_STMTs happens before analyzing operations
(the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102176
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102176
Bug ID: 102176
Summary: BB SLP scalar costing is off with extern promoted
nodes
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88085
--- Comment #21 from rguenther at suse dot de ---
On Thu, 2 Sep 2021, petro.karashchenko at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88085
>
> --- Comment #20 from Petro Karashchenko
> ---
> I just checked next
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102175
Bug ID: 102175
Summary: Error comparing the pointers on static class fields in
static_assert
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101918
--- Comment #25 from Rimvydas (RJ) ---
Created attachment 51401
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51401=edit
testcase with ice deep in rtl code for sign extend
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102174
Bug ID: 102174
Summary: Unused result of undefined behavior arithmetic is
accepted during constant evaluation
Product: gcc
Version: 12.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101918
--- Comment #24 from Rimvydas (RJ) ---
Created attachment 51400
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51400=edit
alog() intrinsic testcases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101918
--- Comment #23 from Rimvydas (RJ) ---
Created attachment 51399
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51399=edit
additional patch, for previous behavior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88085
--- Comment #20 from Petro Karashchenko
---
I just checked next case
typedef int tolerant_int __attribute__((aligned(1)));
tolerant_int var;
int foo(void)
{
return var;
}
--
arm-none-eabi-gcc -save-temps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101918
--- Comment #22 from Rimvydas (RJ) ---
Created attachment 51398
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51398=edit
proposed patch
1 - 100 of 166 matches
Mail list logo
