(The following sample is taken from my LKML post at
https://lkml.org/lkml/2023/11/15/213)
$ cat t-build-bug.c
struct vring_tx_mac {
unsigned int d[3];
unsigned int ucode_cmd;
} __attribute__((packed));
struct vring_rx_mac {
unsigned int d0;
unsigned int d1;
Hi all, hi David,
I am trying to use the analyzer API to transform an element_region (such
as 't[1]') to a binop_svalue with an inner region_svalue (such as ' +
4' in case of integers array) for analysis purpose.
I managed to do it the other way around (i.e. from a binop_svalue to an
Hi,
On Wed, Nov 15 2023, Mark Wielaard wrote:
> Hi! (adding gdb and binutils to the CC)
>
> On Thu, Nov 09, 2023 at 12:30:59AM +0100, Mark Wielaard wrote:
>> On Mon, Nov 06, 2023 at 06:04:48PM +0100, Martin Jambor wrote:
>> > I have inherited Martin Liška's buildbot script that checks that all
>>
Hi all,
This is the beginning of a patch to introduce the extended attribute
for asm declarations proposed in
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636563.html. I
will need some reviewer help in implementing this patch, as I am not
very familiar with gcc's internals.
The
Snapshot gcc-11-20231116 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20231116/
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112563
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112563
Bug ID: 112563
Summary: [14 regression] libsanitizer doesn't assemble with
Solaris/sparc as
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112562
--- Comment #1 from Jakub Jelinek ---
find -type f | xargs grep %function
./interception/interception.h: ".type "
SANITIZER_STRINGIFY(TRAMPOLINE(func)) ", %function\n" \
./builtins/assembly.h:#define SYMBOL_IS_FUNC(name) .type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100903
Marc Mutz changed:
What|Removed |Added
CC||marc.mutz at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #46 from Robin Dapp ---
(In reply to Jakub Jelinek from comment #43)
> Now, the patch changed it to allow one extra use in certain cases (but I
> think only on use_stmt, because there should be one use on use_stmt and if
> there is
On 15/11/2023 17:08, Tamar Christina wrote:
Hi All,
At the moment we emit a warning whenever you specify both -march and -mcpu
and the architecture of them differ. The idea originally was that the user may
not be aware of this change.
However this has a few problems:
1. Architecture
Tamar Christina writes:
> Hi All,
>
> In testcases gcc.dg/tree-ssa/slsr-19.c and gcc.dg/tree-ssa/slsr-20.c we have
> a
> fairly simple computation. On the current generic costing we generate:
>
> f:
> add w0, w0, 2
> maddw1, w0, w1, w1
> lsl w0, w1, 1
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112564
Bug ID: 112564
Summary: std::format(std::thread::id) is incorrectly
left-aligned
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
On Wed, 15 Nov 2023, Tamar Christina wrote:
> > -Original Message-
> > From: Richard Biener
> > Sent: Wednesday, November 15, 2023 1:23 PM
> > To: Tamar Christina
> > Cc: gcc-patches@gcc.gnu.org; nd ; j...@ventanamicro.com
> > Subject: RE: [PATCH 7/21]middle-end: update IV update code
On Thu, Nov 16, 2023 at 11:58:42AM +0100, Thomas Schwinge wrote:
> > -main ()
> > +void
> > +main (int)
> > {
> >struct tiny x[3];
> >x[0].c = 10;
>
> The nvptx back end doesn't like that one:
>
> PASS: gcc.c-torture/execute/931004-13.c -O0 (test for excess errors)
>
* Thomas Schwinge:
> Hi Florian!
>
> Thanks for all your ongoing clean-up work!
>
> On 2023-11-10T23:07:55+0100, Florian Weimer wrote:
>> This change updates the gcc.c-torture/execute/ to avoid obsolete
>> language constructs. In the changed tests, use of the features
>> appears to be
Pinging back to the top of reviewers' inboxes due to worry about Stage 1
End in a few days :)
See the last email for the latest version of the 2/2 patch. The 1/2
patch is A-Ok from Kyrill's earlier target-backend review.
On 10/11/2023 12:41, Stamatis Markianos-Wright wrote:
On 06/11/2023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112478
--- Comment #9 from CVS Commits ---
The master branch has been updated by Kito Cheng :
https://gcc.gnu.org/g:defa8681d951c6d6c43c71e3636ce4db9de04a28
commit r14-5526-gdefa8681d951c6d6c43c71e3636ce4db9de04a28
Author: Kito Cheng
Date: Tue
Committed, thanks for the review and test :)
On Thu, Nov 16, 2023 at 7:19 AM Christoph Müllner
wrote:
>
> On Tue, Nov 14, 2023 at 3:15 PM Kito Cheng wrote:
> >
> > We set ra to fixed register now, but we still need to save/restore that at
> > prologue/epilogue if that has used.
>
> So before
* Jakub Jelinek:
> So, I guess void main (int) could be ok in some implementations, but I don't
> think that is the case of our. Florian, didn't you mean
> int
> main (void)
> or
> int
> main ()
> instead?
Exactly, it was a silly mistake.
> Note, I'm using
> int
> main ()
> {
> ...
> }
> in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112562
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112562
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #1 from Jakub Jelinek ---
> find -type f | xargs grep %function
> ./interception/interception.h: ".type "
> SANITIZER_STRINGIFY(TRAMPOLINE(func)) ", %function\n"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112532
--- Comment #6 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:e36d5f424a0dcb984620a172c73da989f215dc42
commit r14-5525-ge36d5f424a0dcb984620a172c73da989f215dc42
Author: liuhongt
Date: Wed Nov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112532
liuhongt at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
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 misoptimizations:
after we fold _mm{,256}_blendv_epi8/pd/ps into gimple, the backend
On Tue, Nov 7, 2023 at 10:53 AM Richard Biener wrote:
>
> On Mon, 6 Nov 2023, Tamar Christina wrote:
>
> > Hi All,
> >
> > This adds new test to check for all the early break functionality.
> > It includes a number of codegen and runtime tests checking the values at
> > different needles in the
On Thu, 2023-11-16 at 09:18 +0800, chenglulu wrote:
>
> 在 2023/11/15 下午7:38, Xi Ruoyao 写道:
> > Pushed r14-5486.
> >
> > /* snip */
> >
> > > > * gcc.target/loongarch/cas-acquire.c: New test.
> > This test fails with GCC 12/13 on LA664, and it indicates a
> > correctness
> > issue. May
Hi Florian!
Thanks for all your ongoing clean-up work!
On 2023-11-10T23:07:55+0100, Florian Weimer wrote:
> This change updates the gcc.c-torture/execute/ to avoid obsolete
> language constructs. In the changed tests, use of the features
> appears to be accidental, and updating allows the
> -Original Message-
> From: Richard Biener
> Sent: Thursday, November 16, 2023 10:40 AM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; j...@ventanamicro.com
> Subject: RE: [PATCH 7/21]middle-end: update IV update code to support early
> breaks and arbitrary exits
>
> On Wed,
On Wed, 15 Nov 2023, Tamar Christina wrote:
>
>
> > -Original Message-
> > From: Richard Biener
> > Sent: Wednesday, November 15, 2023 1:42 PM
> > To: Tamar Christina
> > Cc: gcc-patches@gcc.gnu.org; nd ; j...@ventanamicro.com
> > Subject: RE: [PATCH 8/21]middle-end: update
On Thu, 16 Nov 2023, Tamar Christina wrote:
> > -Original Message-
> > From: Richard Biener
> > Sent: Thursday, November 16, 2023 10:40 AM
> > To: Tamar Christina
> > Cc: gcc-patches@gcc.gnu.org; nd ; j...@ventanamicro.com
> > Subject: RE: [PATCH 7/21]middle-end: update IV update code
Committed with changelog update :P Thanks for the review.
On Thu, Nov 16, 2023 at 7:59 AM Christoph Müllner
wrote:
>
> On Tue, Nov 14, 2023 at 3:15 PM Kito Cheng wrote:
> >
> > The target attribute which proposed in [1], target attribute allow user
> > to specify a local setting per-function
libsanitizer/ChangeLog:
* configure.tgt: allow loongarch64-linux-*.
---
libsanitizer/configure.tgt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libsanitizer/configure.tgt b/libsanitizer/configure.tgt
index d24566a2343..5af524cb271 100644
---
Tested x86_64-linux. Pushed to trunk.
-- >8 --
This change moves the definitions of feature test macros (or strictly
speaking, the requests for to define them) so that only
standard headers define them. For example, will no
longer define macros related to std::shared_ptr, only and
will
On Thu, Nov 16, 2023 at 04:01:13PM +0800, Yang Yujie wrote:
> libsanitizer/ChangeLog:
>
> * configure.tgt: allow loongarch64-linux-*.
${target} in there shouldn't be what user specified, but what config.sub
canonicalized it to.
And
./config.sub x86_64-linux; ./config.sub loongarch64-linux
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Tests which check for feature test macros should use the no_pch option,
so that we're really testing for the definition being in the intended
header, and not just testing that it's present in (which
includes all the standard headers and so defines
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111667
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:c7f6537db94f7c6320a5a8ecaa387c9b9ce1f0ac
commit r14-5524-gc7f6537db94f7c6320a5a8ecaa387c9b9ce1f0ac
Author: Jonathan Wakely
Based on SPEC2017 performance evaluation results, it's better to make them equal
to the cost of unaligned store/load so as to avoid odd alignment peeling.
gcc/ChangeLog:
* config/loongarch/loongarch.cc
(loongarch_builtin_vectorization_cost): Adjust.
diff --git
On 16/11/2023 06:15, Philipp Tomsich wrote:
With the addition of CSSC (Common Short Sequence Compression)
instructions, a number of idioms match to single instructions (e.g.,
abs) that previously expanded to multi-instruction sequences.
This recognizes (some of) those idioms that are now
> -Original Message-
> From: Richard Earnshaw
> Sent: Thursday, November 16, 2023 8:53 AM
> To: Philipp Tomsich ; gcc-patches@gcc.gnu.org
> Cc: Kyrylo Tkachov
> Subject: Re: [PATCH] aarch64: costs: update for TARGET_CSSC
>
>
>
> On 16/11/2023 06:15, Philipp Tomsich wrote:
> > With
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #37 from Jakub Jelinek ---
(In reply to Robin Dapp from comment #35)
> What does get rid of the comparison failures in the three last posted
> reduced examples is:
>
> gcall *call = dyn_cast (op_use_stmt);
>
On 15/11/2023 17:08, Tamar Christina wrote:
Hi All,
This patch adds a new generic scheduling model "generic-armv9-a" and makes it
the default for all Armv9 architectures.
-mcpu=generic and -mtune=generic is kept around for those that really want the
deprecated cost model.
Bootstrapped
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112547
--- Comment #5 from Filip Kastl ---
Compile options are:
-O2 -g -flto=128
Configure options of GCC are:
--enable-languages=c,c++,fortran,rust,m2 --disable-bootstrap
--disable-libsanitizer --disable-multilib --enable-checking=release
Hello Richard:
This patch does decision making in code sinking considers the following
decision.
High register pressure region is true if the following criteria
satisfied.
a) If liveout (early_bb) <= livein (early_bb).
b) if liveout (best_bb) <= liveout (early_bb).
c) !best_bb->count >=
> -Original Message-
> From: Richard Earnshaw
> Sent: Thursday, November 16, 2023 9:27 AM
> To: Tamar Christina ; gcc-patches@gcc.gnu.org
> Cc: nd ; Richard Earnshaw ;
> Marcus Shawcroft ; Kyrylo Tkachov
> ; Richard Sandiford
>
> Subject: Re: [PATCH 6/6]AArch64: only emit mismatch error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #41 from Richard Biener ---
(In reply to Jakub Jelinek from comment #39)
> Created attachment 56601 [details]
> gcc14-pr112374.patch
>
> So the following then?
LGTM. Refactoring to more explicitly handle debug stmts like with
> -Original Message-
> From: Richard Earnshaw
> Sent: Thursday, November 16, 2023 9:42 AM
> To: Tamar Christina ; gcc-patches@gcc.gnu.org
> Cc: nd ; Richard Earnshaw ;
> Marcus Shawcroft ; Kyrylo Tkachov
> ; Richard Sandiford
>
> Subject: Re: [PATCH 6/6]AArch64: only emit mismatch error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #43 from Jakub Jelinek ---
(In reply to Robin Dapp from comment #40)
> (In reply to Jakub Jelinek from comment #37)
> [..]
>
> > The above isn't complete, so one just has to guess what you mean outside of
> > that, but the above
Tested x86_64-linux. Pushed to trunk.
-- >8 --
We don't need any library concepts to define the constraints for rvalue
stream overloads, only compiler support. So change the test from using
__cpp_lib_concepts to __cpp_concepts >= 201907L.
libstdc++-v3/ChangeLog:
* include/std/istream
Tested x86_64-linux. Pushed to trunk.
-- >8 --
I noticed that our C++23 features were not being defined when using
Clang 16 with -std=c++2b, because it only defines __cplusplus=202101L
but uses 202302L since my r14-3252-g0c316669b092fb
change.
This changes to use 202100 instead of the final
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112325
liuhongt at gcc dot gnu.org changed:
What|Removed |Added
CC||liuhongt at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112561
Bug ID: 112561
Summary: [14 Regression] Segfault only on RISC-V vector
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Tested x86_64-linux. Pushe to trunk.
-- >8 --
This implements that changes from P1132R8, including optimized paths for
std::shared_ptr and std::unique_ptr.
For std::shared_ptr we pre-allocate a new control block in the
std::out_ptr_t constructor so that the destructor is non-throwing. This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111667
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106749
Bug 106749 depends on bug 111667, which changed state.
Bug 111667 Summary: [C++23] Implement P1132R8, out_ptr - a scalable output
pointer abstraction
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111667
What|Removed
Thanks for the quick turnaround on the review.
I'll send a v2 after the mcpu=ampere1b change has landed, as the
extra-costs change will have an interaction with that change (due to
the extra fields in the structure).
Philipp.
On Thu, 16 Nov 2023 at 15:12, Kyrylo Tkachov wrote:
>
>
>
> >
On 15/11/2023 17:08, Tamar Christina wrote:
Hi All,
At the moment we emit a warning whenever you specify both -march and -mcpu
and the architecture of them differ. The idea originally was that the user may
not be aware of this change.
However this has a few problems:
1. Architecture
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #44 from Jakub Jelinek ---
(In reply to Andrew Pinski from comment #42)
> Just one suggestion for the testcases, add:
> /* { dg-additional-options "-march=armv9-a" { target aarch64*-*-* } } */
>
> So it at least it will be tested
On Mon, Oct 30, 2023 at 1:10 PM Ajit Agarwal wrote:
>
> Hello Richard:
>
> Currently, code sinking will sink code at the use points with loop having same
> nesting depth. The following patch improves code sinking by placing the sunk
> code in immediate dominator with same loop nest depth.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112561
JuzheZhong changed:
What|Removed |Added
CC||juzhe.zhong at rivai dot ai
--- Comment
On 16/11/2023 09:33, Tamar Christina wrote:
-Original Message-
From: Richard Earnshaw
Sent: Thursday, November 16, 2023 9:27 AM
To: Tamar Christina ; gcc-patches@gcc.gnu.org
Cc: nd ; Richard Earnshaw ;
Marcus Shawcroft ; Kyrylo Tkachov
; Richard Sandiford
Subject: Re: [PATCH
This is a temporary solution to
https://forum.dlang.org/thread/bug-1226...@https.d.puremagic.com%2Fissues%2F
libphobos/ChangeLog:
* libdruntime/gcc/sections/elf.d: Removes reference to __tls_get_addr
for
static libdruntime.
---
libphobos/libdruntime/gcc/sections/elf.d | 4 +++-
> ${target} in there shouldn't be what user specified, but what config.sub
> canonicalized it to.
> And
> ./config.sub x86_64-linux; ./config.sub loongarch64-linux
> x86_64-pc-linux-gnu
> loongarch64-unknown-linux-gnu
> so I really don't see why you want to change it.
OK, I see. Thanks.
Yujie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112325
--- Comment #4 from liuhongt at gcc dot gnu.org ---
(In reply to liuhongt from comment #3)
> BB vectorizer relies on the backend support of .REDUC_PLUS for reduction,
> but loop vectorizer can manually do reduction. That's why it's not
>
Based on SPEC2017 performance evaluation results, it's better to make them equal
to the cost of unaligned store/load so as to avoid odd alignment peeling.
gcc/ChangeLog:
* config/loongarch/loongarch.cc
(loongarch_builtin_vectorization_cost): Adjust.
diff --git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #34 from Robin Dapp ---
(In reply to Jakub Jelinek from comment #29)
> --- gcc/tree-vect-loop.cc.jj 2023-11-14 10:35:52.0 +0100
> +++ gcc/tree-vect-loop.cc 2023-11-15 22:42:32.782007408 +0100
> @@ -4105,9 +4105,9 @@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #35 from Robin Dapp ---
What does get rid of the comparison failures in the three last posted reduced
examples is:
gcall *call = dyn_cast (op_use_stmt);
internal_fn ifn;
if (call &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #36 from Jakub Jelinek ---
Actually, while i386-expand.o compilation fails with -fcompare-debug even after
the above patch, seems that is only because of the discriminator issue, the
*.gkd difference is then:
--- i386-expand.cc.gkd
On 15/11/2023 17:07, Tamar Christina wrote:
Hi All,
In anticipation of adding new generic turning values this removes the hardcoding
of the "generic" CPU and instead just specifies it as a normal CPU.
No change in behavior is expected.
Bootstrapped Regtested on aarch64-none-linux-gnu and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112325
--- Comment #5 from Richard Biener ---
Yes, as I said in comment#2. Note I specifically ended up not open-coding the
reduction because of concerns of efficiency. So a target should only provide
reduc_*_scal patterns when they are more
On 15/11/2023 17:07, Tamar Christina wrote:
Hi All,
This patch adds a new generic scheduling model "generic-armv8-a" and makes it
the default for all Armv8 architectures.
-mcpu=generic and -mtune=generic is kept around for those that really want the
deprecated cost model.
Rather than
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #38 from Jakub Jelinek ---
And the #c29 change actually seems to fix all the testcases here with
-fcompare-debug -gno-statement-frontiers:
$ ~/src/gcc/obj48/gcc/xg++ -B ~/src/gcc/obj48/gcc/ -fcompare-debug
-gno-statement-frontiers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #40 from Robin Dapp ---
(In reply to Jakub Jelinek from comment #37)
[..]
> The above isn't complete, so one just has to guess what you mean outside of
> that, but the above doesn't seem to be correct. There are many internal
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #42 from Andrew Pinski ---
Just one suggestion for the testcases, add:
/* { dg-additional-options "-march=armv9-a" { target aarch64*-*-* } } */
So it at least it will be tested on another target.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #45 from Andrew Pinski ---
(In reply to Jakub Jelinek from comment #44)
> (In reply to Andrew Pinski from comment #42)
> > Just one suggestion for the testcases, add:
> > /* { dg-additional-options "-march=armv9-a" { target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112562
Bug ID: 112562
Summary: [14 regression] asan_interceptors_memintrinsics.cpp
doesn't assemble with Solaris/x86 as
Product: gcc
Version: 14.0
Status: UNCONFIRMED
With -mdiv32, we can assume div.w[u] and mod.w[u] works on low 32 bits
of a 64-bit GPR even if it's not sign-extended.
gcc/ChangeLog:
* config/loongarch/loongarch.md (DIV): New mode iterator.
(3): Don't expand if TARGET_DIV32.
(di3_fake): Disable if TARGET_DIV32.
Loongson 3A6000 processor will be shipped to general users in this month
and it features 4 cores with the new LA664 micro architecture. Here is
some changes from LA464:
1. The 32-bit division instruction now ignores the high 32 bits of the
input registers. This is enumerated via CPUCFG word
We'll use HOST_WIDE_INT in LoongArch static properties in following
patches. Switch loongarch-def from C to C++ to make it possible.
To keep the same readability as C99 designated initializers, create a
std::array like data structure with position setter function, and add
field setter functions
Allow using -march=la664 and -mtune=la664. -march=la664 implies -mdiv32
and -mld-seq-sa. -mtune=la664 is currently same as -mtune=la464 and it
may need an update later.
gcc/ChangeLog:
* config/loongarch/genopts/loongarch-strings: Add la664 as
STR_CPU_LA664.
*
This option (CPUCFG word 0x3 bit 23) means "the hardware guarantee that
two loads on the same address won't be reordered with each other". Thus
we can omit the "load-load" barrier dbar 0x700.
This is only a micro-optimization because dbar 0x700 is already treated
as nop if the hardware supports
LoongArch v1.10 introduced the concept of ISA evolution. During ISA
evolution, many independent features can be added and enumerated via
CPUCFG.
Add a data file into genopts storing the CPUCFG word, bit, the name
of the command line option controlling if this feature should be used
for
> > > > > >
> > > > > > Perhaps I'm missing something here?
> > > > >
> > > > > OK, so I refreshed my mind of what
> > > > > vect_update_ivs_after_vectorizer
> > > does.
> > > > >
> > > > > I still do not understand the (complexity of the) patch.
> > > > > Basically the function computes the new
On Thu, 16 Nov 2023, Tamar Christina wrote:
> > > > > > >
> > > > > > > Perhaps I'm missing something here?
> > > > > >
> > > > > > OK, so I refreshed my mind of what
> > > > > > vect_update_ivs_after_vectorizer
> > > > does.
> > > > > >
> > > > > > I still do not understand the (complexity of
No functional change intended.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r14-5530-g4547c271c455dc.
gcc/ChangeLog:
* diagnostic.cc (diagnostic_context::set_option_hooks): Add
"lang_mask" param.
* diagnostic.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
--- Comment #42 from Costas Argyris ---
Looks like what is being requested here is a windows-host-specific
configuration option similar to the existing --disable-win32-registry, like for
example --disable-win32-utf8-manifest with its
From: Thomas Rodgers
These two patches were written by Tom earlier this year, before he left
Red Hat. We should finish reviewing them for GCC 14 (and probably squash
them into one?)
Tom, you mentioned further work that changes the __platform_wait_t* to
uintptr_t, is that ready, or likely to be
From: Thomas Rodgers
Tested x86_64-linux, testing underway on powerpc-aix and sparc-solaris.
-- >8 --
This change splits the __wait_args data members to a new struct
__wait_args_base and then passes that type by const pointer to the low
level implementation functions.
libstdc++-v3/ChangeLog:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70
--- Comment #7 from Costas Argyris ---
Some ideas on how this could be implemented in case someone wants to try and
fix this sooner than me:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865#c42
gcc/testsuite/
* gcc.c-torture/execute/931004-13.c (main): Fix mistakenly swapped
int/void types.
---
gcc/testsuite/gcc.c-torture/execute/931004-13.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/testsuite/gcc.c-torture/execute/931004-13.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112567
David Binderman changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #4
)
=
When using the 'stepi' command in GDB, an abnormal jump in the execution occurs
when reaching line 7 of the code. The execution unexpectedly jumps to line 13.
$ gcc --version
gcc (GCC) 14.0.0 20231116 (experimental)
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112565
--- Comment #2 from Anonymous ---
(In reply to Tom de Vries from comment #1)
> (In reply to Anonymous from comment #0)
> > Tom de Vries suggests that this issue may be attributed to a GCC
> > optimization bug.
>
> I do not.
Thanks for the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111878
Tamar Christina changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112566
Bug ID: 112566
Summary: Some ctz/popcount/parity/ffs optimizations
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Thu, 16 Nov 2023, Tamar Christina wrote:
> > -Original Message-
> > From: Richard Biener
> > Sent: Thursday, November 16, 2023 11:28 AM
> > To: Tamar Christina
> > Cc: gcc-patches@gcc.gnu.org; nd ; j...@ventanamicro.com
> > Subject: RE: [PATCH 7/21]middle-end: update IV update code
Okay, thank you for your suggestion.
在 2023/11/16 下午8:11, Xi Ruoyao 写道:
The change should be OK, I've seen these test failures for a while. But
it would be better to provide some explanations in the commit message
(does these test fails since they were added first day or something has
changed
These tests fail when they are first added,this patch adjusts the
scan-assembler-times
to fix them.
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/vector/lasx/lasx-vcond-1.c: Adjust assembler
times.
* gcc.target/loongarch/vector/lasx/lasx-vcond-2.c: Ditto.
*
1 - 100 of 362 matches
Mail list logo
