https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61
--- Comment #2 from Zdenek Sojka ---
(In reply to xu...@eswincomputing.com from comment #1)
> backport
> https://github.com/gcc-mirror/gcc/commit/
> 7f26e76c9848aeea9ec10ea701a6168464a4a9c2
> to gcc-13, should be fixed now.
I can confirm this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104661
--- Comment #3 from Fedor Chelnokov ---
Related discussion: https://stackoverflow.com/a/77021213/7325599
> -Original Message-
> From: Richard Sandiford
> Sent: Friday, September 1, 2023 2:36 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; Marcus Shawcroft
> ; Kyrylo Tkachov
> Subject: Re: [PATCH]AArch64 xorsign: Fix scalar xorsign lowering
>
> Tamar
Hi all, this is a gentle ping for the following patch:
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627913.html
> gcc/ChangeLog:
>
> * ada/Makefile.rtl: Add LoongArch support.
> * ada/libgnarl/s-linux__loongarch.ads: New.
> * ada/libgnat/system-linux-loongarch.ads: New.
> * config/loongarch/loongarch.h: mark normalized options
> passed from driver to gnat1 as explicit for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83077
--- Comment #6 from Iain Sandoe ---
is there a version available for testing, rebased to trunk (the one I saw from
Aug 19th pretty much fails to apply for most entries)?
Change is OK, thanks!
> Noticed trivial syntax errors in gcc/ada/expect.c when tried to compile gcc
> 13.2 as cross-compiler for target i686-pc-msdosdjgpp.
>
> Errors were there since
>
> Tiedostossa, joka sisällytettiin kohdasta expect.c:54:
> expect.c:Funktio ”__gnat_waitpid”:
>
Tamar Christina writes:
> Hi All,
>
> In GCC-9 our scalar xorsign pattern broke and we didn't notice it because the
> testcase was not strong enough. With this commit
>
> 8d2d39587d941a40f25ea0144cceb677df115040 is the first bad commit
> commit 8d2d39587d941a40f25ea0144cceb677df115040
> Author:
On Thu, Aug 31, 2023 at 05:46:28PM -0400, Jason Merrill wrote:
> I've suggested this to Core.
Thanks.
> > So, I'm not really sure what to do. Intuitively the patch seems right
> > because even block externs redeclare stuff and change meaning of the
> > identifiers and void foo () { int i;
Hello
and ping.
Thanks,
Martin
On Fri, May 12 2023, Martin Jambor wrote:
> Hi,
>
> PR 108007 is another manifestation where we rely on DCE to clean-up
> after IPA-SRA and if the user explicitely switches DCE off, IPA-SRA
> can leave behind statements which are fed uninitialized values and
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111264
--- Comment #4 from Hans-Peter Nilsson ---
(In reply to Andrew Pinski from comment #3)
> You are mostly correct.
> In C++17, Copy elision is guaranteed to be done here while in earlier
> versions it is not and earlier versions of C++ require a
Hello
and ping.
Thanks,
Martin
On Fri, Aug 18 2023, Martin Jambor wrote:
> Hi,
>
> testing on 32bit arm revealed that even the simplest case of PR 110378
> was still not resolved there because destructors were returning this
> pointer. Needless to say, the return value of those destructors
On Thu, Aug 31, 2023 at 03:52:22PM -0400, Jason Merrill wrote:
> On 8/31/23 03:20, Jakub Jelinek wrote:
> > As the following testcase shows, while check_local_shadow diagnoses most of
> > the [basic.scope.block]/2 violations, it doesn't diagnose when parameter's
> > name is redeclared inside of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111269
Bug ID: 111269
Summary: Confusing location of error in source code
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Hi Jonathan,
On 2023-09-01 08:49, Jonathan Wakely wrote:
> On Thu, 31 Aug 2023, 17:05 Alejandro Colomar via Gcc,
> wrote:
>
>> Hi!
>>
>> I've been confused for some time with a compilation error that
>> pointed to a slightly-off location. I wasn't seeing that I used
>> a temporary variable in
On 8/31/23 17:01, Edwin Lu wrote:
Related Discussion:
https://inbox.sourceware.org/gcc-patches/12fb5088-3f28-0a69-de1e-f387371a5...@gmail.com/
This patch updates the pic instructions to ensure that no insn is left
without a type attribute.
Tested for regressions using rv32/64 multilib with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111069
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:cd37325b8d500bf4021692620686572d5ffb0868
commit r14-3624-gcd37325b8d500bf4021692620686572d5ffb0868
Author: Jakub Jelinek
Date:
On 8/31/23 11:57, Vineet Gupta wrote:
On 8/31/23 06:51, Jeff Law wrote:
On 8/30/23 15:57, Vineet Gupta wrote:
This was tripping up gcc.c-torture/execute/pr60003.c at -O1 since the
pattern semantics can't be expressed by zicond instructions.
This involves test code snippet:
if
It affects the build, and if used as a static file, can reliably be
tracked using the `-MF` mechanism.
gcc/cp/:
* mapper-client.cc, mapper-client.h (open_module_client): Accept
dependency tracking and track module mapper files as
dependencies.
* module.cc
This patch implements support for [P1689R5][] to communicate to a build
system the C++20 module dependencies to build systems so that they may
build `.gcm` files in the proper order.
Support is communicated through the following three new flags:
- `-fdeps-format=` specifies the format for the
It affects the build, and if used as a static file, can reliably be
tracked using the `-MF` mechanism.
gcc/cp/:
* mapper-client.cc, mapper-client.h (open_module_client): Accept
dependency tracking and track module mapper files as
dependencies.
* module.cc
They affect the build, so report them via `-MF` mechanisms.
gcc/cp/
* module.cc (do_import): Report imported CMI files as
dependencies.
gcc/testsuite/
* g++.dg/modules/depreport-1_a.C: New test.
* g++.dg/modules/depreport-1_b.C: New test.
*
When passing `-o` flags to other options, the typical `-o foo` spelling
leaves a leading whitespace when replacing elsewhere. This ends up
creating flags spelled as `-some-option-with-arg= foo.ext` which doesn't
parse properly. When attempting to make a spec function to just remove
the leading
They affect the build, so report them via `-MF` mechanisms.
gcc/cp/
* module.cc (do_import): Report imported CMI files as
dependencies.
gcc/testsuite/
* g++.dg/modules/depreport-1_a.C: New test.
* g++.dg/modules/depreport-1_b.C: New test.
*
This patch implements support for [P1689R5][] to communicate to a build
system the C++20 module dependencies to build systems so that they may
build `.gcm` files in the proper order.
Support is communicated through the following three new flags:
- `-fdeps-format=` specifies the format for the
Hi,
This patch series adds initial support for ISO C++'s [P1689R5][], a
format for describing C++ module requirements and provisions based on
the source code. This is required because compiling C++ with modules is
not embarrassingly parallel and need to be ordered to ensure that
`import
Hi,
This patch series adds initial support for ISO C++'s [P1689R5][], a
format for describing C++ module requirements and provisions based on
the source code. This is required because compiling C++ with modules is
not embarrassingly parallel and need to be ordered to ensure that
`import
When passing `-o` flags to other options, the typical `-o foo` spelling
leaves a leading whitespace when replacing elsewhere. This ends up
creating flags spelled as `-some-option-with-arg= foo.ext` which doesn't
parse properly. When attempting to make a spec function to just remove
the leading
Ping for the use of __is_signed built-in.
Sincerely,
Ken Matsui
On Wed, Jul 12, 2023 at 6:45 PM Ken Matsui wrote:
>
> This patch lets libstdc++ use new built-in trait __is_signed.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_signed): Use __is_signed built-in trait.
>
On Fri, Sep 1, 2023 at 3:35 PM Roger Sayle wrote:
>
>
> Hi Manolis,
> Many thanks. If you haven't already, could you create/file a
> bug report at https://gcc.gnu.org/bugzilla/ which ensures this
> doesn't get lost/forgotten. It provides a PR number for tracking
> discussions, and patches/fixes
Ping for the use of __is_pointer built-in.
Sincerely,
Ken Matsui
On Thu, Jul 13, 2023 at 1:49 PM Ken Matsui wrote:
>
> This patch lets libstdc++ use new built-in trait __is_pointer.
>
> libstdc++-v3/ChangeLog:
>
> * include/bits/cpp_type_traits.h (__is_ptr): Use __is_pointer
>
Ping for the use of __is_array built-in.
Sincerely,
Ken Matsui
On Fri, Jul 7, 2023 at 10:24 PM Ken Matsui wrote:
>
> This patch lets libstdc++ use new built-in trait __is_array.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_array): Use __is_array built-in trait.
>
Ping for std::is_object.
Sincerely,
Ken Matsui
On Wed, Jul 12, 2023 at 7:42 PM Ken Matsui wrote:
>
> This patch gets std::is_object to dispatch to new built-in traits,
> __is_function and __is_reference.
>
> libstdc++-v3/ChangeLog:
> * include/std/type_traits (is_object): Use new
Ping for the use of __is_const built-in.
Sincerely,
Ken Matsui
On Fri, Jul 7, 2023 at 10:27 PM Ken Matsui wrote:
>
> This patch lets libstdc++ use new built-in trait __is_const.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_const): Use __is_const built-in trait.
>
Ping for the use of __is_volatile built-in.
Sincerely,
Ken Matsui
On Fri, Jul 7, 2023 at 10:19 PM Ken Matsui wrote:
>
> This patch lets libstdc++ use new built-in trait __is_volatile.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_volatile): Use __is_volatile built-in
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268
--- Comment #3 from Mathieu Malaterre ---
For reference
% /usr/lib/gcc-snapshot/bin/gcc -march=armv8.2-a+sve -O2 -c m.c && echo
"success"
success
with
% cat m.c
#pragma GCC aarch64 "arm_sve.h"
svbool_t
foo (svint8_t a, svint8_t b, svbool_t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268
--- Comment #1 from Mathieu Malaterre ---
Created attachment 55830
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55830=edit
preprocessed source
% /usr/lib/gcc-snapshot/bin/g++ -O2 -g -DNDEBUG -c testcase.i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268
--- Comment #2 from Mathieu Malaterre ---
% /usr/lib/gcc-snapshot/bin/g++ --version
g++ (Debian 20230811-1) 14.0.0 20230811 (experimental) [master
r14-3139-g68783211f66]
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268
Bug ID: 111268
Summary: internal compiler error: in to_constant, at
poly-int.h:504
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111267
Bug ID: 111267
Summary: Codegen regression from i386 argument passing changes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Hi All,
In GCC-9 our scalar xorsign pattern broke and we didn't notice it because the
testcase was not strong enough. With this commit
8d2d39587d941a40f25ea0144cceb677df115040 is the first bad commit
commit 8d2d39587d941a40f25ea0144cceb677df115040
Author: Segher Boessenkool
Date: Mon Oct 22
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111017
Tobias Burnus changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111017
--- Comment #7 from CVS Commits ---
The releases/gcc-12 branch has been updated by Tobias Burnus
:
https://gcc.gnu.org/g:2f8ccacd41a45bccf3e19625c0fbd2627472b45e
commit r12-9841-g2f8ccacd41a45bccf3e19625c0fbd2627472b45e
Author: Tobias Burnus
Hi Manolis,
Many thanks. If you haven't already, could you create/file a
bug report at https://gcc.gnu.org/bugzilla/ which ensures this
doesn't get lost/forgotten. It provides a PR number for tracking
discussions, and patches/fixes with PR numbers are (often)
prioritized during the review and
On Fri, 1 Sep 2023, Jiufu Guo wrote:
> Hi,
>
> Integer expression "(X - N * M) / N" can be optimized to "X / N - M" with
> the below conditions:
> 1. There is no wrap/overflow/underflow.
>wrap/overflow/underflow breaks the arithmetic operation.
> 2. "X - N * M" and "X" are not of opposite
On Thu, Aug 31, 2023 at 10:24:10AM -0700, Andrew Pinski via Gcc-patches wrote:
> This patch adds the following match patterns to optimize these:
> /* (a != b) ? (a - b) : 0 -> (a - b) */
These tests FAIL on i686-linux, with
.../gcc/testsuite/gcc.dg/pr110915-1.c:8:1: warning: MMX vector return
On Wed, Aug 30, 2023 at 03:25:11PM -0700, Andrew Pinski via Gcc-patches wrote:
> This simple patch extends the min_value/max_value match to vector integer
> types.
> Using uniform_integer_cst_p makes this easy.
These tests FAIL on i686-linux, with
.../gcc/testsuite/gcc.dg/pr110915-1.c:8:1:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19832
--- Comment #13 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:c2d3211d580369b75200fbdd7b854d30460e0aba
commit r14-3623-gc2d3211d580369b75200fbdd7b854d30460e0aba
Author: Jakub Jelinek
Date:
On Wed, Aug 30, 2023 at 04:28:18PM -0400, Jason Merrill wrote:
> On 8/29/23 09:35, Nathaniel Shead wrote:
> > This is an attempt to improve the constexpr machinery's handling of
> > union lifetime by catching more cases that cause UB. Is this approach
> > OK?
> >
> > I'd also like some feedback
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110915
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:b8df57b3221aac70f22fb5c93d0b95bf22fded90
commit r14-3622-gb8df57b3221aac70f22fb5c93d0b95bf22fded90
Author: Jakub Jelinek
Date:
> For some reason, your email is endeing up in a strange format, I almost
> missed the .patch file attached, making the review harder.
Never mind, I was on vacation earlier this month and then busy with a seminar
last week, so I started looking at your ping email before the original email
which
Richard,
For some reason, your email is endeing up in a strange format, I almost
missed the .patch file attached, making the review harder.
There's a typo in the comment added:
+ -- explicit limitedness implied by a synchronized private extension
+ -- the does not derive from a
On Thu, 2023-08-31 at 21:25 -0400, Eric Feng wrote:
> On Thu, Aug 31, 2023 at 4:19 PM David Malcolm
> wrote:
> >
> > On Thu, 2023-08-31 at 15:09 -0400, Eric Feng wrote:
> > > On Thu, Aug 31, 2023 at 1:01 PM David Malcolm
> > >
> > > wrote:
> > > >
> > > > On Wed, 2023-08-30 at 18:15 -0400,
On Fri, Sep 01, 2023 at 07:34:16PM +0800, Hongyu Wang wrote:
> > On Fri, Sep 01, 2023 at 05:07:53PM +0800, Hongyu Wang wrote:
> > > Jakub Jelinek via Gcc-patches 于2023年8月31日周四
> > > 17:44写道：
> > > >
> > > > On Thu, Aug 31, 2023 at 04:20:19PM +0800, Hongyu Wang via Gcc-patches
> > > > wrote:
> >
On Wed, Aug 9, 2023 at 6:53 PM Di Zhao OS wrote:
>
> Hi,
>
> The previous version of this patch tries to solve two problems
> at the same time. For better clarity, I'll separate them and
> only deal with the "nested" FMA in this version. I plan to
> propose another patch in avoiding bad shaped
On 2023/9/1 18:00, Robin Dapp via Gcc-patches wrote:
Thanks, LGTM.
Thanks, committed these patches.
Btw. I haven't forgotten to respond to your last refactor but just didn't find
the time yet. I figured I should have some proper draft before suggesting
more things :)
Well, let's talk
Jakub Jelinek 于2023年9月1日周五 17:20写道：
>
> On Fri, Sep 01, 2023 at 05:07:53PM +0800, Hongyu Wang wrote:
> > Jakub Jelinek via Gcc-patches 于2023年8月31日周四
> > 17:44写道：
> > >
> > > On Thu, Aug 31, 2023 at 04:20:19PM +0800, Hongyu Wang via Gcc-patches
> > > wrote:
> > > > For vector move insns like
This patch optimizes the performance of the is_compound trait by
dispatching to the new __is_arithmetic built-in trait.
libstdc++-v3/ChangeLog:
* include/std/type_traits (is_compound): Do not use __not_.
(is_compound_v): Use is_fundamental_v instead.
Signed-off-by: Ken Matsui
On Fri, Sep 1, 2023 at 12:36 PM Hongtao Liu wrote:
>
> On Fri, Sep 1, 2023 at 5:38 PM Uros Bizjak via Gcc-patches
> wrote:
> >
> > On Fri, Sep 1, 2023 at 11:10 AM Hongyu Wang wrote:
> > >
> > > Uros Bizjak via Gcc-patches 于2023年8月31日周四
> > > 18:01写道：
> > > >
> > > > On Thu, Aug 31, 2023 at
This patch optimizes the performance of the is_fundamental trait by
dispatching to the new __is_arithmetic built-in trait.
libstdc++-v3/ChangeLog:
* include/std/type_traits (is_fundamental_v): Use __is_arithmetic
built-in trait.
(is_fundamental): Likewise. Optimize the
This patch optimizes the performance of the is_arithmetic trait by
dispatching to the new __is_arithmetic built-in trait.
libstdc++-v3/ChangeLog:
* include/std/type_traits (is_arithmetic): Use __is_arithmetic
built-in trait.
(is_arithmetic_v): Likewise.
Signed-off-by:
This patch implements built-in trait for std::is_arithmetic.
gcc/cp/ChangeLog:
* cp-trait.def: Define __is_arithmetic.
* constraint.cc (diagnose_trait_expr): Handle CPTK_IS_ARITHMETIC.
* semantics.cc (trait_expr_value): Likewise.
(finish_trait_expr): Likewise.
On Fri, Sep 1, 2023 at 4:27 AM Andrew Pinski via Gcc-patches
wrote:
>
> This pushes the conversion further down the chain which allows to optimize
> away more
> conversions in many cases.
But when building (T1)(T2)-x it will make simplifying (T1)(T2) more difficult
as we'd need a
(convert
On Wed, 23 Aug 2023 at 17:03, Jonathan Wakely via Libstdc++
wrote:
>
> Any objections to this? It's a C++23 feture, so should be enabled by
> default.
I've pushed this to trunk, so let's see what breaks!
>
> -- >8 --
>
> This causes libstdc++_libbacktrace.a to be built by default. This might
>
Tested x86_64-linux. Pushed to trunk.
-- >8 --
This test expects to be able to link, which fails if there are undefined
references to chdir, mkdir etc. in fs_ops.o in the libstdc++.a archive.
libstdc++-v3/ChangeLog:
* testsuite/27_io/filesystem/path/108636.cc: Add dg-require for
Tested x86_64-linux. Pushed to trunk.
-- >8 --
chrono::tzdb::current_zone uses filesystem::read_symlink, which creates
a dependency on the fs_ops.o object in libstdc++.a, which then creates
dependencies on several OS functions if --gc-sections isn't used. For
more details see PR libstdc++/104167
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104167
--- Comment #13 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f2eb6132c6951edf7960a82828c571a1b98a1a09
commit r14-3616-gf2eb6132c6951edf7960a82828c571a1b98a1a09
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110817
--- Comment #12 from Zdenek Sojka ---
(In reply to Andrew Pinski from comment #11)
> (In reply to Zdenek Sojka from comment #10)
> > Probably related, even simpler testcase, failing everywhere at -O0:
> >
> > $ cat testcase.c
> > typedef
Uros Bizjak via Gcc-patches writes:
> On Thu, Aug 31, 2023 at 11:18 AM Jakub Jelinek via Gcc-patches
> wrote:
>>
>> On Thu, Aug 31, 2023 at 04:20:17PM +0800, Hongyu Wang via Gcc-patches wrote:
>> > From: Kong Lingling
>> >
>> > In inline asm, we do not know if the insn can use EGPR, so disable
Committed, thank Robin.
Pan
-Original Message-
From: Gcc-patches On Behalf
Of Robin Dapp via Gcc-patches
Sent: Friday, September 1, 2023 5:58 PM
To: Juzhe-Zhong ; gcc-patches@gcc.gnu.org
Cc: kito.ch...@sifive.com; kito.ch...@gmail.com
Subject: Re: [PATCH] RISC-V: Enable
Committed, thanks Robin.
Pan
-Original Message-
From: Gcc-patches On Behalf
Of Robin Dapp via Gcc-patches
Sent: Friday, September 1, 2023 5:58 PM
To: Juzhe-Zhong ; gcc-patches@gcc.gnu.org
Cc: kito.ch...@sifive.com; kito.ch...@gmail.com
Subject: Re: [PATCH] RISC-V: Add dynamic LMUL
Tested x86_64-linux. Pushed to trunk.
-- >8 --
We fail to diagnose an error and extract an incorrect time for cases
like "25:59" >> parse("%H:%M", mins). The bad "25" hour value gets
ignored (on the basis that we might not care about it if trying to
extract something like a weekday or a month
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target Milestone|13.3
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Using an offset as the second argument instead of an iterator makes it
easier for callers, as they don't need to create an lvalue span in order
to get an iterator from it for the _M_reset call.
libstdc++-v3/ChangeLog:
* include/std/format
Hi,
The below (slightly) reduced test-case from gcc.c-torture/execute/simd-2.c
produces an execution failure for avr.
typedef short __attribute__((vector_size (16))) vecint;
vecint i = { 150, 100, 150, 200, 0, 0, 0, 0 };
vecint j = { 10, 13, 20, 30, 1, 1, 1, 1 };
vecint k;
union {
vecint
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/62
* include/bits/chrono_io.h (_Parser::Operator()): Check %C
values are in range of year::min() to year::max().
* testsuite/std/time/parse.cc: Check out of range centuries.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:207c507499d23f0176cbfdfe96d3cd50dec39584
commit r14-3609-g207c507499d23f0176cbfdfe96d3cd50dec39584
Author: Jonathan Wakely
On Fri, 1 Sep 2023, Filip Kastl wrote:
> > That's interesting. Your placement at
> >
> > NEXT_PASS (pass_cd_dce, false /* update_address_taken_p */);
> > NEXT_PASS (pass_phiopt, true /* early_p */);
> > + NEXT_PASS (pass_sccp);
> >
> > and
> >
> >NEXT_PASS
Robin Dapp via Gcc-patches writes:
>> It's not just a question of which byte though. It's also a question
>> of which bit.
>>
>> One option would be to code-generate for even X and for odd X, and select
>> between them at runtime. But that doesn't scale well to 2+2X and 1+1X.
>>
>> Otherwise
Hi Roger,
I've (accidentally) found a codegen regression that I bisected down to
this patch.
For these two functions:
typedef struct {
float minx, miny;
float maxx, maxy;
} AABB;
int TestOverlap(AABB a, AABB b) {
return a.minx <= b.maxx
&& a.miny <= b.maxy
&& a.maxx >= b.minx
On Tue, Aug 8, 2023 at 1:33 PM Jonathan Wakely wrote:
>
>
>
> On Tue, 18 Jul 2023 at 08:44, Ken Matsui via Libstdc++
> wrote:
>>
>> This patch optimizes the performance of the is_compound trait by
>> dispatching to the new __is_arithmetic built-in trait.
>>
>> libstdc++-v3/ChangeLog:
>>
>>
> It's not just a question of which byte though. It's also a question
> of which bit.
>
> One option would be to code-generate for even X and for odd X, and select
> between them at runtime. But that doesn't scale well to 2+2X and 1+1X.
>
> Otherwise I think we need to treat the bit position
On Thu, Aug 31, 2023 at 5:31 PM Richard Biener via Gcc-patches
wrote:
>
> On Thu, Aug 31, 2023 at 11:26 AM Richard Biener
> wrote:
> >
> > On Thu, Aug 31, 2023 at 10:25 AM Hongyu Wang via Gcc-patches
> > wrote:
> > >
> > > From: Kong Lingling
> > >
> > > Disable EGPR usage for below legacy
On Fri, Sep 1, 2023 at 5:38 PM Uros Bizjak via Gcc-patches
wrote:
>
> On Fri, Sep 1, 2023 at 11:10 AM Hongyu Wang wrote:
> >
> > Uros Bizjak via Gcc-patches 于2023年8月31日周四 18:01写道：
> > >
> > > On Thu, Aug 31, 2023 at 11:18 AM Jakub Jelinek via Gcc-patches
> > > wrote:
> > > >
> > > > On Thu,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110817
--- Comment #11 from Andrew Pinski ---
(In reply to Zdenek Sojka from comment #10)
> Probably related, even simpler testcase, failing everywhere at -O0:
>
> $ cat testcase.c
> typedef unsigned long __attribute__((__vector_size__ (8))) V;
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110817
--- Comment #10 from Zdenek Sojka ---
Probably related, even simpler testcase, failing everywhere at -O0:
$ cat testcase.c
typedef unsigned long __attribute__((__vector_size__ (8))) V;
int
main (void)
{
V v = ~((V) { } <=0);
if (v[0])
This one is OK as well, thanks.
Regards
Robin
From: Christoph Müllner
Recently, these xtheadcondmov tests regressed with -Oz:
* FAIL: gcc.target/riscv/xtheadcondmov-mveqz-imm-eqz.c
* FAIL: gcc.target/riscv/xtheadcondmov-mveqz-imm-not.c
* FAIL: gcc.target/riscv/xtheadcondmov-mvnez-imm-cond.c
* FAIL:
Hi Lehua,
this is OK, thanks.
Regards
Robin
> That's interesting. Your placement at
>
> NEXT_PASS (pass_cd_dce, false /* update_address_taken_p */);
> NEXT_PASS (pass_phiopt, true /* early_p */);
> + NEXT_PASS (pass_sccp);
>
> and
>
>NEXT_PASS (pass_tsan);
>NEXT_PASS (pass_dse, true /* use DR
Hi David,
On Fri, Sep 1, 2023 at 1:59 AM David Malcolm wrote:
> On Fri, 2023-09-01 at 00:04 +0200, priour...@gmail.com wrote:
>
>
[..snip..]
> ...which will only fire if arg 1 is a region_svalue. This won't
> trigger if you have e.g. a binop_svalue for pointer arithmetic.
>
> What happens
Hi Lehua,
this LGTM now, thanks. It's also easier to read after the refactor :)
Regards
Robin
Thanks, LGTM.
Btw. I haven't forgotten to respond to your last refactor but just didn't find
the time yet. I figured I should have some proper draft before suggesting
more things :)
Regards
Robin
LTGM
juzhe.zh...@rivai.ai
From: Robin Dapp
Date: 2023-09-01 17:55
To: gcc-patches; palmer; Kito Cheng; jeffreyalaw; juzhe.zh...@rivai.ai
CC: rdapp.gcc
Subject: [PATCH] RISC-V: Add vec_extract for BI -> QI.
Hi,
this patch adds a vec_extract expander that extracts a QImode from a
vector mask
LGTM
Regards
Robin
Hi Juzhe,
thanks, this is OK, we would have needed this sooner or later anyway.
Regards
Robin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111266
Bug ID: 111266
Summary: Missing -Wanalyzer-out-of-bounds for concrete offset
overwrite.
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Hi,
this patch adds a vec_extract expander that extracts a QImode from a
vector mask mode. In doing so, it helps recognize a "live operation"/extract
last idiom for mask modes.
It fixes the ICE in tree-vect-live-6.c by circumventing the fallback
code in extract_bit_field_1. The problem there is
This mailing list is for automated email from our bug tracker, it's
not for reporting bugs directly. Emails sent to this list are likely
to be missed, and definitely won't get entered into the bug tracker.
Please use Bugzilla to report bugs, as described at https://gcc.gnu.org/bugs/
On Fri, Sep 1, 2023 at 11:10 AM Hongyu Wang wrote:
>
> Uros Bizjak via Gcc-patches 于2023年8月31日周四 18:01写道：
> >
> > On Thu, Aug 31, 2023 at 11:18 AM Jakub Jelinek via Gcc-patches
> > wrote:
> > >
> > > On Thu, Aug 31, 2023 at 04:20:17PM +0800, Hongyu Wang via Gcc-patches
> > > wrote:
> > > >
101 - 200 of 233 matches
Mail list logo
