On 11/26/24 11:43 AM, Florian Weimer wrote:
* Jeff Law:
On 11/26/24 9:06 AM, David Malcolm wrote:
OK for trunk? (caveat: not properly tested)
gcc/ChangeLog:
PR translation/90160
* config/csky/csky.cc (csky_configure_build_target): Use %qs when
referring to cpu and a
On Tue, 2024-11-26 at 13:52 -0700, Jeff Law wrote:
>
>
> On 11/26/24 11:43 AM, Florian Weimer wrote:
> > * Jeff Law:
> >
> > > On 11/26/24 9:06 AM, David Malcolm wrote:
> > > > OK for trunk? (caveat: not properly tested)
> > > > gcc/ChangeLog:
> > > > PR translation/90160
> > > >
r15-3614-g9fe57e4879de93 changed the error message for __builtin_launder but
this testcase
was not updated for the new format of the error message since it is an aarch64
specific
testcase.
This patch updates the expected error message.
Pushed as obvious after testing to see the testcase now wor
> On Nov 25, 2024, at 16:46, Martin Uecker wrote:
>
>
> Hi Qing,
>
> Am Montag, dem 25.11.2024 um 17:40 + schrieb Qing Zhao:
>> Hi, Martin,
>>
>> I didn’t go through all the details of your patch.
>>
>> But I have one question:
>>
>> Did you consider the effect of the option -fstrict-f
Hello,
I don't have anything to add to the threads topic itself, but was
triggered by something:
On Tue, 26 Nov 2024, Jonathan Wakely wrote:
> > > const size_t __bufsz = __deque_buf_size(sizeof(_Tp));
> > ...
> > I wonder why "const" is useful here.
>
> Because if you don't initialize a cons
Ping!
please review.
Thanks & Regards
Jeevitha
On 15/10/24 12:49 pm, jeevitha wrote:
> Hi All,
>
> Removed powerpc*-*-* from the target test as it is always true. Simplified
> options by removing -mpower9-misc and -mvsx, which are enabled by default with
> -mdejagnu-cpu=power9. The has_arch_pwr
On 29/09/2024 09:35, Jeff Law wrote:
>
>
> On 9/23/24 4:33 AM, Alex Coplan wrote:
> > On 30/08/2024 18:11, Alex Coplan wrote:
> > > Hi,
> > >
> > > vec.h has this method:
> > >
> > >template
> > >inline T *
> > >vec_safe_push (vec *&v, const T &obj CXX_MEM_STAT_INFO)
> > >
> > > wh
On Tue, 26 Nov 2024 at 16:15, Michael Matz wrote:
>
> Hello,
>
> thanks for bearing with me :)
>
> On Tue, 26 Nov 2024, Jonathan Wakely wrote:
>
> > Being a member function makes no difference, but yes, I'm specifically
> > talking about the case of calling a constexpr function.
> >
> > constexpr
On Nov 26, 2024, at 11:56 AM, David Malcolm wrote:
>
> Ping for this patch; thanks!
Ok.
> On Fri, 2024-11-15 at 20:05 -0500, David Malcolm wrote:
>> In r12-6650-g5c69acb32329d4 we updated our sources from .c to .cc
>> since for some time GCC has been implemented in C++, not C.
>>
>> GCC plugin
Dear all,
the attached patch fixes two minor front-end memleaks I saw when working
on recent PRs (pr117774 is one of them) and running f951 under valgrind.
Regtested on x86_64-pc-linux-gnu. OK for mainline?
Thanks,
Harald
From d5236446302a01eb11c017862a0813fafd0b95a1 Mon Sep 17 00:00:00 2001
F
Ping for this patch; thanks!
Dave
On Fri, 2024-11-15 at 20:05 -0500, David Malcolm wrote:
> In r12-6650-g5c69acb32329d4 we updated our sources from .c to .cc
> since for some time GCC has been implemented in C++, not C.
>
> GCC plugins are also implemented in C++, not C, but the plugins
> in our
On Wed, Nov 20, 2024 at 1:25 AM Claudio Bantaloukas
wrote:
>
>
> On 19/11/2024 17:01, Andrew Pinski wrote:
> > On Fri, Nov 8, 2024 at 8:11 AM Claudio Bantaloukas
> > wrote:
> >>
> >> According to the aapcs64: If the argument is an 8-bit (...) precision
> >> Floating-point or short vector type and
On Nov 26, 2024, at 11:55 AM, David Malcolm wrote:
>
> Ping
Ok. I'll punt on the diff documentation bits.
> On Mon, 2024-11-18 at 16:22 -0500, David Malcolm wrote:
>> Another ping for this patch; any pex experts out there?
>>
>> Thanks!
>> Dave
>>
>> On Wed, 2024-05-29 at 17:06 -0400, David M
On Mon, Nov 25, 2024 at 10:49:02PM -0500, David Malcolm wrote:
> This patch attempts to provide better error messages for
> code compiled with C23 that hasn't been updated for
> "bool", "true", and "false" becoming keywords (based on
> a brief review of the Gentoo bug tracker links given at
> https
Hi Harald,
Looks good to me.
Thanks
Paul
On Tue, 26 Nov 2024 at 19:51, Harald Anlauf wrote:
> Dear all,
>
> the attached patch fixes two minor front-end memleaks I saw when working
> on recent PRs (pr117774 is one of them) and running f951 under valgrind.
>
> Regtested on x86_64-pc-linux-gnu.
The function body test was expecting:
umovw0, v0.b[0]
strbw0, [sp, 15]
But the code generation was improved after r15-5375-gbeec291225be to just:
str b0, [sp, 15]
which is correct and better because no longer need to move between SIMD
registers
and the GPRs.
T
On Tue, Nov 26, 2024 at 04:35:15PM -0500, Marek Polacek wrote:
> Thanks for the patch.
>
> For:
>
> typedef int _Bool;
>
> or
>
> int _Bool;
>
> this patch says:
>
> note: '_Bool' is a keyword with '-std=c23' onwards
>
> but I don't think that's true: _Bool was added in C99 and is obso
* David Malcolm:
> whereas with this patch we emit:
>
> t1.c:7:13: error: 'bool' cannot be defined via 'typedef'
> 7 | typedef int bool;
> | ^~~~
> t1.c:7:13: note: 'bool' is a keyword with '-std=c23' onwards
> t1.c:7:1: warning: useless type name in empty declaration
> 7
Am 26.11.24 um 21:09 schrieb Paul Richard Thomas:
Hi Harald,
Looks good to me.
Thanks
Paul
Thanks, Paul.
Pushed as r15-5701-geff7e72815ada5 .
On Tue, 26 Nov 2024 at 19:51, Harald Anlauf wrote:
Dear all,
the attached patch fixes two minor front-end memleaks I saw when working
on recent
Am 26.11.24 um 23:12 schrieb Harald Anlauf:
Am 26.11.24 um 21:09 schrieb Paul Richard Thomas:
Hi Harald,
Looks good to me.
Thanks
Paul
Thanks, Paul.
Pushed as r15-5701-geff7e72815ada5 .
This should have read r15-5708-g94f98f67f7271f,
the testcase in the other one was used in the testing f
On Mon, 18 Nov 2024, Florian Weimer wrote:
> This is another recent GCC extension whose use is apparently
> difficult to spot in code reviews.
>
> The name of the option is due to Jonathan Wakely. Part of it
> could apply to C++ as well (for labels at the end of a compound
> statement).
>
> gcc
Ping
On Mon, 2024-11-18 at 16:22 -0500, David Malcolm wrote:
> Another ping for this patch; any pex experts out there?
>
> Thanks!
> Dave
>
> On Wed, 2024-05-29 at 17:06 -0400, David Malcolm wrote:
> > On Wed, 2024-05-29 at 16:35 -0400, Eric Gallager wrote:
> > > On Tue, May 28, 2024 at 1:21 PM
Am 25.11.24 um 23:33 schrieb Steve Kargl:
On Mon, Nov 25, 2024 at 10:05:49PM +, Harald Anlauf wrote:
Dear all,
the attached patch fixes an ICE when passing an inquiry reference of a complex
array to an assumed-rank dummy argument by terminating the search for the
array reference before we h
Think this over these days, I have another thought that need some feedback:
The major issue right now is:
1. For the following structure in which the “counted_by” attributes is attached
to the pointer field.
struct foo {
int n;
char *p __attribute__ ((counted_by (n)));
} *x;
There is one i
libstdc++-v3/ChangeLog:
PR libstdc++/117751
* testsuite/18_support/50594.cc: Edit dg-options to include the
-fno-assume-sane-operators-new-delete option.
---
Tested x86_64-linux. Pushed to trunk.
I checked the other tests that replace operator new and operator delete,
but
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
As the manual states, using "-fhardened -fstack-protector" will produce
a warning because -fhardened wants to enable -fstack-protector-strong,
but it can't since it's been overriden by the weaker -fstack-protector.
-fhardened a
Hello,
thanks for bearing with me :)
On Tue, 26 Nov 2024, Jonathan Wakely wrote:
> Being a member function makes no difference, but yes, I'm specifically
> talking about the case of calling a constexpr function.
>
> constexpr int bla() { return 2; }
> int foo (void) {
> const int x = bla();
>
On Tue, Nov 26, 2024 at 06:19:46PM +0100, Heiko Eißfeldt wrote:
> Thanks for your patience!
>
> On 11/26/24 8:36 AM, Jakub Jelinek wrote:
> > This is wrongly formatted and valid only in C++17 and later, while
> > GCC is currently written in C++14.
> > So it needs to be
> > static_assert
This patch adds the TARGET_CREATE_FMV_DISPATCHER_AT_DEFAULT_IMPL flag
which changes FMV behavior for target_version functions to match the Arm
C Language Extension.
The functional differences consist of:
1. Generating the resolver for the dispatched symbol at the site of the
default version de
From: Alfie Richards
Hello,
I have changed this patch to not rely on the C multiversion patch.
I still plan to get that patch up eventually, but I think it requires
some more work and feedback.
This patch now just changes the FMV dispatcher generation for Aarch64
to comply with the ACLE.
If po
Yury Khrustalev writes:
> gcc/ChangeLog:
> * config/aarch64/arm_acle.h (_CHKFEAT_GCS): New.
>
> libgcc/ChangeLog:
>
> * config/aarch64/aarch64-unwind.h (_Unwind_Frames_Extra): Update.
> (_Unwind_Frames_Increment): Update
OK, thanks. (We discussed getting commit access off-list.
Another ping on the Middle-end review of this patch.
This patch has been waiting for the middle-end review for a long time.
Please review it and provide any feedback, I believe that this should be a nice
improvement to GCC diagnostic in general.
Thanks.
Qing
> On Nov 15, 2024, at 10:34, Qi
On Tue, 26 Nov 2024, Jonathan Wakely wrote:
In the bla() example above, the call bla() is a constant expression
when used to initialize a const int, so the compiler is required to
evaluate it at compile time.
When used in contexts that doesn't require an integral constant I think a
distinction
On Tue, 26 Nov 2024 at 18:16, Marc Glisse wrote:
>
> On Tue, 26 Nov 2024, Jonathan Wakely wrote:
>
> >>> In the bla() example above, the call bla() is a constant expression
> >>> when used to initialize a const int, so the compiler is required to
> >>> evaluate it at compile time.
> >>
> >> When u
Hi,
this patch makes genrecog split its output into separate files (10 by
default) in the same vein genemit does. The changes are mostly
mechanical again, changing printfs and puts to fprintf.
As insn-recog.cc relies on being able to call other recog functions a
header insn-recog.h is introduced
Hello,
On Tue, 26 Nov 2024, Jonathan Wakely wrote:
> So the 'const int' doesn't really matter for any -On level, as you
> say, but just avoiding two separate uses of the __deque_buf_size
> function is worthwhile for -std=c++98 -O0
Oh, definitely. Avoiding duplicate calls in C++ sources (no matt
On 2024-11-26 16:33, Christophe Lyon wrote:
On 11/26/24 13:42, Torbjörn SVENSSON wrote:
Hi,
Sorry for the mess. I'm not sure how I managed to miss this...
Maybe I tested the GCC15 binaries on the GCC14 test tree.
Anyway, here is a fix that uses the assembler generated in GCC14.
The csinc
OK for trunk? (caveat: I haven't done a full test on this patch)
gcc/ChangeLog:
PR translation/90160
* config/arm/arm.cc (arm_option_check_internal): Use quotes in
messages that refer to command-line options. Tweak wording.
Signed-off-by: David Malcolm
---
gcc/config/a
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r15-5700-g5134bad11b9a71.
gcc/c/ChangeLog:
PR c/94370
* c-typeck.cc (c_build_functype_attribute_variant): Reword
warning message to avoid double-negative.
gcc/testsuite/ChangeLog:
PR
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r15-5698-g08bb92d642757f.
gcc/ChangeLog:
PR plugins/93746
* plugin.cc (try_init_one_plugin): Add missing colon in error
message.
Signed-off-by: David Malcolm
---
gcc/plugin.cc | 2 +-
1 fil
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r15-5699-g67458ea13895ba.
gcc/ChangeLog:
PR translation/80760
* tree-ssa-loop-prefetch.cc (pass_loop_prefetch::execute): Add
missing colon to not-a-power-of-two param warning.
gcc/testsuite/C
OK for trunk? (caveat: not properly tested)
gcc/ChangeLog:
PR translation/90160
* config/csky/csky.cc (csky_configure_build_target): Use %qs when
referring to cpu and arch names.
(csky_option_override): Likewise.
Signed-off-by: David Malcolm
---
gcc/config/csky/
* Jeff Law:
> On 11/26/24 9:06 AM, David Malcolm wrote:
>> OK for trunk? (caveat: not properly tested)
>> gcc/ChangeLog:
>> PR translation/90160
>> * config/csky/csky.cc (csky_configure_build_target): Use %qs when
>> referring to cpu and arch names.
>> (csky_option_override):
On Tue, 26 Nov 2024 at 14:27, Michael Matz wrote:
>
> Hello,
>
> I don't have anything to add to the threads topic itself, but was
> triggered by something:
>
> On Tue, 26 Nov 2024, Jonathan Wakely wrote:
>
> > > > const size_t __bufsz = __deque_buf_size(sizeof(_Tp));
> > > ...
> > > I wonder wh
On 11/26/24 13:42, Torbjörn SVENSSON wrote:
Hi,
Sorry for the mess. I'm not sure how I managed to miss this...
Maybe I tested the GCC15 binaries on the GCC14 test tree.
Anyway, here is a fix that uses the assembler generated in GCC14.
The csinc instruction was introduced in r15-1579-g792f97b
I'd like to highlight the question around the C++ frontend folding the
code generated by ix86_atomic_assign_expand_fenv that I mentioned in
this cover letter.
(Question being whether it seems reasonable to say this hook should
be updated by the target maintainers or alternatively whether I'm
using
Do you mind creating a PR to
https://github.com/riscv/riscv-elf-psabi-doc/pull/ to start the
discussion? I believe this should be documented somewhere since it
should be consistent between LLVM and GCC.
On Mon, Nov 4, 2024 at 2:26 PM Zhijin Zeng wrote:
>
> I can't find the vector function name ma
Hi,
here is updated patch.
I am not ceratin if:
const size_t __diffmax
= __gnu_cxx::__numeric_traits::__max / sizeof(_CharT);
really needs "/ sizeof (_CharT)". I think we only need to be able to
compute the difference between two entries in multiplies of sizeof(_CharT)?
However
On 11/26/24 9:06 AM, David Malcolm wrote:
OK for trunk? (caveat: not properly tested)
gcc/ChangeLog:
PR translation/90160
* config/csky/csky.cc (csky_configure_build_target): Use %qs when
referring to cpu and arch names.
(csky_option_override): Likewise.
It ma
Thanks for your patience!
On 11/26/24 8:36 AM, Jakub Jelinek wrote:
This is wrongly formatted and valid only in C++17 and later, while
GCC is currently written in C++14.
So it needs to be
static_assert (FIRST_PSEUDO_REGISTER <= INT_MAX, "");
done.
Heikodiff --git a/gcc/varasm.cc
On 11/23/24 2:59 AM, shiyul...@iscas.ac.cn wrote:
From: yulong
This patch modifies the char string from __riscv_xsfvcp to __riscv_xsfcease.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/predef-sf-2.c: Modify the char string.
Thanks. I've pushed this to the trunk.
jeff
On Wed, Nov 27, 2024 at 12:03:23AM -0500, Jason Merrill wrote:
> Tested x86_64-pc-linux-gnu.
>
> Does this approach make sense to you? Any other ideas?
>
> -- 8< --
>
> We weren't representing 'using namespace' at all in modules, which broke
> some of the literals tests.
>
> I experimented wi
On Wed, 2024-11-27 at 14:24 +0800, Lulu Cheng wrote:
>
> 在 2024/11/27 下午12:06, Xi Ruoyao 写道:
> > On Wed, 2024-11-27 at 11:58 +0800, Lulu Cheng wrote:
> > > > > --- /dev/null
> > > > > +++
> > > > > b/gcc/testsuite/gcc.target/loongarch/vector/lasx/lasx-shift-sameimm-vec.c
> > > > > @@ -0,0 +1,72 @
在 2024/11/27 上午10:14, Xi Ruoyao 写道:
On Tue, 2024-11-26 at 18:37 +0800, Jinyang He wrote:
For {xv,v}{srl,sll,sra}, the constraint `vector_same_uimm6` cause overflow
in when emit {w,h,b}. Since the number of bits shifted is the remainder of
the register value, it is actually unnecessary to constr
在 2024/11/27 下午3:10, Xi Ruoyao 写道:
On Wed, 2024-11-27 at 14:24 +0800, Lulu Cheng wrote:
在 2024/11/27 下午12:06, Xi Ruoyao 写道:
On Wed, 2024-11-27 at 11:58 +0800, Lulu Cheng wrote:
--- /dev/null
+++ b/gcc/testsuite/gcc.target/loongarch/vector/lasx/lasx-shift-sameimm-vec.c
@@ -0,0 +1,72 @@
+/* Te
For a double conversion, we will simplify it into a conversion
with an and if the outer type and inside precision matches and
the intra precision is smaller and unsigned. We should be able
to extend this to where the outer precision is larger too.
This is a good canonicalization too.
Bootstrapped
On Thu, Oct 31, 2024 at 1:41 PM Andi Kleen wrote:
>
> From: Andi Kleen
>
> autofdo looks up inline stacks and tries to match them with the profile
> data using their symbol name. Make sure all decls that can be in a inline
> stack
> have a valid assembler name.
>
> This fixes a bootstrap problem
On Tue, Nov 26, 2024 at 04:06:37PM -0800, Andrew Pinski wrote:
> On Thu, Oct 31, 2024 at 1:41 PM Andi Kleen wrote:
> >
> > From: Andi Kleen
> >
> > autofdo looks up inline stacks and tries to match them with the profile
> > data using their symbol name. Make sure all decls that can be in a inline
在 2024/11/27 上午10:14, Xi Ruoyao 写道:
On Tue, 2024-11-26 at 18:37 +0800, Jinyang He wrote:
For {xv,v}{srl,sll,sra}, the constraint `vector_same_uimm6` cause overflow
in when emit {w,h,b}. Since the number of bits shifted is the remainder of
the register value, it is actually unnecessary to const
When loop requires any kind of versioning which could increase register
pressure too much, and it's in a deeply nest big loop, don't do
vectorization.
I tested the patch with both Ofast and O2 for SPEC2017, besides 548.exchange_r,
other benchmarks are same binary.
Bootstrapped and regtested 0on x
On Wed, 2024-11-27 at 11:58 +0800, Lulu Cheng wrote:
> > > --- /dev/null
> > > +++
> > > b/gcc/testsuite/gcc.target/loongarch/vector/lasx/lasx-shift-sameimm-vec.c
> > > @@ -0,0 +1,72 @@
> > > +/* Test shift bits overflow in vector */
> > > +/* { dg-do compile } */
> > > +/* { dg-options "-mlasx -O
Tested x86_64-pc-linux-gnu.
Does this approach make sense to you? Any other ideas?
-- 8< --
We weren't representing 'using namespace' at all in modules, which broke
some of the literals tests.
I experimented with various approaches to representing them, and ended up
with emitting them as a ps
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
I enabled include translation to header units in r15-1104-ga29f481bbcaf2b,
but it seems that patch wasn't sufficient, as any diagnostics in the main
source file would show up as coming from the header instead.
Fixed by setting buffer->file
Tested x86_64-pc-linux-gnu, applying to trunk.
Marek, I hope this change doesn't interfere with your work on P2865R5.
-- 8< --
P2865R5 pointed out that we only enabled this warning with -Wall; we should
handle it like other deprecations.
gcc/c-family/ChangeLog:
* c-opts.cc (c_common_po
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
Here we weren't emitting the guard variable for 'a' when we emitted 'afn'
in the importer, because we only treated inline variables as needing that.
Fixed by generalizing to vague_linkage_p.
But we need to specifically exempt vtables, beca
This patch modifies the intrinsic expanders to expand svlsl and svlsr to
unpredicated forms when the predicate is a ptrue. It also folds the
following pattern:
lsl , ,
lsr , ,
orr , ,
to:
revb/h/w ,
when the shift amount is equal to half the bitwidth of the
register.
This relies
Tested x86_64-pc-linux-gnu, OK for trunk?
-- 8< --
Some tests were failing due to the exported using declaration of iter_move
conflicting with friend declarations; the exported using needs to be in the
inline namespace, like the customization point itself, rather than
std::ranges.
Also add a few
On Mon, 25 Nov 2024, Martin Uecker wrote:
>
> Hi Richard,
>
> here is another version. This now just ignores the size for all trailing
> arrays which I think is the right thing to do. It also modifies the lto
> hashing which also seems to work (but needs more testing and I haven't
> added test
From: Pan Li
Some forms like below failed to recog the SAT_ADD pattern
for target i386. It is related to some match pattern
extraction but get fixed after the refactor of the SAT_ADD
pattern. Thus, add testcases to ensure we may have similar
issue in futrue.
#define DEF_SAT_ADD(T) \
T sa
On Tue, 2024-11-26 at 18:37 +0800, Jinyang He wrote:
> For {xv,v}{srl,sll,sra}, the constraint `vector_same_uimm6` cause overflow
> in when emit {w,h,b}. Since the number of bits shifted is the remainder of
> the register value, it is actually unnecessary to constrain the range.
> Simply mask the s
在 2024/11/27 下午12:06, Xi Ruoyao 写道:
On Wed, 2024-11-27 at 11:58 +0800, Lulu Cheng wrote:
--- /dev/null
+++ b/gcc/testsuite/gcc.target/loongarch/vector/lasx/lasx-shift-sameimm-vec.c
@@ -0,0 +1,72 @@
+/* Test shift bits overflow in vector */
+/* { dg-do compile } */
+/* { dg-options "-mlasx -O2"
Hi!
__builtin_is{inf,finite,normal} builtins ICE on _Decimal{32,64,128,64x}
operands unless those operands are constant.
The problem is that we fold the builtins to comparisons with the largest
finite number, but
a) get_max_float was only handling binary floats
b) real_from_string again assumes b
Hi!
This patch is similar to the one I've just posted, __builtin_fpclassify also
needs to print decimal float minimum differently and use real_from_string3.
Plus I've done some formatting fixes.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2024-11-26 Jakub Jelinek
In r15-5327, change the default language version for C compilation from
-std=gnu17 to -std=gnu23.
ISO C99 and C11 allow ceil, floor, round and trunc, and their float and
long double variants, to raise the “inexact” exception,
but ISO/IEC TS 18661-1:2014, the C bindings to IEEE 754-2008, as
integra
Add '-fdump-tree-optimized' to this testcases.
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/lasx-andn-iorn.c:
Add '-fdump-tree-optimized'.
* gcc.target/loongarch/lsx-andn-iorn.c:
Likewise.
---
gcc/testsuite/gcc.target/loongarch/lasx-andn-iorn.c | 2 +-
gcc/test
On Mon, Nov 25, 2024 at 03:40:18PM -0500, Marek Polacek wrote:
> Just "omitting a comma", I think.
>
> "of a function parameter list"
>
> I suppose we should also test -Wno-deprecated and/or
> -Wno-deprecated-variadic-comma-omission in C++26.
Thanks, I've made those changes including adding more
On Tue, Nov 26, 2024 at 1:59 AM Andrew MacLeod wrote:
>
> A lot of time was being spent processing inferred ranges during a cache
> update. Requesting the range of an argument during processing of
> inferred ranges was suppose to be cheap because they have already been
> calculated during folding
On Tue, Nov 26, 2024 at 2:00 AM Andrew MacLeod wrote:
>
> This patch is also going to be needed by Jakub for his non-null work, I
> just foudn another use for it.
>
> hiis patch adds a range-query to the instantiation of an inferred range
> manager so that inferred range processing can make a rang
This might fix the current bootstrap failure on aarch64, I only tested it
on x86_64. But the rem variable is unused and the for poly_widest_int, there
could be loop if NUM_POLY_INT_COEFFS is 2 or more. In the case of aarch64,
NUM_POLY_INT_COEFFS is 2.
Note the reason why there is warning for the un
On Tue, Nov 26, 2024 at 2:00 AM Andrew MacLeod wrote:
>
> Once an inferred range such as non-null has been registered, its a waste
> of time to register and apply them over and over. Pointers that are
> frequently used often are registered in each basic block as non-null.
> This patch prevents the
Hi!
The following patch implements the with_*_nonzero_bits* cleanups and
improvements I was talking about.
get_nonzero_bits is extended to also handle BIT_AND_EXPR (as a tree or
as SSA_NAME with BIT_AND_EXPR def_stmt), new function is added for the
bits known to be set (get_known_nonzero_bits) an
> On 20 Nov 2024, at 13:43, Richard Sandiford wrote:
>
> External email: Use caution opening links or attachments
>
>
> Jennifer Schmitz writes:
>>> On 13 Nov 2024, at 12:54, Richard Sandiford
>>> wrote:
>>>
>>> External email: Use caution opening links or attachments
>>>
>>>
>>> Jennif
Use Markdown backticks to format comments, instead of Doxygen @c and @a
commands.
libstdc++-v3/ChangeLog:
* include/bits/forward_list.h: Use Markdown in Doxygen comments.
---
Tested x86_64-linux. Pushed to trunk.
libstdc++-v3/include/bits/forward_list.h | 123 ---
1
On Mon, Nov 25, 2024 at 09:57:16AM +0100, Richard Biener wrote:
> On Sun, Nov 24, 2024 at 7:22 PM Hans-Peter Nilsson wrote:
> >
> > On Sat, 16 Nov 2024, Lewis Hyatt wrote:
> > > The size of struct gimple increases by 8 bytes with the change in size of
> > > location_t from 32- to 64-bit
> >
> > Ha
On Tue, 26 Nov 2024, Jakub Jelinek wrote:
> Hi!
>
> This patch is similar to the one I've just posted, __builtin_fpclassify also
> needs to print decimal float minimum differently and use real_from_string3.
> Plus I've done some formatting fixes.
>
> Bootstrapped/regtested on x86_64-linux and i6
On Tue, 26 Nov 2024, Jakub Jelinek wrote:
> Hi!
>
> __builtin_is{inf,finite,normal} builtins ICE on _Decimal{32,64,128,64x}
> operands unless those operands are constant.
>
> The problem is that we fold the builtins to comparisons with the largest
> finite number, but
> a) get_max_float was only
Hi!
The following patch adds the new papers. I've also filed PRs for them,
except for the consistent grammar paper which I believe is trivially
implemented by all GCC versions.
Committed to wwwdocs.
diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index 48cd8a36..2
From: Viljar Indus
Raise_Exception_On_Error is never modified so it can be removed.
gcc/ada/ChangeLog:
* err_vars.ads: Remove Raise_Exception_On_Error and
Error_Msg_Exception.
* errout.ads: Same as above.
* errout.adb: Remove uses of Raise_Exception_On_Error and
From: Viljar Indus
gcc/ada/ChangeLog:
* errout.adb: Use Output_Msg_Location
* erroutc.adb: add common implementation for printing the
error message line.
* erroutc.ads: Add new method Output_Msg_Location
* errutil.adb: use Output_Msg_Location
Tested on x8
From: Viljar Indus
Move common code between errout and errutil into a single function.
gcc/ada/ChangeLog:
* errout.adb: Use Is_Redundant_Error_Message.
* erroutc.adb: Move the common code for checking if a message
can be removed to Is_Redundant_Error_Message.
* e
From: Eric Botcazou
The RM B.1(24) sub-clause says that imported entities cannot be initialized
and it is checked in three contexts, aspect Import, pragma Import and pragma
Import_Object, with slightly different error messages. Moreover, for the
aspect, the error is given twice because that of t
From: Viljar Indus
This variable was used for Opt.Include_Subprogram_In_Messages
activated by -gnatdJ. This switch has been removed so this variable
is no longer used.
gcc/ada/ChangeLog:
* errout.ads: Remove Current_Node.
* errout.adb: Remove uses of Current_Node.
* par-
From: Eric Botcazou
The tag is not assigned when a compile-time known aggregate initializes an
object declared with an address clause/aspect.
gcc/ada/ChangeLog:
* freeze.adb: Remove clauses for Exp_Ch3.
(Check_Address_Clause): Always reassign the tag for an object of a
t
From: Viljar Indus
The implementation was duplicated in errout and errutil. Move
the implementation to erroutc where other similar commonly used
functions are.
gcc/ada/ChangeLog:
* errout.adb: Remove implemntation of Set_Msg_Insertion_Column.
* erroutc.adb: Add implementation of
From: Viljar Indus
Simplify the storage for the kind of error message under a single
enumerator. This replaces the existing attributes with the following
enumeration values.
* Is_Warning_Msg => Warning
* Is_Style_Msg => Style
* Is_Info_Msg => Info
* Is_Check_Msg => Low_Check, Medium_Check, High_C
For {xv,v}{srl,sll,sra}, the constraint `vector_same_uimm6` cause overflow
in when emit {w,h,b}. Since the number of bits shifted is the remainder of
the register value, it is actually unnecessary to constrain the range.
Simply mask the shift number with the unit-bit-width, without any
constraint o
From: Ronan Desplanques
The old specifications were ambiguous as to whether they expected
actuals to have %s/%b suffixes. The new specifications also increases
modularity across the board.
gcc/ada/ChangeLog:
* uname.ads (Is_Internal_Unit_Name, Is_Predefined_Unit_Name): Change
sp
From: Viljar Indus
gcc/ada/ChangeLog:
* diagnostics-converter.adb: Remove uses of Info_Warning type. Use
common constructors to simplify implementation.
* diagnostics-pretty_emitter.adb: Remove Info_Warning type.
* diagnostics-utils.adb: Remove uses of Info_Warnin
From: Ronan Desplanques
Before this patch, the body of Fname.UF.Get_File_Name did a lot of
juggling with the global name buffer, which made it hard to understand.
This patch makes the body use local buffers instead.
gcc/ada/ChangeLog:
* fname-uf.adb (Get_File_Name): Use local name buffe
From: Jose Ruiz
gcc/ada/ChangeLog:
* doc/gnat_ugn/the_gnat_compilation_model.rst: The format of
the ali file is documented in lib-writ.ads.
* gnat_ugn.texi: Regenerate.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/doc/gnat_ugn/the_gnat_compilation_mo
1 - 100 of 121 matches
Mail list logo
