On Wed, Jul 26, 2023 at 01:55:00 AM Andreas Schwab
wrote:
>
>On Jul 19 2023, Xiao Zeng wrote:
>
>> diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
>> index 38d8eb2fcf5..7e6b24bd232 100644
>> --- a/gcc/config/riscv/riscv.cc
>> +++ b/gcc/config/riscv/riscv.cc
>> @@ -2448,6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110789
--- Comment #10 from Xi Ruoyao ---
(In reply to Xi Ruoyao from comment #9)
> (In reply to Andrew Pinski from comment #7)
> > If you compile GMP (MPFR and MPC) as part of GCC build rather than
> > seperately, the build will do the correct thing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110789
--- Comment #9 from Xi Ruoyao ---
(In reply to Andrew Pinski from comment #7)
> If you compile GMP (MPFR and MPC) as part of GCC build rather than
> seperately, the build will do the correct thing and not use the "native"
> options by default.
On 6/30/23 03:05, Nathaniel Shead wrote:
On Thu, Jun 29, 2023 at 01:43:07PM -0400, Jason Merrill wrote:
On 6/24/23 09:24, Nathaniel Shead wrote:
On Fri, Jun 23, 2023 at 11:59:51AM -0400, Patrick Palka wrote:
Hi,
On Sat, 22 Apr 2023, Nathaniel Shead via Gcc-patches wrote:
Bootstrapped and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103497
--- Comment #5 from CVS Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:ca912a39cccdd990ef705768faa7311ac210b3f3
commit r14-2814-gca912a39cccdd990ef705768faa7311ac210b3f3
Author: Nathaniel Shead
Date:
> -Original Message-
> From: Yan Simonaytes
> Sent: Wednesday, July 26, 2023 2:11 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao ; Uros Bizjak ;
> Yan Simonaytes
> Subject: [PATCH] Replace invariant ternlog operands
>
> Sometimes GCC generates ternlog with three operands, but
on 2023/7/26 18:02, Richard Biener wrote:
> On Wed, Jul 26, 2023 at 4:52 AM Kewen.Lin wrote:
>>
>> Hi,
>>
>> PR110776 exposes one issue that we could query unaligned
>> load for vector type but actually no unaligned vector load
>> is supported there. The reason is that the costed load is
>> with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110795
Kewen Lin changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110776
Kewen Lin changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110776
--- Comment #10 from CVS Commits ---
The master branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:9890d4e8bcda1f34b8eefb481935ef0e4cd8069e
commit r14-2813-g9890d4e8bcda1f34b8eefb481935ef0e4cd8069e
Author: Kewen Lin
Date: Wed Jul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827
Bug ID: 110827
Summary: C++20 coroutines aren't being measured by gcov
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
> rtx_insn *last = BB_END (bb);
> emit_insn_before_noloc (gen_frrmsi (DYNAMIC_FRM_RTL (cfun)), last, bb);
The frrmsi insn need to be placed after CALL (aka last), then I bet here we
should use emit_insn_after_noloc.
Unfortunately, it will have ICE like below. I am still investigating the
Thanks Juzhe and Jeff for suggestion. The approach like emit_insn_before_noloc
will result in below ICE here.
../../../.././gcc/libstdc++-v3/libsupc++/new_opant.cc:42:1: error: flow control
insn inside a basic block.
../../../.././gcc/libstdc++-v3/libsupc++/new_opant.cc:42:1: internal compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110789
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #8
Whoops, this should have gone in with the fixes to the RISC-V
diagnostics from earlier this week.
Committed to the trunk.
Jeff
commit 6f709f79c915a1ea82220a44e9f4a144d5eedfd1
Author: Jeff Law
Date: Wed Jul 26 19:25:33 2023 -0600
[committed] [RISC-V] Fix expected diagnostic messages in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110818
Xi Ruoyao changed:
What|Removed |Added
Keywords||needs-bisection,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110818
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #5
Hi Jason,
I've made the following changes.
1. Add pr83054-2.C
2. Move the devirt tests to tree-ssa.
3. Remove dg do run for devirt tests
4. Add // PR c++/110057
5. Generate commit message with git gcc-commit-mklog
6. Check commit format with git gcc-verify
Thanks!
On Thu, Jul 27, 2023 at 12:30
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88160
--- Comment #4 from Vincent Riviere ---
Created attachment 55647
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55647=edit
Workaround for compiling libgcc with -mcpu=5475 -mshort
Here is a patch for GCC 13.1.0. It allows libgcc to be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88160
--- Comment #3 from Vincent Riviere ---
There are 2 lightweight workarounds for the OP testcase:
-fno-combine-stack-adjustments
-fno-omit-frame-pointer
$ m68k-elf-gcc -mshort -mcpu=5475 -g -O2 -c test.c
/tmp/ccW6hc6h.s: Assembler messages:
Thanks Jeff.
Hi, Pan:
Plz try (insert edge and put 'frrm' on that edge) instead of insert end of
block to see whether it works
(I have tried onece but I don't remember what happens).
Try that with following codes:
edge eg;
edge_iterator ei;
FOR_EACH_EDGE (eg, ei, bb->succs)
{
start_sequence
>> Any specific reason for MAX_BITS_PER_WORD instead of
>> GET_MODE_BITSIZE (Pmode)? In general I like the idea to switch
>> to scalar moves here but couldn't it already be debatable for
>> a 64-bit move on rv32 i.e. a question of costing?
V2SImode for example,
I think
I prefer this following
On 7/26/23 16:21, 钟居哲 wrote:
Hi, Jeff.
insert_insn_end_basic_block is to handle this following case:
bb 1:
...
CALL.>BB_END of bb
bb 2:
vfadd rne
You can see there is no instructions after CALL.
So you we use insert_insn_end_basic_block insert a "frrm" at the end of
the bb 1.
I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95316
bur...@net-b.de changed:
What|Removed |Added
CC||bur...@net-b.de
--- Comment #6 from
On Wed, Jul 26, 2023 at 5:36 PM Jason Merrill wrote:
>
> On 6/30/23 18:59, Lewis Hyatt wrote:
> > In order to support processing #pragma in preprocess-only mode (-E or
> > -save-temps for gcc/g++), we need a way to obtain the #pragma tokens from
> > libcpp. In full compilation modes, this is
Hi, Jeff.
insert_insn_end_basic_block is to handle this following case:
bb 1:
...
CALL.>BB_END of bb
bb 2:
vfadd rne
You can see there is no instructions after CALL.
So you we use insert_insn_end_basic_block insert a "frrm" at the end of the bb
1.
I know typically it's better to insert
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110825
--- Comment #3 from Steve Kargl ---
On Wed, Jul 26, 2023 at 08:54:01PM +, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110825
>
> --- Comment #1 from anlauf at gcc dot gnu.org ---
> (In reply to kargl
On Wed, Jul 26, 2023 at 01:54:01PM +0800, Kewen.Lin wrote:
> Hi Mike,
>
> on 2023/7/11 03:59, 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 .
>
> It actually
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110566
--- Comment #6 from waffl3x ---
(In reply to Patrick Palka from comment #5)
> Should be fixed on trunk so far.
Once it shows up on godbolt I will make sure that all the cases that exhibited
the bug are working for me now. I had a bunch of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110818
Andrew Pinski changed:
What|Removed |Added
Component|c |middle-end
--- Comment #4 from Andrew
On 7/26/23 07:08, Robin Dapp via Gcc-patches wrote:
So after thinking about it again - I'm still not really sure
I like treating every function as essentially an fesetround.
There is a reason why fesetround is special. Does LLVM behave
the same way?
But supposing we really, really want it
On 6/30/23 18:59, Lewis Hyatt wrote:
In order to support processing #pragma in preprocess-only mode (-E or
-save-temps for gcc/g++), we need a way to obtain the #pragma tokens from
libcpp. In full compilation modes, this is accomplished by calling
pragma_lex (), which is a symbol that must be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110566
Patrick Palka changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110566
--- Comment #4 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:b8218eb2266811991b8163f36d5c1d974cb50b93
commit r14-2810-gb8218eb2266811991b8163f36d5c1d974cb50b93
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108179
--- Comment #11 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:b8218eb2266811991b8163f36d5c1d974cb50b93
commit r14-2810-gb8218eb2266811991b8163f36d5c1d974cb50b93
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110566
--- Comment #3 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:b3adcc60dcf3314f47f5409aecef40607f82b80b
commit r14-2809-gb3adcc60dcf3314f47f5409aecef40607f82b80b
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108179
--- Comment #10 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:b3adcc60dcf3314f47f5409aecef40607f82b80b
commit r14-2809-gb3adcc60dcf3314f47f5409aecef40607f82b80b
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110825
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
On 7/19/23 04:11, Xiao Zeng wrote:
This patch completes the recognition of the basic semantics
defined in the spec, namely:
Conditional zero, if condition is equal to zero
rd = (rs2 == 0) ? 0 : rs1
Conditional zero, if condition is non zero
rd = (rs2 != 0) ? 0 : rs1
gcc/ChangeLog:
On 7/19/23 04:11, Xiao Zeng wrote:
This patch is the minimal support for Zicond extension, include
the extension name, mask and target defination.
gcc/ChangeLog:
* common/config/riscv/riscv-common.cc: New extension.
* config/riscv/riscv-opts.h (MASK_ZICOND): New mask.
> I would like to propose that being focus and moving forward for this
> patch itself, the underlying other RVV floating point API support and
> the RVV instrinsic API fully tests depend on this.
Sorry, I didn't mean to ditch LCM/mode switching. I believe it is doing
a pretty good job and we
May I please ping this?
I am just about ready with the followup patch that fixes PR87299, but
it depends on this one. Thanks!
https://gcc.gnu.org/pipermail/gcc-patches/2023-June/623364.html
-Lewis
On Fri, Jun 30, 2023 at 6:59 PM Lewis Hyatt wrote:
>
> In order to support processing #pragma in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110826
Bug ID: 110826
Summary: Fortran array of derived type with a pointer to
function with dimensional arguments
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110825
--- Comment #1 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #0)
> Thus, when compiled and executed the program hits 'STOP 1'. Likely,
> gfortran needs to add a possibly unused hidden argument to the argument list
> for a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110809
Patrick Palka changed:
What|Removed |Added
Target Milestone|--- |13.3
--- Comment #8 from Patrick Palka
On 7/26/23 15:32, Tamar Christina wrote:
+
+ cp_token *tok = pragma_tok;
+
+ do
{
- tok = cp_lexer_consume_token (parser->lexer);
- ivdep = cp_parser_pragma_ivdep (parser, tok);
- tok = cp_lexer_peek_token (the_parser->lexer);
+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110809
--- Comment #7 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:744e1f35266dbd6b6fb95c7e8422562815f8b56f
commit r14-2806-g744e1f35266dbd6b6fb95c7e8422562815f8b56f
Author: Patrick Palka
Date:
Hi Juzhe,
just some small remarks, all in all no major concerns.
> + vmv%m1r.v\t%0,%1"
> + "&& (!register_operand (operands[0], mode)
> + || !register_operand (operands[1], mode))"
> + [(const_int 0)]
> + {
> +unsigned size = GET_MODE_BITSIZE (mode).to_constant ();
> +if (size
On 6/28/23 06:35, Alex Coplan wrote:
Hi,
This patch implements clang's __has_feature and __has_extension in GCC.
This is a v2 of the original RFC posted here:
https://gcc.gnu.org/pipermail/gcc-patches/2023-May/617878.html
Changes since v1:
- Follow the clang behaviour where -pedantic-errors
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110824
--- Comment #1 from Andrew Pinski ---
Reducing to see if it is reproducible on the trunk ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110825
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110825
Bug ID: 110825
Summary: TYPE(*) dummy argument to generate an unused hidden
argument
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80256
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|REOPENED|WAITING
--- Comment #7 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110824
Bug ID: 110824
Summary: Gcc crashing on a lambda capture
Product: gcc
Version: 11.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110823
--- Comment #3 from Andrew Pinski ---
The gimple level looks like:
```
if (_54 >= 0)
goto ; [90.00%]
else
goto ; [10.00%]
[local count: 63261141172]:
_18 = (unsigned int) _54;
goto ; [100.00%]
...
len_37 = mbrtoc32 (,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68569
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33056
Bug 33056 depends on bug 68569, which changed state.
Bug 68569 Summary: ICE with automatic character object and DATA
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68569
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68569
--- Comment #9 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:27ba73644f53c118e3f9b3fe9cd792210696ec55
commit r14-2805-g27ba73644f53c118e3f9b3fe9cd792210696ec55
Author: Harald Anlauf
Date:
On Wed, Jul 26, 2023 at 09:33:22PM +0200, Harald Anlauf via Fortran wrote:
> I am going to get the brown bag for today... This is now the right
> corrected patch.
>
> Sorry for all the noise!
>
Third times a charm (as the saying goes).
Looks good to me. Thanks for the patch.
--
Steve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110823
--- Comment #2 from Paul Eggert ---
Created attachment 55645
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55645=edit
code-mbcel1.s with the optimization suggested in the bug report
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110823
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110823
--- Comment #1 from Paul Eggert ---
Created attachment 55644
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55644=edit
gcc -O2 -S output (from code-mbcel1.i)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110823
Bug ID: 110823
Summary: [missed optimization] >50% speedup for x86-64 ASCII
processing a la GNU diffutils
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
Hi, This is a respin of the patch taking in the feedback received from the C++
part.
Simultaneously it's also a ping
Hi All,
FORTRAN currently has a pragma NOVECTOR for indicating that vectorization should
not be applied to a particular loop.
ICC/ICX also has such a pragma for C and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110822
Andrew Pinski changed:
What|Removed |Added
Summary|ICE on constexpr|[13/14 Regression] ICE on
I am going to get the brown bag for today... This is now the right
corrected patch.
Sorry for all the noise!
Harald
Am 26.07.23 um 21:17 schrieb Harald Anlauf via Gcc-patches:
Dear all,
the original submission missed the adjustments of the expected
patterns of 2 tests. This is corrected
> > +
> > + cp_token *tok = pragma_tok;
> > +
> > + do
> > {
> > - tok = cp_lexer_consume_token (parser->lexer);
> > - ivdep = cp_parser_pragma_ivdep (parser, tok);
> > - tok = cp_lexer_peek_token (the_parser->lexer);
> > + switch (cp_parser_pragma_kind (tok))
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110822
Bug ID: 110822
Summary: ICE on constexpr initialized with non-constant
expression also accepts-invalid
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106310
Jason Merrill changed:
What|Removed |Added
Known to work||11.3.0, 14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68569
--- Comment #8 from anlauf at gcc dot gnu.org ---
Submitted (v2): https://gcc.gnu.org/pipermail/fortran/2023-July/059652.html
Dear all,
the original submission missed the adjustments of the expected
patterns of 2 tests. This is corrected in the new attachments.
Am 26.07.23 um 21:10 schrieb Harald Anlauf via Gcc-patches:
Dear all,
the attached patch fixes an ICE-on-invalid after use of strings of
non-constant length
Dear all,
the attached patch fixes an ICE-on-invalid after use of strings of
non-constant length in DATA statements.
Regtested on x86_64-pc-linux-gnu. OK for mainline?
Thanks,
Harald
From b5b13db48c169ef18a8b75739bd4f22f9fd5654e Mon Sep 17 00:00:00 2001
From: Harald Anlauf
Date: Wed, 26 Jul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110821
--- Comment #2 from David CARLIER ---
Ah, makes sense sorry for the disturbance. thanks
Here is what I came up with for combining the two:
/* For (x << c) >> c, optimize into x & ((unsigned)-1 >> c) for
unsigned x OR truncate into the precision(type) - c lowest bits
of signed x (if they have mode precision or a precision of 1) */
(simplify
(rshift (nop_convert? (lshift @0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110821
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Pushed to trunk.
-- >8 --
This new test uses uniform initialization syntax, so requires C++11 or
later.
libstdc++-v3/ChangeLog:
PR libstdc++/110807
* testsuite/23_containers/vector/bool/110807.cc: Require c++11.
---
libstdc++-v3/testsuite/23_containers/vector/bool/110807.cc |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110807
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f30e62b0ee05befd20863466d1fb55a34d15c228
commit r14-2802-gf30e62b0ee05befd20863466d1fb55a34d15c228
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
Дилян Палаузов changed:
What|Removed |Added
CC||dilyan.palauzov at aegee dot
org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110821
Bug ID: 110821
Summary: gcc inline asm for the riscv architecture with the BNE
(and possibly other instructions)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110819
Jonathan Wakely changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110817
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
On 7/19/23 04:11, Xiao Zeng wrote:
This patch completes the recognition of the basic semantics
defined in the spec, namely:
Conditional zero, if condition is equal to zero
rd = (rs2 == 0) ? 0 : rs1
Conditional zero, if condition is non zero
rd = (rs2 != 0) ? 0 : rs1
gcc/ChangeLog:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110817
Andrew Pinski changed:
What|Removed |Added
Target|riscv64-unknown-linux-gnu |
Target Milestone|---
This final patch fixes an error introduced by patch 9/12 in this series.
I'll backport alongside the other patches once the 13 branch is unfrozen :)
On 7/25/23 18:22, Kito Cheng wrote:
OK for backport :)
On Wed, Jul 26, 2023 at 2:11 AM Patrick O'Neill wrote:
From: Martin Liska
Fixes:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
Jakub Jelinek changed:
What|Removed |Added
Attachment #55637|0 |1
is obsolete|
Sorry, I meant PR110280 in subject line (not PR10280).
On Wed, 26 Jul 2023 at 23:03, Prathamesh Kulkarni
wrote:
>
> Hi Richard,
> Sorry for the delay in backport to gcc-13.
> The attached patch (cherry picked from master) is bootstrapped+tested
> on aarch64-linux-gnu with SVE enabled on gcc-13
Hi Richard,
Sorry for the delay in backport to gcc-13.
The attached patch (cherry picked from master) is bootstrapped+tested
on aarch64-linux-gnu with SVE enabled on gcc-13 branch.
OK to commit to gcc-13 branch ?
Thanks,
Prathamesh
[aarch64/match.pd] Fix ICE observed in PR110280.
gcc/ChangeLog:
On 7/26/23 12:57, Patrick Palka wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
trunk/13 (later)?
OK.
-- >8 --
Now that init_subob_ctx no longer sets new_ctx.ctor for a subobject of
empty type, it seems we need to ensure its callers cxx_eval_bare_aggregate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110820
Bug ID: 110820
Summary: vector_size attribute does not apply inside a template
nttp argument
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109365
--- Comment #6 from Benjamin Priour ---
(In reply to David Malcolm from comment #5)
> (In reply to Benjamin Priour from comment #4)
> > (In reply to Benjamin Priour from comment #3)
>
> Here's a link to the reproducer:
>
On 7/26/23 12:57, Patrick Palka wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
trunk/13 (after the branch is unfrozen)?
OK.
-- >8 --
This teaches unify how to compare two REAL_CSTs.
PR c++/110809
gcc/cp/ChangeLog:
* pt.cc (unify) :
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110796
Richard Earnshaw changed:
What|Removed |Added
Last reconfirmed||2023-07-26
CC|
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
trunk/13 (later)?
-- >8 --
Now that init_subob_ctx no longer sets new_ctx.ctor for a subobject of
empty type, it seems we need to ensure its callers cxx_eval_bare_aggregate
and cxx_eval_vec_init_1 consistently omit entries
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
trunk/13 (after the branch is unfrozen)?
-- >8 --
This teaches unify how to compare two REAL_CSTs.
PR c++/110809
gcc/cp/ChangeLog:
* pt.cc (unify) : Generalize to handle
REAL_CST as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106310
--- Comment #9 from CVS Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:51b997ea1d07465cb0208c711975b545872a2d2b
commit r14-2799-g51b997ea1d07465cb0208c711975b545872a2d2b
Author: Jason Merrill
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110819
Andrew Pinski changed:
What|Removed |Added
Component|c++ |tree-optimization
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110819
Bug ID: 110819
Summary: Missed optimization: when vector size is 0 but
vector::reserve has been called.
Product: gcc
Version: unknown
Status: UNCONFIRMED
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Ukrainian team of translators. The file is available at:
https://translationproject.org/latest/gcc/uk.po
(This file, 'gcc-13.1.0.uk.po', has
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
For backward compatibility we still want to allow patterns like
this->A::foo, but the template keyword in a qualified name is
specifically to specify that a dependent name is a template, so don't look
in the enclosing scope at all.
Also
On 7/26/23 12:00, Ng YongXiang wrote:
Hi Jason,
Thanks for the reply and review. I've attached an updated patch with the
change log and sign off.
The change made in gcc/testsuite/g++.dg/warn/pr83054.C is because I
think there is no more warning since we have already devirtualized the
1 - 100 of 233 matches
Mail list logo
