https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112092
--- Comment #18 from Maciej W. Rozycki ---
Any fix will have to be based on valid code though and the lone presence
of inline asm is not supposed to prevent optimisations from being used,
e.g. I may have to insert a memory barrier into my code f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117759
Maciej W. Rozycki changed:
What|Removed |Added
Summary|Alpha: `_Atomic' keyword|Alpha: Data races with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112092
--- Comment #16 from Maciej W. Rozycki ---
As I say GCC doesn't know the inline asm makes use of the vector unit, so
the compiler is free to make any optimisations that it can see fit based
on vector code it has produced itself. Actually in thi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112092
--- Comment #14 from Maciej W. Rozycki ---
This is invalid code, because you haven't told GCC your inline assembly
makes use of v8 or v24. You need to specify inputs and outputs correctly
or otherwise the compiler will consider these registers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117759
--- Comment #1 from Maciej W. Rozycki ---
I need to withdraw the fix for this PR, it is a red herring that has
misled me.
While there is a data race here it is not within access to the atomic
data object, it comes from the *outside*. Consider
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117759
Maciej W. Rozycki changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117759
Bug ID: 117759
Summary: Alpha: `_Atomic' keyword not respected for !BWX and
8-bit/16-bit stores
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: major
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115526
--- Comment #20 from Maciej W. Rozycki ---
Created attachment 58687
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58687&action=edit
Test case modified to use scan-assembler-times instead
(In reply to Uroš Bizjak from comment #17)
> (In r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115526
--- Comment #15 from Maciej W. Rozycki ---
(In reply to Uroš Bizjak from comment #13)
> CC Maciej if he can test the patch on his Alpha system.
It takes about a day to complete and I had to rerun the libstdc++3
subdirectory due to an intermitte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115565
Maciej W. Rozycki changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |macro at orcam dot me.uk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115565
--- Comment #2 from Maciej W. Rozycki ---
Created attachment 58475
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58475&action=edit
Reduced reproducer and incorrect code + RTL dumps produced with commit
08a692679fb8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115565
--- Comment #1 from Maciej W. Rozycki ---
Created attachment 58474
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58474&action=edit
Reduced reproducer and correct code + RTL dumps produced with commit
4cd26879f758
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115565
Bug ID: 115565
Summary: [4.0/4.1/4.2/4.3/4.4/4.5/4.6/4.7/4.8/4.9/5/6/7/8/9/10/
11/12/13/14/15 Regression] CSE: Comparison incorrectly
evaluated as constant causing optimization to pro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115459
--- Comment #4 from Maciej W. Rozycki ---
(In reply to Andrew Pinski from comment #3)
> Alpha really should move to LRA too.
I can certainly have a look once I'm done with the VAX target unless
someone beats me to it. Or maybe even before, as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115459
Bug ID: 115459
Summary: [14/15 regression] Alpha/Linux ICE: in gen_rtx_SUBREG,
at emit-rtl.cc:1032 around g-debpoo.adb:1896:8, as
from r14-1187-gd6b756447cd5
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883
Bug 40883 depends on bug 79646, which changed state.
Bug 79646 Summary: Typos in vax.opt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79646
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79646
Maciej W. Rozycki changed:
What|Removed |Added
CC||macro at orcam dot me.uk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114083
--- Comment #7 from Maciej W. Rozycki ---
(In reply to Roland Illig from comment #6)
> There's a problem with the wording though. On a platform that doesn't
> support conditional-move operations, it's not possible to _use_
> conditional-move ope
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114083
--- Comment #4 from Maciej W. Rozycki ---
The flag enables the use of the conditional-move operations even with
hardware that has no support for such operations, hence unconditionally.
Such operations, where unavailable, are then synthesized as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113949
Maciej W. Rozycki changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |macro at orcam dot me.uk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113454
--- Comment #2 from Maciej W. Rozycki ---
(In reply to Sam James from comment #1)
> Didn't help this time ;)
Well, now it mentions 483.xalancbmk, which the other bug does not
(and which I searched for specifically, finding only a bunch of old
r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113454
Bug ID: 113454
Summary: [14 regression] "assignment of read-only member" error
with 483.xalancbmk from SPEC CPU 2006
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111815
Maciej W. Rozycki changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111956
--- Comment #9 from Maciej W. Rozycki ---
Hmm, the host check for `__frexpieee128' in gcc/ will surely not do
what's intended: even if the host is `powerpc*-*-linux*', the target
will often be something else and vice versa (libgm2's host is GCC'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111956
--- Comment #5 from Maciej W. Rozycki ---
Hmm, this seems awkward to me. It won't work AFAICT with the usual
native bootstrap environment, where you just run:
$ /path/to/configure && make bootstrap
and it won't work where you have an old vers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112092
Maciej W. Rozycki changed:
What|Removed |Added
Keywords|wrong-code |missed-optimization
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112295
Bug ID: 112295
Summary: RISC-V: Short forward branch pessimisation for ALU
operations
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimizat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112092
--- Comment #7 from Maciej W. Rozycki ---
Thank you for all your explanations. I think I'm still missing something
here, so I'll write it differently (and let's ignore the tail-agnostic vs
tail-undisturbed choice for the purpose of this conside
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112092
--- Comment #3 from Maciej W. Rozycki ---
Maybe I'm missing something, but the RVV spec has this for VSETVLI:
"The application specifies the total number of elements to be processed
(the application vector length or AVL) as a candidate value fo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112092
Bug ID: 112092
Summary: RISC-V: Wrong RVV code produced for vsetvl-11.c and
vsetvlmax-8.c
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112091
Bug ID: 112091
Summary: rs6000: redefinition of 'constexpr long double
std::abs(long double)', while building libgm2
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111815
--- Comment #1 from Maciej W. Rozycki ---
Created attachment 56120
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56120&action=edit
Reduced testcase
This triggers the same ICE in `p'. Preincrements are required so that
their results land
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85152
Maciej W. Rozycki changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111815
Maciej W. Rozycki changed:
What|Removed |Added
Ever confirmed|0 |1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111815
Bug ID: 111815
Summary: VAX: ICE in 'print_operand_address' while building
'elf_zstd_decompress' from libbacktrace/elf.c
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111530
Bug ID: 111530
Summary: Unable to build GM2 standard library on BSD due to a
`getopt_long_only' GNU extension dependency
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110632
Bug ID: 110632
Summary: RISC-V: SLP optimisation
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: target
A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110630
Bug ID: 110630
Summary: Missed optimization: bb-slp-pr95839.c not vectorised
with V2SF targets
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: enhance
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107405
--- Comment #18 from Maciej W. Rozycki ---
Well, according to the assertion triggered `typeof (EM_MAX_SLOTS)' will
yield a data type of a different width depending on the compiler version.
Even if this GNU extension does not constitute a part of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107405
--- Comment #15 from Maciej W. Rozycki ---
If in older C standard versions such enums are invalid, then I think
this should be a hard error rather than a silent ABI change for the code
produced. Not all code out there will have sanity checks su
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107756
Bug ID: 107756
Summary: Change in sizeof(enum) with -std=gnu11 breaks Linux
kernel code compilation (PR c/36113 change regression)
Product: gcc
Version: 13.0
Status: UNC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107044
Bug ID: 107044
Summary: internal compiler error: in
dump_possible_polymorphic_call_targets, at
ipa-devirt.cc:3456
Product: gcc
Version: 13.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106705
Bug ID: 106705
Summary: Expensive constant load replicated throughout switch
statement
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104865
--- Comment #7 from Maciej W. Rozycki ---
Well, it's not clear to me whether the reserved operand as defined by the
VAX floating-point architecture ought be considered an sNaN given that
there is no qNaN.
Also a reserved operand causes a fault
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104865
--- Comment #5 from Maciej W. Rozycki ---
Wrong question then. Should `__builtin_nan' even compile on non-IEEE-754
FP targets that don't have a qNaN? And I'll reply to myself.
According to our manual:
"-- Built-in Function: double __builtin_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104865
Maciej W. Rozycki changed:
What|Removed |Added
CC||macro at orcam dot me.uk
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97504
--- Comment #49 from Maciej W. Rozycki ---
*** Bug 98724 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98724
Maciej W. Rozycki changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103059
Maciej W. Rozycki changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103059
Maciej W. Rozycki changed:
What|Removed |Added
Last reconfirmed||2021-11-03
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103059
Bug ID: 103059
Summary: [10 regression][VAX] ICE in postreload with the ASHIFT
form of scaled indexed addressing
Product: gcc
Version: 12.0
Status: UNCONFIRMED
51 matches
Mail list logo