Hi Carl,
Excepting for Peter's review comments, some nits are inline below.
on 2023/7/11 03:18, Carl Love wrote:
>
> GCC maintainers:
>
> Ver 3, Renamed the patch per comments on ver 2. Previous subject line
> was " [PATCH ver 2] rs6000, __builtin_set_fpscr_rn add retrun value".
> Fixed
on 2023/7/11 03:18, Carl Love wrote:
> On Fri, 2023-07-07 at 12:06 +0800, Kewen.Lin wrote:
>> Hi Carl,
>>
>> Some more minor comments are inline below on top of Peter's
>> insightful
>> review comments.
>>
>> on 2023/7/1 08:58, Carl Love wrote:
>>> GCC maintainers:
>>>
>>> Ver 2, Went back thru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110179
Florian Weimer changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
From: Christoph Müllner
Recently, two identical XTheadCondMov tests have been added, which both fail.
Let's fix that by changing the following:
* Merge both files into one (no need for separate tests for rv32 and rv64)
* Drop unrelated attribute check test (we already test for `th.mveqz`
and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110179
--- Comment #3 from CVS Commits ---
The master branch has been updated by Florian Weimer :
https://gcc.gnu.org/g:104b09005229ef48a79a33511ea192bb3ec3c415
commit r14-2426-g104b09005229ef48a79a33511ea192bb3ec3c415
Author: Florian Weimer
Date:
Here's updated patch.
1. use optimize_insn_for_speed_p instead of using optimize_function_for_speed_p.
2. explicitly move memory to dest register to avoid false dependence in
one_cmpl pattern.
False dependency happens when destination is only updated by
pternlog. There is no false dependency
On Tue, Jul 11, 2023 at 11:40 AM Haochen Jiang via Gcc-patches
wrote:
>
> Hi all,
>
> Currently on trunk, both usage of intrin and builtin for 128 bit VAES
> ISA will result in ICE since we did not check AVX512VL until pattern,
> which is not user expected. This patch aims to fix that ICE and
Hi all,
Currently on trunk, both usage of intrin and builtin for 128 bit VAES
ISA will result in ICE since we did not check AVX512VL until pattern,
which is not user expected. This patch aims to fix that ICE and throw
an error under this scenario.
Regtested on x86-64-linux-gnu{-m32,}. Ok for
Please ignore this patch, I'm testing another patch to separate non
swap operands case where a setcc is not needed in the peephole2.
On Tue, Jul 11, 2023 at 11:14 AM liuhongt via Gcc-patches
wrote:
>
> Similar like we did for cmpxchg, but extended to all
> ix86_comparison_int_operator since
Similar like we did for cmpxchg, but extended to all
ix86_comparison_int_operator since cmpccxadd set EFLAGS exactly same
as CMP.
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,},
Ok for trunk?
gcc/ChangeLog:
PR target/110591
* config/i386/sync.md (cmpccxadd_): Add a new
Attached is an updated version of the patch.
Based on Philipp's review, some changes:
1. Defined new enum fma_state to describe the state of FMA candidates
for a list of operands. (Since the tests seems simple after the
change, I didn't add predicates on it.)
2. Changed return type of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107013
HaoChen Gui changed:
What|Removed |Added
CC||joseph at codesourcery dot com
---
Hi Juzhe,
> Hi, Kewen.
>
> You mean COND_LEN_* family I added is unlikely used by power in the future?
Since AFAIK there is no plan to extend len family on Power, it's very likely
that
Power will have no chance to leverage them, so yes.
> Could you revise them to make it possible used by
on 2023/7/11 07:11, Peter Bergner wrote:
> On 6/29/23 4:31 AM, Kewen.Lin via Gcc-patches wrote:
>> This is okay for trunk (no backports needed btw), this fix can even be
>> taken as obvious, thanks!
>>
>>>
>>> 2023-06-07 Jeevitha Palanisamy
>>>
>>> gcc/
>>> PR target/106907
>>
>> One
Hi, Kewen.
You mean COND_LEN_* family I added is unlikely used by power in the future?
Could you revise them to make it possible used by power in the future so that
we won't duplicate to many patterns.
For example, COND_LEN_* has mask operand, is it possible that power can also
use it with
Hi Carl,
on 2023/7/8 04:40, Carl Love wrote:
>
> GCC maintainers:
>
> Ver 5. Removed -compile from the names of the compile only tests. Fixed
> up the reference to the compile file names in the .h file headers.
> Replaced powerpc_vsx_ok with vsx_hw in the run test files. Removed the
>
on 2023/7/10 18:40, Richard Biener wrote:
> On Fri, 7 Jul 2023, juzhe.zh...@rivai.ai wrote:
>
>> From: Ju-Zhe Zhong
>>
>> Hi, Richard and Richi.
>>
>> This patch is adding cond_len_* operations pattern for target support
>> loop control with length.
>
> It looks mostly OK - the probably
Bootstraped and Regression on X86 last night with no surprise fails.
This patch has already included 'BIAS' argument.
Ok for trunk ?
juzhe.zh...@rivai.ai
From: juzhe.zhong
Date: 2023-07-10 19:35
To: gcc-patches
CC: richard.sandiford; rguenther; Ju-Zhe Zhong
Subject: [PATCH V2] VECT: Add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617
Sam James changed:
What|Removed |Added
CC||bugzilla at tecnocode dot
co.uk,
Peter:
On Mon, 2023-07-10 at 16:57 -0500, Peter Bergner wrote:
> On 7/10/23 2:18 PM, Carl Love wrote:
> > + /* Get the current FPSCR fields, bits 29:31 (DRN) and bits 56:63
> > (VE, OE, UE,
> > + ZE, XE, NI, RN) from the FPSCR and return them. */
>
> The 'Z' above should line up directly
On Tue, Jul 11, 2023 at 12:24 AM Alexander Monakov via Gcc-patches
wrote:
>
>
> On Mon, 10 Jul 2023, liuhongt via Gcc-patches wrote:
>
> > False dependency happens when destination is only updated by
> > pternlog. There is no false dependency when destination is also used
> > in source. So either
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110613
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Ever confirmed|0
On 6/29/23 4:31 AM, Kewen.Lin via Gcc-patches wrote:
> This is okay for trunk (no backports needed btw), this fix can even be
> taken as obvious, thanks!
>
>>
>> 2023-06-07 Jeevitha Palanisamy
>>
>> gcc/
>> PR target/106907
>
> One curious question is that this PR106907 seemed not to
On Fri, 7 Jul 2023, Richard Biener wrote:
I have implemented support for uninitialized memory in my translation
validator. But I am not sure how well this corresponds to the GIMPLE
semantics, so I have some questions...
My implementation tracks uninitialized bits. Use of uninitialized bits is
On 7/10/23 11:47 AM, Peter Bergner wrote:
> While helping someone on the team debug an issue, I noticed some redundant
> tests in a couple of our predicates which can be removed. I'm going to
> commit the following as obvious once bootstrap and regtesting come back
> clean.
>
> Peter
>
>
>
On Mon, Jul 10, 2023 at 03:10:21PM -0500, Segher Boessenkool wrote:
> Hi!
>
> On Mon, Jul 10, 2023 at 03:59:44PM -0400, Michael Meissner wrote:
> > In doing other work, I noticed that there was an insn:
> >
> > vsx_extract_v4sf__load
> >
> > Which did not have an iterator. I removed the
I noted that all memory spaces are supported, some by falling
back to the default ("malloc") - except for omp_high_bw_mem_space
(unless the memkind lib is available).
I think it makes more sense to fallback to 'malloc' also for
omp_high_bw_mem_space.
Additionally, I updated the documentation to
On 7/10/23 2:18 PM, Carl Love wrote:
> + /* Get the current FPSCR fields, bits 29:31 (DRN) and bits 56:63 (VE, OE,
> UE,
> + ZE, XE, NI, RN) from the FPSCR and return them. */
The 'Z' above should line up directly under the 'G' in Get.
> - /* Insert new RN mode into FSCPR. */
> -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110610
--- Comment #9 from Andrew Pinski ---
I am shocked that optabs.h is not included for PLUGIN_HEADERS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617
Alejandro Colomar changed:
What|Removed |Added
CC||alx at kernel dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110618
--- Comment #1 from Mikael Morin ---
Created attachment 55517
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55517=edit
Draft patch
This seems to work for this case, but I'm not sure how reliable it is.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110288
--- Comment #3 from anlauf at gcc dot gnu.org ---
The apparent discrepancy between fndecl and the actual arguments in the call
may be a result from the following block in gfc_conv_procedure_call after:
7390 /* Deferred length dummies
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 104843, which changed state.
Bug 104843 Summary: signed overflow in compute_const_anchors, at cse.cc:1180
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104843
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104843
Xi Ruoyao changed:
What|Removed |Added
Target Milestone|--- |13.0
Status|UNCONFIRMED
On Mon, 10 Jul 2023, Alexander Monakov wrote:
> > I chose to make it possible to write function definitions with that
> > attribute with GCC adding the necessary callee save/restore code in
> > the xlogue itself.
>
> But you can't trivially restore if the callee is sibcalling — what
> happens
Running
$ make check-g++
RUNTESTFLAGS='--target_board=unix\{-D_GLIBCXX_USE_CXX11_ABI=0,\}
dg.exp=allocator-opt1.C'
yields:
FAIL: g++.dg/tree-ssa/allocator-opt1.C -std=c++98 scan-tree-dump-times gimple
"struct allocator D" 1
FAIL: g++.dg/tree-ssa/allocator-opt1.C -std=c++14
On 7/10/23 22:14, Alejandro Colomar wrote:
[CC += Andrew]
Hi Xi, Andrew,
On 7/10/23 20:41, Xi Ruoyao wrote:
Maybe we should have a weaker version of nonnull which only performs the
diagnostic, not the optimization. But it looks like they hate the idea:
https://gcc.gnu.org/PR110617.
This is
[CC += Andrew]
Hi Xi, Andrew,
On 7/10/23 20:41, Xi Ruoyao wrote:
Maybe we should have a weaker version of nonnull which only performs the
diagnostic, not the optimization. But it looks like they hate the idea:
https://gcc.gnu.org/PR110617.
This is the one thing that makes me use both Clang
Hi!
On Mon, Jul 10, 2023 at 03:59:44PM -0400, Michael Meissner wrote:
> In doing other work, I noticed that there was an insn:
>
> vsx_extract_v4sf__load
>
> Which did not have an iterator. I removed the useless .
This patch does that, you mean.
> --- a/gcc/config/rs6000/vsx.md
> +++
I forgot to add:
I have tested this patch on the following systems and there was no degration.
Can I check it into the trunk branch?
* Power10, LE, --with-cpu=power10, IBM 128-bit long double
* Power9, LE, --with-cpu=power9, IBM 128-bit long double
* Power9, LE,
I forgot to add:
I have tested this patch on the following systems and there was no degration.
Can I check it into the trunk branch?
* Power10, LE, --with-cpu=power10, IBM 128-bit long double
* Power9, LE, --with-cpu=power9, IBM 128-bit long double
* Power9, LE,
In doing other work, I noticed that there was an insn:
vsx_extract_v4sf__load
Which did not have an iterator. I removed the useless .
I have tested this patch on the following systems and there was no degration.
Can I check it into the trunk branch?
* Power10, LE,
Also change some internal variables and function arguments from int to bool.
gcc/ChangeLog:
* reorg.cc (stop_search_p): Change return type from int to bool
and adjust function body accordingly.
(resource_conflicts_p): Ditto.
(insn_references_resource_p): Change return type from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110621
Bug ID: 110621
Summary: x86_64: Test gcc.target/i386/pr105354-2.c fails with
-fstack-protector
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
If we are converting an unsigned DImode to a TImode value, and the TImode value
will go in a vector register, GCC currently does the DImode to TImode conversion
in GPR registers, and then moves the value to the vector register via a mtvsrdd
instruction.
This patch adds a new zero_extendditi2 insn
This patch optimizes cases like:
vector double v1, v2;
/* ... */
v2 = vec_splats (vec_extract (v1, 0); /* or */
v2 = vec_splats (vec_extract (v1, 1);
Previously:
vector long long
splat_dup_l_0 (vector long long v)
{
return
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110620
--- Comment #5 from Andrew Pinski ---
>From the looks of it is just not optimizing enough before the warning happens.
The final optimized code does not have the store in it.
The store for the vector to create the size of one element vector
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110620
--- Comment #4 from Chris Uzdavinis ---
(Sorry I was getting bugzilla errors about collisions when adding comments, but
they seemed to have gone through after all.)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110620
--- Comment #3 from Chris Uzdavinis ---
Starting with Gcc12.1 (at least on x86) and through all versions up to the
trunk (post 13.1)
This warning hits with optimization -O2 or higher.
https://godbolt.org/z/q3T39Wf8c
#include
void
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110620
--- Comment #2 from Chris Uzdavinis ---
Created attachment 55516
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55516=edit
preprocessed code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110620
--- Comment #1 from Chris Uzdavinis ---
Starting with Gcc12.1 (at least on x86) and through all versions up to the
trunk (post 13.1)
This warning hits with optimization -O2 or higher.
https://godbolt.org/z/q3T39Wf8c
#include
void
On Sat, 1 Jul 2023, Nathaniel Shead wrote:
> This is an update of the patch series at
> https://gcc.gnu.org/pipermail/gcc-patches/2023-March/614811.html
>
> Changes since v2:
>
> - Use a separate 'hash_set' to track expired variables instead of
> adding a flag to 'lang_decl_base'.
> - Use
Hi Harald,
I do get why this happens. I still don't get why I have to do this
'optimization' manually. I mean, this rewriting of expressions is needed in
more than one location and most probably already present somewhere. So who
can point me in the right direction?
Regards,
Andre
Andre
On Mon, Jul 10, 2023 at 08:54:54PM +0200, Florian Weimer via Gcc-patches wrote:
> Fixes commit r14-1614-g49310a99330849 ("libgcc: Fix eh_frame fast path
> in find_fde_tail").
>
> libgcc/
>
> PR libgcc/110179
> * unwind-dw2-fde-dip.c (find_fde_tail): Add cast to avoid
> implicit
GCC maintainers:
Ver 3, Renamed the patch per comments on ver 2. Previous subject line
was " [PATCH ver 2] rs6000, __builtin_set_fpscr_rn add retrun value".
Fixed spelling mistakes and formatting. Updated define_expand
"rs6000_set_fpscr_rn to have the rs6000_get_fpscr_fields and
On Fri, 2023-07-07 at 12:06 +0800, Kewen.Lin wrote:
> Hi Carl,
>
> Some more minor comments are inline below on top of Peter's
> insightful
> review comments.
>
> on 2023/7/1 08:58, Carl Love wrote:
> > GCC maintainers:
> >
> > Ver 2, Went back thru the requirements and emails. Not sure where
On Thu, 2023-07-06 at 17:54 -0500, Peter Bergner wrote:
> On 6/30/23 7:58 PM, Carl Love via Gcc-patches wrote:
> > rs6000, __builtin_set_fpscr_rn add retrun value
>
> s/retrun/return/
>
> Maybe better written as:
>
> rs6000: Add return value to __builtin_set_fpscr_rn
Changed subject, fixed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110620
Bug ID: 110620
Summary: spurious array-bounds
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee:
Hi,
This is the change for the GCC14 releaes Notes on the deprecating of a C
extension about flexible array members.
Okay for committing?
thanks.
Qing
*htdocs/gcc-14/changes.html (Caveats): Add notice about deprecating a C
extension about flexible array members.
---
On Mon, 10 Jul 2023, Michael Matz via Gcc-patches wrote:
> Hello,
>
> the ELF psABI for x86-64 doesn't have any callee-saved SSE
> registers (there were actual reasons for that, but those don't
> matter anymore). This starts to hurt some uses, as it means that
> as soon as you have a call
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110619
--- Comment #3 from Fedor Chelnokov ---
I think according to https://eel.is/c++draft/basic.stc#general-4 the function
shall return an "invalid pointer valued". And nullptr is not considered such.
And if one modifies the function slightly (see
Hi Andre,
thanks for looking into this!
While it fixes the original PR, here is a minor extension of the
testcase that ICEs here with your patch:
program pr102003
type pdt(n)
integer, len :: n = 8
character(len=n) :: c
end type pdt
type(pdt(42)) :: p
integer, parameter ::
Fixes commit r14-1614-g49310a99330849 ("libgcc: Fix eh_frame fast path
in find_fde_tail").
libgcc/
PR libgcc/110179
* unwind-dw2-fde-dip.c (find_fde_tail): Add cast to avoid
implicit conversion of pointer value to integer.
---
libgcc/unwind-dw2-fde-dip.c | 2 +-
1 file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110619
--- Comment #2 from Andrew Pinski ---
>but it is not nullptr.
Or is it just undefined so it could be considered a nullptr ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110619
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #1 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110619
Bug ID: 110619
Summary: Dangling pointer returned from constexpr function
converts in nullptr
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity:
Hi Thomas,
this patch contains support for the 'readonly' modifier in copyin clauses
and the cache directive.
As we discussed earlier, the work for actually linking this to middle-end
points-to analysis is a somewhat non-trivial issue. This first patch allows
the language feature to be used in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #2 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110614
--- Comment #2 from seurer at gcc dot gnu.org ---
This may be a dupe of PR110616 (or vice-versa).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617
--- Comment #1 from Xi Ruoyao ---
[1]:
https://sourceware.org/glibc/wiki/Style_and_Conventions#Bugs_in_the_user_program
[2]: https://sourceware.org/pipermail/libc-alpha/2023-July/149893.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110618
Bug ID: 110618
Summary: Dependency between arguments when one is allocatable
array whose dummy is intent(out)
Product: gcc
Version: 11.4.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617
Bug ID: 110617
Summary: RFE: Add a diagnostic-only variant of nonnull
attribute
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110580
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106050
Mikael Morin changed:
What|Removed |Added
CC||mikael at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110523
--- Comment #12 from Sergei Trofimovich ---
I confirm ICE gone away for json-3.11.2. json-3.11.2 still odes not compile
same as in https://gcc.gnu.org/PR110580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110205
Xi Ruoyao changed:
What|Removed |Added
Component|c |other
CC|
> Am 10.07.2023 um 17:56 schrieb Michael Matz via Gcc-patches
> :
>
> Hello,
>
> the ELF psABI for x86-64 doesn't have any callee-saved SSE
> registers (there were actual reasons for that, but those don't
> matter anymore). This starts to hurt some uses, as it means that
> as soon as you
While helping someone on the team debug an issue, I noticed some redundant
tests in a couple of our predicates which can be removed. I'm going to
commit the following as obvious once bootstrap and regtesting come back
clean.
Peter
rs6000: Remove redundant MEM_P predicate usage
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110615
--- Comment #3 from Julien Jorge ---
> This is the expected behaviour for those old releases (which are no longer
> supported or maintained, and so there's no point reporting bugs in them).
Well, it was more an attempt to raise awareness on a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106050
--- Comment #4 from Paul Thomas ---
Created attachment 55515
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55515=edit
Patch that fixes this PR for me
I had to add to Steve's patch to get this PR sorted out.
Ideally of course, we would
On Mon, 10 Jul 2023, liuhongt via Gcc-patches wrote:
> False dependency happens when destination is only updated by
> pternlog. There is no false dependency when destination is also used
> in source. So either a pxor should be inserted, or input operand
> should be set with constraint '0'.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106050
--- Comment #3 from Paul Thomas ---
(In reply to Martin Liška from comment #2)
> Likely started with r8-3056-g5bab4c9631c478b7, it was rejected before the
> revision anyway.
With all branches up to 13-branch, I see:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110616
Bug ID: 110616
Summary: [14 regression] ICE after r14-2117-gdd86a5a69cbda4
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110615
--- Comment #2 from Jonathan Wakely ---
(In reply to Julien Jorge from comment #0)
> The int <-> float conversions
> do not happen with current HEAD but I believe it is due to a side effect of
> cmath transitively including stdlib.h.
No, it's
Hello,
the ELF psABI for x86-64 doesn't have any callee-saved SSE
registers (there were actual reasons for that, but those don't
matter anymore). This starts to hurt some uses, as it means that
as soon as you have a call (say to memmove/memcpy, even if
implicit as libcall) in a loop that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102003
Andre Vehreschild changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110615
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |INVALID
Hi all,
while browsing the pdt meta-bug I came across 102003 and thought to myself:
Well, that one is easy. How foolish of me...
Anyway, the solution attached prevents a pdt_len (or pdt_kind) expression in a
function call (e.g. len() or kind()) to mark the whole expression as a pdt one.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95048
--- Comment #26 from CVS Commits ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:d308b11fa94728507984b4ccc949219511273ab6
commit r11-10903-gd308b11fa94728507984b4ccc949219511273ab6
Author: Jonathan
> > - *type_out = STMT_VINFO_VECTYPE (stmt_info);
> > + if (cond_cst)
> > +{
> > + append_pattern_def_seq (vinfo, stmt_info, pattern_stmt, vectype);
> > + pattern_stmt
> > + = gimple_build_cond (gimple_cond_code (cond_stmt),
> > +gimple_get_lhs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110609
--- Comment #2 from Andres Freund ---
(In reply to Andrew Pinski from comment #1)
> Dup.
>
> *** This bug has been marked as a duplicate of bug 110546 ***
Are they really the same? This bug happens at -O0 and requires -fPIC and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110615
Bug ID: 110615
Summary: std::abs converts integers to floats and back
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110614
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110614
Bug ID: 110614
Summary: [14 Regression] ICE in vect_supportable_dr_alignment
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110523
Patrick Palka changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106966
--- Comment #12 from Matthias Klose ---
I'll apply the proposed patch for the next gcc-13 Debian upload, then reporting
back test results.
Committed, thanks Jeff and Richard.
Pan
-Original Message-
From: Gcc-patches On Behalf
Of Jeff Law via Gcc-patches
Sent: Monday, July 10, 2023 10:08 PM
To: juzhe.zh...@rivai.ai; gcc-patches@gcc.gnu.org
Cc: rguent...@suse.de
Subject: Re: [PATCH v2] GCSE: Export
Tested on x86_64-pc-linux-gnu, pushed to trunk as obvious.
-- >8 --
Now that we cache level-lowered ttps we can end up processing the same
ttp multiple times via (multiple calls to) redeclare_class_template, so
we can't assume a ttp's DECL_CONTEXT is initially empty.
PR c++/110523
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110523
--- Comment #10 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:2c60368ab5706a870a1a3be190acc4d673672c30
commit r14-2421-g2c60368ab5706a870a1a3be190acc4d673672c30
Author: Patrick Palka
Date:
thanks, pushed to trunk :)
On Mon, Jul 10, 2023 at 10:33 PM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 7/10/23 08:19, Kito Cheng wrote:
> > Document `z` and `i` operand modifiers, we have much more modifiers
> > other than those two, but they are the only two implement on both
> > GCC and LLVM,
1 - 100 of 212 matches
Mail list logo
