I've committed this patch to change the ways stacks are initialized on
amdgcn. The patch only touches GCN files, or the GCN-only portions of
libgomp files, so I'm allowing it despite stage 4 because I want the ABI
change done for GCC 13, and because it enables Tobias's reverse
offload-patch
MAX_MATCH_SCORE is not assigned anywhere except initialized to 0,
causing BEST_MATCH_MULTI_LIB to always be 0 or -1, which will
cause the result of TARGET_COMPUTE_MULTILIB hook to fail.
gcc/ChangeLog:
* common/config/riscv/riscv-common.cc:
---
gcc/common/config/riscv/riscv-common.cc | 5
> On 30 Jan 2023, at 07:48, Richard Biener wrote:
>
> On Sun, Jan 29, 2023 at 12:35 PM Iain Sandoe via Gcc-patches
> wrote:
>>
>> Technically, this is seems to be a regression somewhere between 4.2 and
>> 4.6 but, it seems, not enough for anyone to care too much. Tested on
>> various
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108626
--- Comment #6 from Jiang An ---
(In reply to Marat Radchenko from comment #5)
> So, does "String literals, and compound literals with const-qualified types,
> need not designate distinct objects." apply here or not? If not, how does
> the case
The following fixes a problem with ! handling in genmatch which isn't
conservative enough when intermediate simplifications push to the
sequence but the final operation appears to just pick an existing
(but in this case newly defined in the sequence) operand. The easiest
fix is to disallow adding
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107944
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107944
--- Comment #5 from CVS Commits ---
The releases/gcc-11 branch has been updated by Martin Jambor
:
https://gcc.gnu.org/g:e36385be53d51539e1c295a80085115b24fede32
commit r11-10496-ge36385be53d51539e1c295a80085115b24fede32
Author: Martin Jambor
On 01/02/2023 15:35, Paul-Antoine Arras wrote:
This patch introduces an instruction pattern for conditional shift
operations (cond_{ashl|ashr|lshr}) in the GCN machine description.
Tested on GCN3 Fiji gfx803.
OK to commit?
The changelog will need to be wrapped to 80 columns.
OK otherwise.
There is less new in TR11 as claimed ... 'strict' on grainsize/num_tasks is
already
in OpenMP 5.1, it is implemented and also listed as 'Y' under 5.1.
Only 'num_threads(strict: int-expr)' is new in TR11.
Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße
On Jan 27, 2023, Jakub Jelinek wrote:
> Now, 1) is precondition of 2), we can only subst the VALUEs if we
> have actually looked the address up, but as can be seen on that testcase,
> we are relying on at least the 1) to be done because we subst the values
> later on even on DEBUG_INSNs and
Ping^2
Richard Sandiford writes:
> [I posted this late in stage 4 as an RFC, but it wasn't suitable for
> GCC 12 at that point. I kind-of dropped the ball after that, sorry.]
>
> Various parts of the omp code checked whether the size of a decl
> was an INTEGER_CST in order to determine whether
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108086
--- Comment #16 from rsandifo at gcc dot gnu.org
---
(In reply to Richard Biener from comment #13)
> (In reply to Richard Biener from comment #12)
> > A regression from GCC 10 which compiles this in 90s at -O1.
> >
> > Richard? Can you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108500
--- Comment #15 from Richard Biener ---
To not look at "nothing" (after successful SRA it should indeed become almost
nothing) I've added a store to a volatile 'x' global variable to the end
of main:
...
s2 = f(s1,s2);
x = s2;
return 0;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108630
--- Comment #3 from Andre Heider ---
While this is a libstdc++ related LTO issue, there's at least another libgcc
one, see the linked bug #60160.
With the workaround here and the patch there the LTOed target libraries look
alot more sane, but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108500
Richard Biener changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45115
--- Comment #4 from Jonathan Wakely ---
This affects C++20 three-way comparisons, which return trivial structs wrapping
an integer.
>From PR 108635:
#include
struct S
{
std::weak_ordering operator<=>(const S&) const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108626
--- Comment #5 from Marat Radchenko ---
So, does "String literals, and compound literals with const-qualified types,
need not designate distinct objects." apply here or not? If not, how does the
case where it applies look like?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107674
--- Comment #2 from CVS Commits ---
The master branch has been updated by Andre Simoes Dias Vieira
:
https://gcc.gnu.org/g:d45ec8a732f449647afa89e46b80a4e0614ec28d
commit r13-5647-gd45ec8a732f449647afa89e46b80a4e0614ec28d
Author: Andre Vieira
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108443
--- Comment #1 from CVS Commits ---
The master branch has been updated by Andre Simoes Dias Vieira
:
https://gcc.gnu.org/g:e0bc13d396002f88b8c27e3a23c7eaee54d379d5
commit r13-5648-ge0bc13d396002f88b8c27e3a23c7eaee54d379d5
Author: Andre Vieira
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107674
--- Comment #1 from CVS Commits ---
The master branch has been updated by Andre Simoes Dias Vieira
:
https://gcc.gnu.org/g:75b58e77706e8b5057770f040005950940a9a0f5
commit r13-5646-g75b58e77706e8b5057770f040005950940a9a0f5
Author: Andre Vieira
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108625
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107300
--- Comment #8 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:d2423144eb36a68fd0da9224857ce807714874a7
commit r13-5645-gd2423144eb36a68fd0da9224857ce807714874a7
Author: Jakub Jelinek
Date:
Since rtl-ssa isn't a real/native SSA representation, it has
to honour the constraints of the underlying rtl representation.
Part of this involves maintaining an rpo list of definitions
for each rtl register, backed by a splay tree where necessary
for quick lookup/insertion.
However, clobbers of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108635
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45115
Andrew Pinski changed:
What|Removed |Added
CC||jzwinck at gmail dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108635
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108635
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2023-02-02
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108635
--- Comment #1 from Andrew Pinski ---
I suspect you need noexcept too. Otherwise you could in theory have an
exception.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104883
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:aa18735f7aa99b40c56b3e3aacb1b28cb805bb90
commit r12-9099-gaa18735f7aa99b40c56b3e3aacb1b28cb805bb90
Author: Jonathan
On Thu, 2 Feb 2023, Jakub Jelinek wrote:
> Hi!
>
> For PR106099 I've added IFN_TRAP as an alternative to __builtin_trap
> meant for __builtin_unreachable purposes (e.g. with -funreachable-traps
> or some sanitizers) which doesn't need vops because __builtin_unreachable
> doesn't need them
Hi!
For PR106099 I've added IFN_TRAP as an alternative to __builtin_trap
meant for __builtin_unreachable purposes (e.g. with -funreachable-traps
or some sanitizers) which doesn't need vops because __builtin_unreachable
doesn't need them either. This works in various cases, but unfortunately
IPA
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108596
--- Comment #7 from David Binderman ---
(In reply to Jakub Jelinek from comment #6)
> Fixed on the trunk so far.
linux-6.2-rc6 builds fine, when built with -O3.
Thanks for the quick fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108623
--- Comment #10 from rsandifo at gcc dot gnu.org
---
(In reply to rguent...@suse.de from comment #9)
> Please you do it, as far as I understand Richard S. no further adjustment
> is necessary but we could simplify some code after the change(?)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108601
--- Comment #15 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:209f02b0a9e9adc0bf0247cb5eef04e0f175d64e
commit r13-5644-g209f02b0a9e9adc0bf0247cb5eef04e0f175d64e
Author: liuhongt
Date: Wed
Hi!
When gimplifying OMP_CLAUSE_{LASTPRIVATE,LINEAR}_STMT, we wrap it always
into a GIMPLE_BIND, but when putting statements directly into
OMP_CLAUSE_{LASTPRIVATE,LINEAR}_GIMPLE_SEQ, we do it only if needed (there
are any temporaries that need to be declared in the sequence).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108435
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:0f349928e16fdc7dba52561e8d40347909f9f0ff
commit r13-5643-g0f349928e16fdc7dba52561e8d40347909f9f0ff
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583
--- Comment #23 from Tamar Christina ---
(In reply to rguent...@suse.de from comment #22)
> On Thu, 2 Feb 2023, tnfchris at gcc dot gnu.org wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583
> >
> > --- Comment #21 from Tamar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583
--- Comment #22 from rguenther at suse dot de ---
On Thu, 2 Feb 2023, tnfchris at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583
>
> --- Comment #21 from Tamar Christina ---
> >
> > OK, so that's an
On Thu, 2 Feb 2023, liuhongt wrote:
> Normally when vf is not constant, it will be prevented by
> vectorizable_nonlinear_inductions, but for this case, it failed going
> into
>
> if (STMT_VINFO_RELEVANT_P (stmt_info))
> {
> need_to_vectorize = true;
> if
Hi,
this patch adds LEN_LOAD/LEN_STORE support for z14 and newer.
It defines a bias value of -1 and implements the LEN_LOAD and LEN_STORE
optabs.
It also includes various vll/vstl testcases adapted from Kewen Lin's patch
for Power.
Bootstrapped and regtested on z13-z16.
Is it OK?
Regards
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60160
Andre Heider changed:
What|Removed |Added
CC||a.heider at gmail dot com
--- Comment #8
On Wed, 1 Feb 2023, Siddhesh Poyarekar wrote:
> On 2023-02-01 13:24, Qing Zhao wrote:
> >
> >
> >> On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar
> >> wrote:
> >>
> >> On 2023-01-31 09:11, Qing Zhao wrote:
> >>> Update documentation to clarify a GCC extension on structure with
> >>> flexible
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108623
--- Comment #9 from rguenther at suse dot de ---
On Wed, 1 Feb 2023, meissner at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108623
>
> Michael Meissner changed:
>
>What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106157
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
On Wed, 1 Feb 2023, Qing Zhao wrote:
>
>
> > On Feb 1, 2023, at 6:41 AM, Richard Biener wrote:
> >
> > On Tue, 31 Jan 2023, Qing Zhao wrote:
> >
> >> GCC extension accepts the case when a struct with a flexible array member
> >> is embedded into another struct (possibly recursively).
> >>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583
--- Comment #21 from Tamar Christina ---
>
> OK, so that's an ADD_HIGHPART_EXPR then? Though the highpart of an
> add is only a single bit, isn't it? For scalar you'd use the
> carry bit here and instructions like adc to consume it. Is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108635
Bug ID: 108635
Summary: Redundant calls to C++ spaceship operator<=> with
attribute pure or const
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity:
201 - 247 of 247 matches
Mail list logo