https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113353
Bug ID: 113353
Summary: Wrong rounding in std::nearbyint when vectorized with
-funsafe-math-optimizations on PPC
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112513
--- Comment #4 from Alexander Grund ---
Thank you, I replaced that by
unsigned unused;
__cpuid(1, cpuid1.val, unused, unused, unused);
and it works in the setup I have.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112513
Alexander Grund changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #2 from Alexander
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112513
Bug ID: 112513
Summary: Misoptimization of argument
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112443
--- Comment #3 from Alexander Grund ---
> I can confirm that the suggested patch can be applied to 12.2.0 and fixes
> the issue I observed
Also tested 12.1, 12.3, 13.1, 13.2 with this patch and it works (as expected)
too
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112443
--- Comment #2 from Alexander Grund ---
I can confirm that the suggested patch can be applied to 12.2.0 and fixes the
issue I observed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112443
Bug ID: 112443
Summary: Misoptimization of _mm256_blendv_epi8 intrinsic on
avx512bw+avx512vl
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112370
--- Comment #3 from Alexander Grund ---
Created attachment 56513
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56513=edit
INVALID reduced example (after running cvise on the former example)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112370
--- Comment #2 from Alexander Grund ---
FWIW: I tried to run cvise on this however it created an invalid example where
indeed a non-heap pointer would be freed. I'll attach it anyway for reference
as it took hours to run the reduce
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112370
--- Comment #1 from Alexander Grund ---
Created attachment 56503
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56503=edit
Preprocessed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112370
Bug ID: 112370
Summary: -Wfree-nonheap-object in std::vector dtor on
sapphirerapids with -O3
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112301
--- Comment #4 from Alexander Grund ---
Thank you! Will there be backports for 12.x?
The current patch is conflicting due to "c++: enable NRVO from inner block
[PR51571]" and while it seems to be easy enough to backport both patches in
order
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112301
Bug ID: 112301
Summary: Double destruction of returned object when exiting the
scope causes an exception which gets rethrown
Product: gcc
Version: 12.3.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100799
--- Comment #11 from Alexander Grund ---
Some more experiments with GCC 10.3, OpenBLAS 0.3.15 and FlexiBLAS 3.0.4:
Baseline: Broken at -O1, working at -Og
I got it to break with "-Og -fmove-loop-invariants".
Then it worked again by adding
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100799
--- Comment #10 from Alexander Grund ---
(In reply to Peter Bergner from comment #2)
> The failure with GCC 7 and later coincides with the PPC port starting to
> default to LRA instead of reload.
Is there a compiler flag that can switch the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100799
--- Comment #7 from Alexander Grund ---
Hi,
it's more than 1 year later now. Peter seemingly has a simple reproducer.
Is there anything new on this? Any patch to fix that or at least anything to
try or a workaround like disabling a specific
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54569
Alexander Grund changed:
What|Removed |Added
CC||alexander.grund@tu-dresden.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101061
--- Comment #13 from Alexander Grund ---
> But what you can see is that the resulting pointer is used for the
> initialization and not the placement address as literally written in source.
So I assume it was supposed to be "Y::Y (D_6557, 1);"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101061
Alexander Grund changed:
What|Removed |Added
Version|8.4.0 |8.5.0
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101061
--- Comment #9 from Alexander Grund ---
> Note that when the union type is visible in the access path then GCC allows
> punning without further restrictions. Thus the accesses as written above are
> OK.
Now I have to ask again for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101061
--- Comment #6 from Alexander Grund ---
Oh and for completeness: The same applies to the following union, doesn't it?
I.e. given this:
struct TF_TString_Raw {
uint8_t raw[24];
};
struct TF_TString_Small {
uint8_t size;
char str[23];
};
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101061
--- Comment #5 from Alexander Grund ---
So am I right assuming that the following is basically UB as per GCC (although
it should work as per the standard)?
template
union slot_type {
map_slot_type() {}
~map_slot_type() = delete;
using
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101061
--- Comment #3 from Alexander Grund ---
You are right, it actually seems to be the combination of those to, so -O2
-fno-strict-aliasing and -O2 -fno-tree-vrp both make it work.
The layout-compatible refers to the "common initial sequence" that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101061
--- Comment #1 from Alexander Grund ---
Created attachment 51006
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51006=edit
compressed preprocessed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101061
Bug ID: 101061
Summary: tree-vrp misoptimization on skylake+ using union-based
aliasing
Product: gcc
Version: 8.4.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100703
--- Comment #3 from Alexander Grund ---
I found that this was fixed in 10.3 and 11.1 by
https://github.com/gcc-mirror/gcc/commit/e2882e76089cecdc268d0835c54cabfa80b5b0be
So yes only happens in 10.2. Thanks for checking that!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100799
--- Comment #1 from Alexander Grund ---
Confirmed to also break with GCC 7.3, 8.2, 8.3 but works with 6.3, 6.4, 6.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100799
Bug ID: 100799
Summary: Stackoverflow in optimized code on PPC
Product: gcc
Version: 10.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100706
--- Comment #3 from Alexander Grund ---
Ok, tested a few different bintuils versions. Bug occurs with 2.35 and 2.35.1
and seems to be fixed in 2.35.2
So I guess this can be closed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100706
--- Comment #2 from Alexander Grund ---
Thanks for the reply. Although this was hard to test (need to interfere with
TFs build process which must use the gold linker) I managed to link that one
library manually with bfd and it did work. Hence
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100706
Bug ID: 100706
Summary: Invalid instructions in plt calls on PPC
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100703
--- Comment #1 from Alexander Grund ---
It goes further: Even the usual conversion rules for pointer types don't apply:
void foo(__vector_pair*){}
void bar(const __vector_pair*){}
int main(){
__vector_pair p;
foo(p); // works
bar(p); //
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100703
Bug ID: 100703
Summary: __vector_pair and __vector_quad cannot be passed by
reference
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100677
Bug ID: 100677
Summary: False positive unused-but-set-parameter warning when
using VSX intrinsics
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100448
Bug ID: 100448
Summary: internal compiler error: Segmentation fault
Product: gcc
Version: 10.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98561
--- Comment #2 from Alexander Grund ---
I did some work to reduce this further: https://godbolt.org/z/sezTPs
For some reason it seems to be related to std::array. So may I suggest to
include the above (or the original reproducer) in the test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98561
Bug ID: 98561
Summary: -Wstringop-overflow triggered when memcpy to single
char and writing to differently sized array members
Product: gcc
Version: 10.2.1
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98140
--- Comment #1 from Alexander Grund ---
It looks like this was fixed in 10.1 by this commit
https://github.com/gcc-mirror/gcc/commit/37e0df8a9be5a8232f4ccb73cdadb02121ba523f
However the codegen looks worse:
390: 20 00 9e c3 lfs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98140
Bug ID: 98140
Summary: Reused register by xsmincdp leads to wrong NaN
propagation on Power9
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
39 matches
Mail list logo
