Hi!
Before bitint lowering, the IL has:
b.0_1 = b;
_2 = -b.0_1;
_3 = (unsigned _BitInt(512)) _2;
a.1_4 = a;
a.2_5 = (unsigned _BitInt(512)) a.1_4;
_6 = _3 * a.2_5;
on the first function. Now, gimple_lower_bitint has an optimization
(when not -O0) that it avoids assigning underlying
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112909
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112914
--- Comment #1 from Filip Kastl ---
The options are -O2 LTO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112915
--- Comment #2 from Filip Kastl ---
The options are -Ofast -march=native -mtune=native LTO and PGO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112916
Bug ID: 112916
Summary: [14 Regression] ~4-7% exec time regression of 433.milc
on AMD Zen2
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66261
Peter Cordes changed:
What|Removed |Added
CC||pcordes at gmail dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112915
--- Comment #1 from Filip Kastl ---
I checked again and its actually a 4% regression on both machines, my bad.
Hi!
For casts from integers to floating point,
simplify_float_conversion_using_ranges uses SCALAR_INT_TYPE_MODE
and queries optabs on the optimization it wants to make.
That doesn't really work for large/huge BITINT_TYPE, those have BLKmode
which is not scalar int mode. Querying an optab is not
On Fri, 8 Dec 2023, Jakub Jelinek wrote:
> On Thu, Dec 07, 2023 at 11:54:01AM +0100, Jakub Jelinek wrote:
> > On Thu, Dec 07, 2023 at 09:36:23AM +0100, Jakub Jelinek wrote:
> > > Without the dg-skip-if I got on 64-bit host:
> > > cc1: out of memory allocating 571230784744 bytes after a total of
Pushed to r14-6303 and r14-6304.
在 2023/12/5 上午10:30, Lulu Cheng 写道:
1. Rebase Xi Ruoyao's patch a to the latest commit.
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636798.html
2. remove the #if
!defined(IN_LIBGCC2) && !defined(IN_TARGET_LIBS) && !defined(IN_RTS)
guards in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112915
Bug ID: 112915
Summary: [14 Regression] ~4-11% exec time regression of
454.calculix on AMD Zen2
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
On Thu, Dec 07, 2023 at 11:54:01AM +0100, Jakub Jelinek wrote:
> On Thu, Dec 07, 2023 at 09:36:23AM +0100, Jakub Jelinek wrote:
> > Without the dg-skip-if I got on 64-bit host:
> > cc1: out of memory allocating 571230784744 bytes after a total of 2772992
> > bytes
>
> I've looked at this and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112914
Bug ID: 112914
Summary: [14 Regression] ~7-9% exec time regression of
436.cactusADM on AMD Zen2
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112411
--- Comment #11 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:39a1ab9c33b6067b1cc843408886e7ba709fbb62
commit r14-6302-g39a1ab9c33b6067b1cc843408886e7ba709fbb62
Author: Jakub Jelinek
Date:
Hi,
Jeff Law writes:
> On 12/6/23 02:27, Jiufu Guo wrote:
>> Hi,
>>
>> The issue mentioned in PR112525 would be able to be handled by
>> updating dse.cc to treat arg_pointer_rtx similarly with frame_pointer_rtx.
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30271#c10 also mentioned
>> this
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
Ready push to trunk.
gcc/ChangeLog:
PR target/112904
* config/i386/mmx.md (*xop_pcmov_): New define_insn.
gcc/testsuite/ChangeLog:
* g++.target/i386/pr112904.C: New test.
---
gcc/config/i386/mmx.md
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112913
Bug ID: 112913
Summary: ICE: in curr_insn_transform, at
lra-constraints.cc:4308
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Hi all,
This patch will mention the following changes in wwwdocs for x86_64 backend:
- AVX10.1 support
- APX EGPR, PUSH2POP2, PPX and NDD support
- Xeon Phi ISAs deprecated
Also I adjust the words in x86_64 part for GCC 13. Ok for gcc-wwwdocs?
Thx,
Haochen
Mention AVX10.1 support, APX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112910
--- Comment #2 from Richard Biener ---
There's also size_type_node
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112909
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
Blocks|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112912
--- Comment #5 from Wang ---
(In reply to Andrew Pinski from comment #4)
> Again bugzilla is not the right place to ask this kind of question, gcc@ is
> a better place.
>
> Refactoring and sharing the mangling code definitely can be done. I
On Fri, Dec 8, 2023 at 1:24 AM Jeff Law wrote:
>
>
>
> On 12/5/23 07:53, Richard Biener via Gcc wrote:
> > On Tue, Dec 5, 2023 at 3:54 PM Alexander Monakov via Gcc
> > wrote:
> >>
> >> Greetings,
> >>
> >> the definitions for NOP_EXPR and CONVERT_EXPR in tree.def, having survived
> >> all the
On Thu, 7 Dec 2023, Hans-Peter Nilsson wrote:
> > Date: Mon, 4 Dec 2023 12:58:03 +0100 (CET)
> > From: Richard Biener
>
> > On Sat, 2 Dec 2023, Hans-Peter Nilsson wrote:
> > > > Date: Fri, 1 Dec 2023 08:07:14 +0100 (CET)
> > > > From: Richard Biener
> > > > I read from your messages that the
On Thu, Dec 7, 2023 at 6:52 PM Alexandre Oliva wrote:
>
> On Dec 7, 2023, Thomas Schwinge wrote:
>
> > Thank you for looking into this so promptly!
>
> You're welcome ;-)
>
>
> > during IPA pass: emutls
> > [...]/source-gcc/gcc/testsuite/c-c++-common/strub-unsupported-3.c:18:1:
> >
Since loop vectorizer won't call better_main_loop_than_p if
!flag_vect_cost_model.
Committed as it is obvious.
gcc/ChangeLog:
* config/riscv/riscv-vector-costs.cc (costs::better_main_loop_than_p):
Remove redundant check.
---
gcc/config/riscv/riscv-vector-costs.cc | 3 ---
1 file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112912
--- Comment #4 from Andrew Pinski ---
Again bugzilla is not the right place to ask this kind of question, gcc@ is a
better place.
Refactoring and sharing the mangling code definitely can be done. I suspect the
first step is to move away from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112912
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112912
--- Comment #2 from Wang ---
(In reply to Andrew Pinski from comment #1)
> I don't get why you need to mangle anything here
>
> what exactly is being mangled here? The types? or something else?
Sorry I didn't describe it clearly. I just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112912
--- Comment #1 from Andrew Pinski ---
I don't get why you need to mangle anything here
what exactly is being mangled here? The types? or something else?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112912
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112912
Bug ID: 112912
Summary: How to implement a mangle interface in c
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
On Wed, Dec 6, 2023 at 3:52 PM Richard Biener
wrote:
>
> On Wed, Dec 6, 2023 at 3:33 AM Jiang, Haochen wrote:
> >
> > > -Original Message-
> > > From: Jiang, Haochen
> > > Sent: Friday, December 1, 2023 4:51 PM
> > > To: Richard Biener
> > > Cc: gcc-patches@gcc.gnu.org; Liu, Hongtao ;
>
2023-12-08 11:35 Kito Cheng wrote:
>> Without comma, there is a warning "warning: ISO C++11 requires at least one
>> argument for the "..." in a variadic macro".
>> So I add the comma.
>
>Oh, thanks, I wasn't aware that, maybe take one more argument to '...'
>
>#define DEF_RVV_FUNCTION(NAME,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112911
Gaius Mulley changed:
What|Removed |Added
Last reconfirmed||2023-12-08
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112911
Bug ID: 112911
Summary: Problem creating aggregate constants containing a
variant record
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
On 2023-12-08 10:04, chenglulu wrote:
在 2023/12/7 下午8:20, Xi Ruoyao 写道:
There seems no real reason to require -mexplicit-relocs=always for
-mcmodel=extreme or model attribute. As the linker does not know how to
relax a 3-operand la.local or la.global pseudo instruction, just emit
explicit
> Without comma, there is a warning "warning: ISO C++11 requires at least one
> argument for the "..." in a variadic macro".
> So I add the comma.
Oh, thanks, I wasn't aware that, maybe take one more argument to '...'
#define DEF_RVV_FUNCTION(NAME, SHAPE, PREDS, ...)
Anyway my intention is to
> Yes, I can see that. I think the patch is OK with a minor nit - can you
> please document the nothrow flag usage in TREE_CHREC in
> tree-core.h? There's a big comment doing flags documentation:
Thanks, committed with the new documentation:
Hi,
Thanks for your insight and helpful review!
"Kewen.Lin" writes:
> Hi Jeff,
>
> on 2023/12/6 13:24, Jiufu Guo wrote:
>> Hi,
>>
>> For constant building e.g. r120=0x, which does not fit 'li or lis',
>> 'pli' is used to build this constant via 'emit_move_insn'.
>>
>> While for a
Hi,
Thanks for your always kind and helpful review!!
"Kewen.Lin" writes:
> Hi Jeff,
>
> on 2023/12/6 13:24, Jiufu Guo wrote:
>> Hi,
>>
>> Trunk gcc supports more constants to be built via two instructions:
>> e.g. "li/lis; xori/xoris/rldicl/rldicr/rldic".
>> And then num_insns_constant
2023-12-08 11:18 Kito Cheng wrote:
>> @@ -31,624 +31,627 @@ along with GCC; see the file COPYING3. If not see
>> - OPS_INFO describes all information of return type and each
>> argument type.
>>
>> + - AVAIL this argument is the optional for AVAIL.Determin the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112774
--- Comment #2 from GCC Commits ---
The master branch has been updated by Hao Liu :
https://gcc.gnu.org/g:2efe3a7de0107618397264017fb045f237764cc7
commit r14-6299-g2efe3a7de0107618397264017fb045f237764cc7
Author: Hao Liu
Date: Wed Dec 6
> @@ -31,624 +31,627 @@ along with GCC; see the file COPYING3. If not see
> - OPS_INFO describes all information of return type and each
> argument type.
>
> + - AVAIL this argument is the optional for AVAIL.Determin the enable
> + of the intrinsic function.
> +
> */
>
ping.
On Thu, Nov 16, 2023 at 6:49 PM liuhongt wrote:
>
> Update in V2:
> 1) Add some comments before the pattern.
> 2) Remove ? from view_convert.
>
> Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
> Ok for trunk?
>
> When I'm working on PR112443, I notice there's some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112758
--- Comment #2 from gyumin ---
Dear GCC Development Team,
I recently reported an inconsistency in the GCC compiler (RISC-V 64 version
14.0.0) involving bitwise AND operations between int and long long int
variables. This issue, which occurs
2023-12-08 10:44 Feng Wang wrote:
Have run all the vector api-testing.
>Patch v2: Using variadic macro and add the dependency into t-riscv
>
>In order to add other extension about vector,this patch add
>unsigned int (*avail) (void) into function_group_info to determine
>whether to
Patch v2: Using variadic macro and add the dependency into t-riscv
In order to add other extension about vector,this patch add
unsigned int (*avail) (void) into function_group_info to determine
whether to register the intrinsic based on ISA info.
gcc/ChangeLog:
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112904
Hongtao Liu changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from Hongtao Liu
Hi Haochen,
on 2023/12/8 09:58, HAO CHEN GUI wrote:
> Hi,
> The "fctid" is supported on 64-bit Power processors and PowerPC476. It
> need a guard to check it. The patch fixes the issue.
>
> Compared with last version,
> https://gcc.gnu.org/pipermail/gcc-patches/2023-December/639536.html
>
If the function desn't clobber any sse registers or only clobber
128-bit part, then vzeroupper isn't issued before the function exit.
the status not CLEAN but ANY after the function.
Also for sibling_call, it's safe to issue an vzeroupper. Also there
could be missing vzeroupper since there's no
On Thu, Dec 07, 2023 at 04:13:51PM +0800, Xi Ruoyao wrote:
>
> I understand and I don't think adding {} is wrong. The problem is the
> indent change causes a large chunk of diff and it makes reviewing more
> difficult. Thus generally we should not mix real code change and format
> change in a
在 2023/12/7 下午8:20, Xi Ruoyao 写道:
There seems no real reason to require -mexplicit-relocs=always for
-mcmodel=extreme or model attribute. As the linker does not know how to
relax a 3-operand la.local or la.global pseudo instruction, just emit
explicit relocs for SYMBOL_PCREL64, and under
On Thu, Dec 07, 2023 at 10:18:47AM +0100, Florian Weimer wrote:
> * Yang Yujie:
>
> > With this patch, I also noticed a few errors in building unpatched older
> > software like expect-5.45.4, perl-5.28.3 and bash-5.0. Will this also be
> > the case when GCC 14 gets released?
>
> For Fedora, we
Hi,
The "fctid" is supported on 64-bit Power processors and PowerPC476. It
need a guard to check it. The patch fixes the issue.
Compared with last version,
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/639536.html
the main change is to change the target requirement in pr88558*.c.
On Thu, Dec 07, 2023 at 11:34:28AM +0100, Iain Buclaw wrote:
>
> Just a nitpick, I'd thought the committing of switchcontext.S should
> come before this. I have no strong opinion either way.
>
> OK to commit.
>
> Iain.
Thanks for the suggestion, indeed this makes sense.
Yujie
On Thu, Dec 07, 2023 at 11:30:16AM +0100, Iain Buclaw wrote:
> Hi,
>
> Thanks for this.
>
> Excerpts from Yang Yujie's message of Dezember 1, 2023 11:08 am:
> > diff --git a/gcc/d/dmd/cond.d b/gcc/d/dmd/cond.d
> > index 568b639e0b6..02af0cc9e29 100644
> > --- a/gcc/d/dmd/cond.d
> > +++
On Thu, 2023-12-07 at 17:34 -0500, Antoni Boucher wrote:
> Hi.
> This patch adds checks gcc_jit_block_add_assignment_op to make sure
> it
> is only ever called on numeric types.
>
> With the previous patch, this might require a change to also allow
> vector types here.
>
> Thanks for the review.
Can I merge this on master even though we're not in phase 1 anymore?
On Thu, 2023-12-07 at 20:07 -0500, David Malcolm wrote:
> On Thu, 2023-12-07 at 17:32 -0500, Antoni Boucher wrote:
> > Hi.
> > This patch changes the function is_int to return false on vector
> > types.
> > Thanks for the
On Thu, 2023-12-07 at 17:32 -0500, Antoni Boucher wrote:
> Hi.
> This patch changes the function is_int to return false on vector
> types.
> Thanks for the review.
Thanks; looks good to me
Dave
On Thu, 2023-12-07 at 17:29 -0500, Antoni Boucher wrote:
> Hi.
> This patches update gcc_jit_context_new_array_type to take the size
> as
> an unsigned long instead of a int, to allow creating bigger array
> types.
>
> I haven't written the ChangeLog yet because I wasn't sure it's
> allowed
> to
On Thu, 2023-12-07 at 17:26 -0500, Antoni Boucher wrote:
> Hi.
> This patch fixes getting the size of size_t (bug 112910).
>
> There's one issue with this patch: like every other feature that
> checks
> for target-specific stuff, it requires a compilation before actually
> fetching the size of
On 12/5/23 01:12, Fei Gao wrote:
op=[PLUS, MINUS, IOR, XOR]
Conditional op, if zero
rd = (rc == 0) ? (rs1 op rs2) : rs1
-->
czero.nez rd, rs2, rc
op rd, rs1, rd
Conditional op, if non-zero
rd = (rc != 0) ? (rs1 op rs2) : rs1
-->
czero.eqz rd, rs2, rc
op rd, rs1, rd
Co-authored-by: Xiao
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112889
--- Comment #3 from David Malcolm ---
Should be fixed on trunk by the above patch.
Keeping open to backport to older releases.
Cncrete bindings were using -1 and -2 in the offset field to signify
deleted and empty hash slots, but these are valid values, leading to
assertion failures inside hash_map::put on a debug build, and probable
bugs in a release build.
(gdb) call k.dump(true)
start: -2, size: 1, next: -1
(gdb) p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112889
--- Comment #2 from GCC Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:775aeabcb870b74e4d0986341c7a39add9bbb06d
commit r14-6297-g775aeabcb870b74e4d0986341c7a39add9bbb06d
Author: David Malcolm
Date:
On 12/6/23 15:03, DJ Delorie wrote:
Alexandre Oliva writes:
This looks like a latent bug in the port.
I'm not surprised, that port was weird.
This was just a plain asm insn in strub.c:
/* Make sure the stack overwrites are not optimized away. */
asm ("" : : "m" (end[0]));
whose
On 12/5/23 07:53, Richard Biener via Gcc wrote:
On Tue, Dec 5, 2023 at 3:54 PM Alexander Monakov via Gcc
wrote:
Greetings,
the definitions for NOP_EXPR and CONVERT_EXPR in tree.def, having survived
all the way from 1992, currently say:
/* Represents a conversion of type of a value.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112868
--- Comment #5 from Peter Bergner ---
(In reply to Richard Biener from comment #3)
> Can't we make sure to pass -mno-any (if that exists...) during bootstrap
> and testsuite instead?
-mno-any does not exist.
On 11/28/23 00:43, HAO CHEN GUI wrote:
Hi,
This patch passes down the equality only flags from
emit_block_cmp_hints to cmpmem optab so that the target specific expand
can generate optimized insns for equality only compare. Targets
(e.g. rs6000) can generate more efficient insn sequence if
Snapshot gcc-11-20231207 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20231207/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Hi.
This patch adds checks gcc_jit_block_add_assignment_op to make sure it
is only ever called on numeric types.
With the previous patch, this might require a change to also allow
vector types here.
Thanks for the review.
From 932048619671c61af224708a3da484b9f54a30a3 Mon Sep 17 00:00:00 2001
Hi.
This patch changes the function is_int to return false on vector types.
Thanks for the review.
From 60ebfb998bd349ca2f05b115de5452378027e4de Mon Sep 17 00:00:00 2001
From: Antoni Boucher
Date: Thu, 26 Oct 2023 19:17:55 -0400
Subject: [PATCH] libgccjit: Make is_int return false on vector types
Hi.
This patches update gcc_jit_context_new_array_type to take the size as
an unsigned long instead of a int, to allow creating bigger array
types.
I haven't written the ChangeLog yet because I wasn't sure it's allowed
to change the type of a function like that.
If it isn't, what would you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111503
--- Comment #1 from anlauf at gcc dot gnu.org ---
Created attachment 56832
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56832=edit
Draft patch
The attached patch adds handling for NULL([MOLD]) and fixes comment#0.
Hi.
This patch fixes getting the size of size_t (bug 112910).
There's one issue with this patch: like every other feature that checks
for target-specific stuff, it requires a compilation before actually
fetching the size of the type.
Which means that getting the size before a compilation might be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112910
--- Comment #1 from Antoni ---
Created attachment 56831
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56831=edit
Patch fixing this bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112488
Martin Uecker changed:
What|Removed |Added
CC||muecker at gwdg dot de
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112910
Bug ID: 112910
Summary: Getting the size of the type size_t returns the wrong
value on some platforms
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112909
Bug ID: 112909
Summary: [14 Regression] glibc -Wuninitialized build failure
for i686-gnu
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
This patch fixes 64 ICEs in full coverage testing since they happens due to
same reason.
Before this patch:
internal compiler error: in expand_const_vector, at config/riscv/riscv-v.cc:1270
appears 400 times in full coverage testing report.
The root cause is we didn't support interleave vector
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112906
Alex Coplan changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On 12/6/23 02:27, Jiufu Guo wrote:
Hi,
The issue mentioned in PR112525 would be able to be handled by
updating dse.cc to treat arg_pointer_rtx similarly with frame_pointer_rtx.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30271#c10 also mentioned
this idea.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112908
Bug ID: 112908
Summary: __reference_{converts,constructs}_from_temporary
checks for move constructor when binding prvalue to
reference of the same type
Product: gcc
On Dec 6, 2023, Jan Hubicka wrote:
> There is also access attribute which speaks directly about individual
> arugments, perhaps you want to drop this one too?
Ah, I've looked a little into it, and now I have a vague recollection of
why I don't mess with them: they only apply to arguments of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109162
--- Comment #2 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #0)
> https://wg21.link/P2693R1 formatting thread::id and stacktrace
This has been implemented for gcc-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109162
--- Comment #1 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #0)
> https://wg21.link/P2372R3 formatting ranges
Oops, that should be https://wg21.link/p2286r8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105170
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2023-12-07
On Dec 6, 2023, Jan Hubicka wrote:
> I am sorry for sending this late.
No need to be sorry. Thank you very much for taking the time to review
and comment on it.
> I think the ipa changes are generally fine.
Phew :-)
>> +static inline bool
>> +strub_always_inline_p (cgraph_node *node)
>> +{
On 12/7/23 05:15, Robin Dapp wrote:
LGTM.
Btw your vsetvl patch from yesterday fixes the vectorized
strlen/strcmp problems. Those use vleff as first instruction.
Definitely good news.
jeff
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112894
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112894
Bug 112894 depends on bug 112882, which changed state.
Bug 112882 Summary: [14 Regression] std::clamp no longer usable in header only
mode
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On 12/7/23 09:33, Hans-Peter Nilsson wrote:
Date: Mon, 4 Dec 2023 12:58:03 +0100 (CET)
From: Richard Biener
On Sat, 2 Dec 2023, Hans-Peter Nilsson wrote:
Date: Fri, 1 Dec 2023 08:07:14 +0100 (CET)
From: Richard Biener
I read from your messages that the testcases pass on arm*-*-*?
Yes:
On 12/7/23 09:59, Christoph Müllner wrote:
On Thu, Dec 7, 2023 at 11:18 AM Liao Shihua wrote:
In accordance with the suggestions of Christoph Müllner, the following
amendments are made
Update v1 -> v2:
1. Rename *_intrinsic-* to *_intrinsic-XLEN.
2. Typo fix.
3. Intrinsics with
Tested x86_64-linux. Pushed to trunk.
-- >8 --
This local typedef for uintptr_t was accidentally named uint64_t,
probably from a careless code completion shortcut. We don't need the
typedef at all since it's only used once. Just use __UINTPTR_TYPE__
directly instead.
libstdc++-v3/ChangeLog:
Tested x86_64-linux. Pushed to trunk. I'll backport this too.
-- >8 --
In r14-5922-g6c8f2d3a08bc01 I added to ,
so that uintptr_t is declared if that header is compiled as a header
unit. I used because that's what already includes,
so it seemed simpler to be consistent. However, this means
Tested x86_64-linux. Pushed to trunk.
-- >8 --
The changes in r14-6198-g5e8a30d8b8f4d7 were broken, as I used
_GLIBCXX17_CONSTEXPR for the 'if _GLIBCXX17_CONSTEXPR (true)' condition,
forgetting that it would also be used for the is_constant_evaluated()
check. Using 'if constexpr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:1395c573c523762957bde8c2a08832c5f4350815
commit r14-6291-g1395c573c523762957bde8c2a08832c5f4350815
Author: Jonathan Wakely
On Dec 6, 2023, Jan Hubicka wrote:
>> On Nov 30, 2023, Jan Hubicka wrote:
>>
>> >> + if (VAR_P (replaced))
>> >> + varpool_node::create_alias (sym_node->decl, replacement);
>> >> + else
>> >> + cgraph_node::create_alias (sym_node->decl, replacement);
>>
>> Unfortunately, this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873
--- Comment #7 from Steve Kargl ---
On Thu, Dec 07, 2023 at 07:59:25PM +, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873
>
> --- Comment #6 from anlauf at gcc dot gnu.org ---
> (In reply to Steve
1 - 100 of 303 matches
Mail list logo
