https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115863
--- Comment #18 from Hu Lin ---
(In reply to Uroš Bizjak from comment #17)
> (In reply to Hongtao Liu from comment #16)
> > > Unfortunately, x86 has no vector mode .SAT_TRUNC instruction.
> > No, AVX512 supports both signed and unsigned saturati
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115950
--- Comment #3 from ktkachov at gcc dot gnu.org ---
(In reply to Andrew Pinski from comment #2)
> Hmm actually there are patterns there but they are not matching. Something
> seems to be going wrong with define_insn_and_rewrite ...
The MD patter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115766
--- Comment #8 from Sam James ---
Are you sure the reduced one is accurate? For me, it behaves the same with
-O0..-O3 for GCC. For Clang, it has the same behaviour as GCC with -O0, and
"passes" with > -O0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115868
--- Comment #3 from GCC Commits ---
The releases/gcc-14 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:c58bede01c06c84f0b36881fafd1e5d6456a38f4
commit r14-10443-gc58bede01c06c84f0b36881fafd1e5d6456a38f4
Author: Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105769
Richard Biener changed:
What|Removed |Added
Known to fail||12.4.0, 13.3.0, 14.1.0
Known to w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115382
--- Comment #8 from GCC Commits ---
The releases/gcc-14 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:bf64404280a90715d1228edef0d5756e81635a64
commit r14-10444-gbf64404280a90715d1228edef0d5756e81635a64
Author: Robin Dapp
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114908
--- Comment #10 from Matthias Kretz (Vir) ---
(In reply to Richard Biener from comment #9)
> One issue with
>
> V load3(const unsigned long* ptr)
> {
> V ret = {};
> __builtin_memcpy(&ret, ptr, 3 * sizeof(unsigned long));
>
> is that we ca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115964
Bug ID: 115964
Summary: GCC accepts invalid program with explicit object
member function overloads
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #67 from uecker at gcc dot gnu.org ---
(In reply to Andrew Church from comment #66)
> (In reply to Andrew Church from comment #65)
> > As one of the advocates for this behavior, it stems (at least in my case)
> > from pre-C23 code in w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105769
--- Comment #18 from Richard Biener ---
(In reply to Richard Biener from comment #17)
> I'm not actually seeing the problematic use of the hoisted address - the
> address value itself is stored and the trick of looking at SSA uses defs to
> pick
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104515
--- Comment #9 from Richard Biener ---
I think not re-emitting the clobber on the exit might be OK semantically - it's
at most a missed optimization for a store. I think it's also OK for the
stack slot sharing logic as any object becoming live
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96717
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96881
Bug 96881 depends on bug 96717, which changed state.
Bug 96717 Summary: -flifetime-dse=2 breaks webkit-gtk-2.28.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96717
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96722
Bug 96722 depends on bug 96717, which changed state.
Bug 96717 Summary: -flifetime-dse=2 breaks webkit-gtk-2.28.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96717
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96721
Bug 96721 depends on bug 96717, which changed state.
Bug 96717 Summary: -flifetime-dse=2 breaks webkit-gtk-2.28.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96717
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104515
--- Comment #10 from Richard Biener ---
Testcase from PR96717, also fixed with my patch in testing.
#include
void pop_many(std::vector& v, unsigned n) {
for (unsigned i = 0; i < n; ++i) {
v.pop_back();
}
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115868
Richard Biener changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 115868, which changed state.
Bug 115868 Summary: [14 Regression] ICE: in exact_div, at poly-int.h:2156
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115868
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115382
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 115382, which changed state.
Bug 115382 Summary: Wrong code with in-order conditional reduction and masked
loops
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115382
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110445
Richard Biener changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115958
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #68 from Andrew Church ---
(In reply to uecker from comment #67)
> But also the library could switch to "discard" or add a condition that the
> lets the user of the library choose it.
The issue here is that the library user has no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114908
--- Comment #11 from rguenther at suse dot de ---
On Wed, 17 Jul 2024, mkretz at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114908
>
> --- Comment #10 from Matthias Kretz (Vir) ---
> (In reply to Richard Biener from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #69 from Jonathan Wakely ---
(In reply to Andrew Church from comment #68)
> I do agree that "(void)" is very idiomatic, and something like a [[discard]]
> statement attribute (which would silence warnings for both
> __attribute__((wur
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115960
--- Comment #4 from Jonathan Wakely ---
> The problem seems to be that, despite passing "-std=c++17", it doesn't use
> c++17
> header files for the Optional identifier.
Why should it? The name "Optional" is not part of any C++ standard.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115965
Bug ID: 115965
Summary: Stack smashing depending on order of declaration
Product: gcc
Version: 14.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115965
--- Comment #1 from Nathan Teodosio ---
Created attachment 58690
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58690&action=edit
Preprocessed file (compressed with Gzip)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115965
--- Comment #2 from Nathan Teodosio ---
Created attachment 58691
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58691&action=edit
Source file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115959
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115954
--- Comment #12 from Wilco ---
This came out of the AArch64 Atomic ABI design work:
https://github.com/ARM-software/abi-aa/pull/256
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115527
--- Comment #11 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:8b5919bae11754f4b65a17e63663d3143f9615ac
commit r15-2090-g8b5919bae11754f4b65a17e63663d3143f9615ac
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115958
--- Comment #1 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:74bcef4cf16b35fe64767c1e8e529bdd229841a3
commit r15-2091-g74bcef4cf16b35fe64767c1e8e529bdd229841a3
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
--- Comment #5 from Hongtao Liu ---
I saw pass_eras optimize BIT_FIELD_REF of big memory into load from small
memory
Created a replacement for D.161366 offset: 0, size: 64: SR.20D.170101
Created a replacement for D.161366 offset: 64, size: 64:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
--- Comment #6 from rguenther at suse dot de ---
On Wed, 17 Jul 2024, liuhongt at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114966
>
> --- Comment #5 from Hongtao Liu ---
> I saw pass_eras optimize BIT_FIELD_REF of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #70 from Andrew Church ---
(In reply to Jonathan Wakely from comment #69)
> Maybe you want:
>
> [[maybe_unused]] auto _ = foo();
If I could apply that attribute to the value itself, i.e.:
[[maybe_unused]] foo();
that woul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115887
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115951
--- Comment #5 from Matthias Klose ---
a new build survived on x86_64-linux-gnu. will wait on the results on other
architectures.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115966
Bug ID: 115966
Summary: [15 Regression] Miscompilation of 403.gcc with -Ofast
-march=native on x86_64
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115966
Filip Kastl changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115959
--- Comment #3 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:24689b84b8ec0c74c2b9a72ec4fb467069806bda
commit r15-2093-g24689b84b8ec0c74c2b9a72ec4fb467069806bda
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115959
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115966
--- Comment #1 from Richard Biener ---
I think we have a few other gcc miscompiles now (but from SPEC CPU 2017), so
this one is probably related. Does -fno-strict-aliasing fix it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #24 from Julian Waters ---
Thanks for the patch, I've been looking through it these past few days. While
the simpler parts of it I can manage, I'm struggling terribly with
understanding the RTL shifting code in legitimize_tls_address
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #71 from Petr Skocik ---
An Ignore macro that works everywhere where a (void) cast syntactically works
(i.e., even on void types for whatever reason) is easy:
#define IGN$(Val) (__extension__({ \
__auto_type IGN$ = _Generic((typ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115966
--- Comment #2 from Filip Kastl ---
(In reply to Richard Biener from comment #1)
> I think we have a few other gcc miscompiles now (but from SPEC CPU 2017), so
> this one is probably related. Does -fno-strict-aliasing fix it?
Just tested it, -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115967
Bug ID: 115967
Summary: ubsan: shift exponent 64 is too large for 64-bit type
HOST_WIDE_INT in ext-dce.cc on line 600 since
r15-1901-g98914f9eba5f19
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115965
--- Comment #3 from Richard Biener ---
I think that's somewhat expected.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115965
--- Comment #4 from Jonathan Wakely ---
Jut to be clear on the bug being reported, are you expecting the error to be
detected in all cases?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115965
--- Comment #5 from Nathan Teodosio ---
In none of them. Or am I overlooking a buffer overrun here? Also with Clang I
get no stack smashing even with -fstack-protector-all.
In any case I fail to see why that would be dependent on which of the a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115963
--- Comment #2 from Jiang An ---
> The question becomes is that an oversight of P3144R2 or not and should a null
> pointer
> constant be valid always since that was never undefined or even had a chance
> of being
> undefined.
CWG2392 (https:/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84246
Andre Vehreschild changed:
What|Removed |Added
Status|ASSIGNED|WAITING
--- Comment #9 from Andre Ve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106800
--- Comment #2 from Richard Biener ---
I have something in the works.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #72 from Segher Boessenkool ---
The correct way to not get the warning about unused results, is to _do_ use
the function return value, of course, as I explained in #c18 already.
Like:
if (foo()) {
/* The return value of foo can be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #73 from Zdenek Sojka ---
See MISRA C:2012 Rule 17.7:
"... If the return value of a function is intended not to be used explicitly,
it should be cast to the void type. ..."
It would be helpful if gcc could be used to write MISRA-com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114440
--- Comment #2 from GCC Commits ---
The master branch has been updated by Feng Xue :
https://gcc.gnu.org/g:178cc419512f7e358f88dfe2336625aa99cd7438
commit r15-2096-g178cc419512f7e358f88dfe2336625aa99cd7438
Author: Feng Xue
Date: Wed May 29
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114440
--- Comment #3 from GCC Commits ---
The master branch has been updated by Feng Xue :
https://gcc.gnu.org/g:db3c8c9726d0bafbb9f85b6d7027fe83602643e7
commit r15-2097-gdb3c8c9726d0bafbb9f85b6d7027fe83602643e7
Author: Feng Xue
Date: Wed May 29
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #74 from Florian Weimer ---
(In reply to Zdenek Sojka from comment #73)
> See MISRA C:2012 Rule 17.7:
> "... If the return value of a function is intended not to be used
> explicitly, it should be cast to the void type. ..."
>
> It
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115968
Bug ID: 115968
Summary: g++ 12 and above incorrectly optimize the code with
Eigen (-O2 or -O1)
Product: gcc
Version: 14.1.1
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115968
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115968
--- Comment #2 from Andrew Pinski ---
See C++11 and the auto keyword section of
https://eigen.tuxfamily.org/dox/TopicPitfalls.html
The problem is that eval() returns a temporary object (in this case a MatrixXd)
which is then referenced by the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #75 from Zdenek Sojka ---
(In reply to Florian Weimer from comment #74)
> (In reply to Zdenek Sojka from comment #73)
> > See MISRA C:2012 Rule 17.7:
> > "... If the return value of a function is intended not to be used
> > explicitl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115968
--- Comment #3 from HanatoK ---
(In reply to Andrew Pinski from comment #2)
> See C++11 and the auto keyword section of
> https://eigen.tuxfamily.org/dox/TopicPitfalls.html
>
>
> The problem is that eval() returns a temporary object (in this c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #76 from Jakub Jelinek ---
(void) casts not quieting the warning was an intentional request when the
warning has been added, I really don't think it is a good idea to change that.
The fact that clang people can't properly implement Pe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115876
Andrew Pinski changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115967
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 115967, which changed state.
Bug 115967 Summary: ubsan: shift exponent 64 is too large for 64-bit type
HOST_WIDE_INT in ext-dce.cc on line 600 since r15-1901-g98914f9eba5f19
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111890
--- Comment #7 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:247335823f420eb1dd56f4bf32ac78d441f5ccc2
commit r15-2098-g247335823f420eb1dd56f4bf32ac78d441f5ccc2
Author: Patrick Palka
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #77 from Andrew Church ---
(In reply to Segher Boessenkool from comment #72)
> if (foo()) {
> /* The return value of foo can be ignored here because X and Y. */
> }
This is just another idiom, with "if(){}" replacing "(void)"; it
eaa8
READ of size 16 at 0x782bede00030 thread T0
#0 0x401b3d in _mm_load_si128(long long __vector(2) const*)
/opt/compiler-explorer/gcc-trunk-20240717/lib/gcc/x86_64-linux-gnu/15.0.0/include/emmintrin.h:701
#1 0x401b3d in Load >
/opt/compiler-explorer/libs/highway/trunk/hwy/ops/x86_128-in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115965
--- Comment #7 from Andrew Pinski ---
Note valgrind in this case cannot always capture buffer overruns due to it
cann't easily add a redzone (buffer to detect overruns) for stack arrays. This
is why -fsanitize=address is more powerful than both
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115936
--- Comment #7 from GCC Commits ---
The master branch has been updated by Tamar Christina :
https://gcc.gnu.org/g:0135a90de5a99b51001b6152d8b548151ebfa1c3
commit r15-2099-g0135a90de5a99b51001b6152d8b548151ebfa1c3
Author: Tamar Christina
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115966
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115936
Tamar Christina changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115887
--- Comment #3 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:5104fe4c7808a66ed3041a8da8e4720585cc8a1f
commit r15-2101-g5104fe4c7808a66ed3041a8da8e4720585cc8a1f
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115754
--- Comment #4 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:297ea7e5bb5c4d92cf3fe29182d432694de858cc
commit r14-10445-g297ea7e5bb5c4d92cf3fe29182d432694de858cc
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115887
--- Comment #4 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:01dfc5b4add9a5ed48c46f6b25cde6e55b9f3ff1
commit r14-10447-g01dfc5b4add9a5ed48c46f6b25cde6e55b9f3ff1
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115527
--- Comment #12 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:d668f875985cf61d3a898d95cf01df90a720e5c2
commit r14-10446-gd668f875985cf61d3a898d95cf01df90a720e5c2
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #78 from Segher Boessenkool ---
(In reply to Andrew Church from comment #77)
> (In reply to Segher Boessenkool from comment #72)
> > if (foo()) {
> > /* The return value of foo can be ignored here because X and Y. */
> > }
>
> Thi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90616
--- Comment #2 from GCC Commits ---
The master branch has been updated by Georg-Johann Lay :
https://gcc.gnu.org/g:e21fef7da92ef36af1e1b020ae5f35ef4f3c3fce
commit r15-2102-ge21fef7da92ef36af1e1b020ae5f35ef4f3c3fce
Author: Georg-Johann Lay
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90616
Georg-Johann Lay changed:
What|Removed |Added
Build|amd64-portbld-freebsd10.4 |
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115527
--- Comment #13 from GCC Commits ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:3eec2d768d72944ed209b51ba60455d751b9aede
commit r11-11580-g3eec2d768d72944ed209b51ba60455d751b9aede
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115966
--- Comment #4 from Filip Kastl ---
My last known to work is r15-1566-gfd536b8412d4da.
And yes, -no-ext-dce does fix the issue!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115526
--- Comment #23 from GCC Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:0841fd4c42ab053be951b7418233f0478282d020
commit r15-2104-g0841fd4c42ab053be951b7418233f0478282d020
Author: Uros Bizjak
Date: Wed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #79 from Andrew Church ---
(In reply to Segher Boessenkool from comment #78)
> If someone (the user, the author, anyone) used warn_unused_result where it is
> not appropriate, just fix *that*. The attribute is specifically for cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #80 from Segher Boessenkool ---
(In reply to Andrew Church from comment #79)
> (In reply to Segher Boessenkool from comment #78)
> > If someone (the user, the author, anyone) used warn_unused_result where it
> > is
> > not appropriat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115526
--- Comment #24 from GCC Commits ---
The releases/gcc-14 branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:3a963d441a68797956a5f67dcb351b2dbd4ac1d0
commit r14-10448-g3a963d441a68797956a5f67dcb351b2dbd4ac1d0
Author: Uros Bizjak
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107200
--- Comment #5 from Andrew Pinski ---
See https://libeigen.gitlab.io/docs/TopicPitfalls.html
section "C++11 and the auto keyword" explictly.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115291
Andrew Pinski changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
--- Comment #4 from Andrew Pi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107200
Andrew Pinski changed:
What|Removed |Added
CC||akihiko.odaki at daynix dot com
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107200
Andrew Pinski changed:
What|Removed |Added
CC||summersnow9403 at gmail dot com
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115968
Andrew Pinski changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
--- Comment #4 from Andrew Pi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111890
--- Comment #8 from Harry Butterworth ---
I applied patch to 14.1.0 and my code compiles now. Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115526
--- Comment #25 from GCC Commits ---
The releases/gcc-13 branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:37bd7d5c4e17c97d2b7d50f630b1cf8b347a31f4
commit r13-8920-g37bd7d5c4e17c97d2b7d50f630b1cf8b347a31f4
Author: Uros Bizjak
Dat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50
--- Comment #1 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:44fcc1ca11e7ea35dc9fb25a5317346bc1eaf7b2
commit r15-2106-g44fcc1ca11e7ea35dc9fb25a5317346bc1eaf7b2
Author: Eikansh Gupta
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115964
Marek Polacek changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110343
Jakub Jelinek changed:
What|Removed |Added
CC||redi at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115900
--- Comment #8 from GCC Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:d890b04197fb0ddba4fbfb32f88e266fa27e02f3
commit r15-2108-gd890b04197fb0ddba4fbfb32f88e266fa27e02f3
Author: Marek Polacek
Date: We
1 - 100 of 188 matches
Mail list logo
