Hi Jonathan
Thanks so much for implementing this.
There are a couple of typos in the patch description:
's/C==17RandomAccessIterator/Cpp17RandomAccessIterator/' and
's/__or_/__and_/'.
I've applied your patch localy and it works fine for all my use cases,
which admitedly simply consist of using v
Hi!
As the testcase shows, the INTEGER_CST handling in handle_operand_addr
(i.e. what is used when passing address of an integer to a bitint library
routine) wasn't correct. If the minimum precision to represent an
INTEGER_CST is smaller or equal to limb_prec, the code correctly uses
m_limb_type;
On Wed, Jan 10, 2024 at 06:07:16PM +, Tamar Christina wrote:
> --- a/gcc/testsuite/gcc.dg/vect/vect-early-break_100-pr113287.c
> +++ b/gcc/testsuite/gcc.dg/vect/vect-early-break_100-pr113287.c
When the testcase was being adjusted for unsigned long -> unsigned long long,
two spots using long we
> Am 13.01.2024 um 10:44 schrieb Jakub Jelinek :
>
> Hi!
>
> As the testcase shows, the INTEGER_CST handling in handle_operand_addr
> (i.e. what is used when passing address of an integer to a bitint library
> routine) wasn't correct. If the minimum precision to represent an
> INTEGER_CST is
On Sat, 13 Jan 2024 at 00:06, Patrick Palka wrote:
>
> On Fri, 12 Jan 2024, Jonathan Wakely wrote:
>
> > On Fri, 12 Jan 2024 at 18:33, Patrick Palka wrote:
> > >
> > > On Fri, 12 Jan 2024, Jonathan Wakely wrote:
> > >
> > > > On Fri, 12 Jan 2024 at 17:55, Patrick Palka wrote:
> > > > >
> > > > >
On Fri, 12 Jan 2024 at 22:59, Jonathan Wakely wrote:
>
> It would be good to update the bundled tzdata for GCC 14.1 and 13.3
The expiry date for the hardcoded leapseconds list should be updated
too, as there's a new date in the file in the tzdata distro. There are
no new leap seconds though, just
On Sat, 13 Jan 2024 at 09:36, Pilar Latiesa wrote:
>
> Hi Jonathan
>
> Thanks so much for implementing this.
>
> There are a couple of typos in the patch description:
> 's/C==17RandomAccessIterator/Cpp17RandomAccessIterator/' and
> 's/__or_/__and_/'.
Thanks for the comments, I'll fix those.
>
Tom Tromey writes:
> When I enable cgen rebuilding in the binutils-gdb tree, the default is
> to run cgen using 'guile'. However, on my host, guile is guile 2.2,
> which doesn't work for me -- I have to use guile3.0.
>
> This patch arranges to pass "GUILE" down to subdirectories, so I can
> use
Patch v2, with more tests. This fixes a bug in lookup by name where if
an alias was matched then the aliases() view wouldn't contain the
primary name or other aliases earlier in the table.
It also optimizes text_encoding::environment_is so it constructs an
encoding by ID and then only matches the
在 2024-01-13星期六的 15:01 +0800，chenglulu写道：
>
> 在 2024/1/12 下午7:42, Xi Ruoyao 写道:
> > 在 2024-01-12星期五的 09:46 +0800，chenglulu写道：
> >
> > > > I found an issue bootstrapping GCC with -mcmodel=extreme in BOOT_CFLAGS:
> > > > we need a target hook to tell the generic code
> > > > UNSPEC_LA_PCREL_64_PART
在 2024-01-13星期六的 15:28 +0800，chenxiaolong写道：
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/pr104992.c: Added additional "-mlsx" compilation options.
> * gcc.dg/signbit-2.c: Dito.
> * gcc.dg/tree-ssa/scev-16.c: Dito.
> * gfortran.dg/graphite/vect-pr40979.f90: Dito.
> * gfort
This is a short series of patches to support non-ELF targets in
the jit tests where these use target-specific capabilities (e.g.
alias support, or scanning for assembler directives.)
An alternative would be to skip these tests for Darwin.
Tested on x86_64 Darwin, and about to test Linux,
OK for t
Add a dg-require-alias to cover this.
gcc/testsuite/ChangeLog:
* jit.dg/test-alias-attribute.c: Require target alias
support.
Signed-off-by: Iain Sandoe
---
gcc/testsuite/jit.dg/test-alias-attribute.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/testsuite/jit.dg/test
Darwin has a different .section directive that has more fields and
uses different whitespace. Amend the whitespace in the scan-asm to
be more flexible.
gcc/testsuite/ChangeLog:
* jit.dg/test-link-section-assembler.c: Accept any whitespace
between the .section directive and its ar
Several of the jit tests check for assembler-specific output
which differs on Mach-O from ELF.
This patch uses the facility to make the scans targer-dependent
and adds handling for darwin.
gcc/testsuite/ChangeLog:
* jit.dg/test-always_inline-attribute.c: Handle Darwin in
jit-veri
If we want to support multiple object formats and to allow for
scan-assembler tests, we need to make it possible to adjust the
tests on a per-target basis.
This adds similar mechamisms to jit-verify-assembler-output{,-not}
to those used for the general scan-assembler dg directives.
As an aside; i
在 2024/1/13 下午9:05, Xi Ruoyao 写道:
在 2024-01-13星期六的 15:01 +0800，chenglulu写道：
在 2024/1/12 下午7:42, Xi Ruoyao 写道:
在 2024-01-12星期五的 09:46 +0800，chenglulu写道：
I found an issue bootstrapping GCC with -mcmodel=extreme in BOOT_CFLAGS:
we need a target hook to tell the generic code
UNSPEC_LA_PCREL_64_
This patch series restores PGO+LTO bootstrap on aarch64 (with the ldp
passes enabled) and fixes wrong code (leading to a segfault) seen in
cactuBSSN_r from SPEC CPU 2017 with PGO+LTO enabled.
For an example showing what goes wrong, see:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113070#c7
In t
The next patch in this series exposes an interface for creating new uses
in RTL-SSA. The intent is that new user-created uses can consume new
user-created defs in the same change group. This is so that we can
correctly update uses of memory when inserting a new store pair insn in
the aarch64 load
This exposes an interface for users to create new uses in RTL-SSA.
This is needed for updating uses after inserting a new store pair insn
in the aarch64 load/store pair fusion pass.
gcc/ChangeLog:
PR target/113070
* rtl-ssa/accesses.cc (function_info::create_use): New.
* r
In r14-5820-ga49befbd2c783e751dc2110b544fe540eb7e33eb I added support to
RTL-SSA for inserting new insns, which included support for users
creating new defs.
However, I missed that apply_changes_to_insn needed updating to ensure
that the new defs actually got inserted into the main def chain. Thi
As the PR shows (specifically #c7) we are missing updating uses of mem
when inserting an stp in the aarch64 load/store pair fusion pass. This
patch fixes that.
RTL-SSA has a simple view of memory and by default doesn't allow stores
to be re-ordered w.r.t. other stores. In the ldp fusion pass, we
Tested on hppa64-hp-hpux11.11. Committed to trunk.
Dave
---
hppa64: Fix fmt_f_default_field_width_3.f90 and fmt_g_default_field_width_3.f90
The hppa*64*-*-hpux* target is not included in the set of fortran_real_16
targets because it doesn't have cosl. However, these tests don't need
cosl, etc.
Since commit 2c3db94d9fd ("c: Turn int-conversion warnings into
permerrors") the test fails with errors such as:
FAIL: gcc.target/arm/acle/cde-mve-error-2.c -O0 (test for errors, line 32)
FAIL: gcc.target/arm/acle/cde-mve-error-2.c -O0 (test for errors, line 33)
FAIL: gcc.target/arm/
Dear all,
the testcase given in PR67277 actually consists of two separate issues:
(1) passing an optional dummy argument to an elemental (intrinsic) procedure
(2) a missing optional argument for SIZE to the ISHFTC intrinsic
shall be equivalent to using BIT_SIZE(I).
I've created a separate P
On Sat, Jan 13, 2024 at 10:12:42PM +0100, Harald Anlauf wrote:
>
> (2) a missing optional argument for SIZE to the ISHFTC intrinsic
> shall be equivalent to using BIT_SIZE(I).
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> As I consider the patch safe, I'd like to backport to 13
Hello-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109704
The below patch fixes the issue noted in the PR that extended characters
cannot appear in the identifier passed to a #pragma push_macro or #pragma
pop_macro. Bootstrap + regtest all languages on x86-64 Linux. Is it OK for
GCC 13 please?
Currently, when std::terminate() is called with a foreign exception
active, since nothing in the path checks whether the exception matches
the `GNUCC++\0` personality, a foreign exception can go into the verbose
terminate handler, and get treated as though it were a C++ exception.
Reflection is at
On Sat, Jan 13, 2024 at 5:10 PM Julia DeMille wrote:
>
> Currently, when std::terminate() is called with a foreign exception
> active, since nothing in the path checks whether the exception matches
> the `GNUCC++\0` personality, a foreign exception can go into the verbose
> terminate handler, and
On 1/13/24 19:17, Andrew Pinski wrote:
2 things, changelogs go into the email message rather than directly as
part of the patch.,
Apologies. I have prepared a revised patch, and will send it when
applicable.
Second I wonder if you could add a multiple language testcase using
GNU objective-C
On 1/10/24 14:28, Jonny Grant wrote:
>
> 2024-01-10 Jonathan Grant
> gcc/ChangeLog:
>* doc/extend.texi: Update builtin example for __builtin_FILE
> __builtin_LINE __builtin_FUNCTION.
>
>
>
>>From 66290eb477dd1a99310ad9972c45391c2a87c1c7 Mon Sep 17 00:00:00 2001
> From: Jonathan Grant
> D
On Sun, 14 Jan 2024, 01:36 Julia DeMille, wrote:
> On 1/13/24 19:17, Andrew Pinski wrote:
> > 2 things, changelogs go into the email message rather than directly as
> > part of the patch.,
>
The reason for this is that the ChangeLog files are auto-generated from the
git commit messages, not edit
32 matches
Mail list logo
