On Thu, Apr 29, 2021 at 10:02 PM Palmer Dabbelt
wrote:
> This was reported as Bug 94136, which is a year old but was categorized
> as a documentation bug. I believe that categorization was incorrect:
> having an empty __clear_cache library routine is simply incorrect
It affects almost all
On Wed, Apr 28, 2021 at 2:25 AM Geng Qi via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> gcc/ChangeLog:
> * doc/options.texi (Negative): Fix the discription so that it
> matches
> the code implementation of prune_options().
>
This matches my testing as mentioned in another
AIX symbol references can refer to either the symbol (a label) or a
symbol with a qualifier (the storage mapping class). The storage mapping
class provide information about the underlying COFF section into which the
symbol will be placed, e.g. [RO] for read-only in the text section,
[RW] for
C/C++ permits to use || and && (logical OR and logical AND) for
floating-point and complex scalars; those evaluated unequal zero
and the result is of type 'int' with value 0 or 1.
While || and && with floating-point numbers is somewhat sensible,
it does not really make sense to use a
On Sat, May 1, 2021 at 12:48 AM Jeff Law wrote:
>
>
> On 4/26/2021 5:38 AM, Christoph Muellner via Gcc-patches wrote:
> > [ree] PR rtl-optimization/100264: Handle more PARALLEL SET expressions
> >
> > PR rtl-optimization/100264
> > * ree.c (get_sub_rtx): Ignore SET expressions
On Fri, 30 Apr 2021, Jonathan Wakely wrote:
> On 30/04/21 17:34 -0400, Patrick Palka via Libstdc++ wrote:
> > On Fri, 30 Apr 2021, Tim Song wrote:
> >
> > > On Fri, Apr 30, 2021 at 12:11 PM Patrick Palka via Libstdc++
> > > wrote:
> > > >
> > > > + template
> > > > + _Tp&
> > > >
On 4/26/2021 5:38 AM, Christoph Muellner via Gcc-patches wrote:
[ree] PR rtl-optimization/100264: Handle more PARALLEL SET expressions
PR rtl-optimization/100264
* ree.c (get_sub_rtx): Ignore SET expressions without register
destinations.
On 4/26/2021 8:27 AM, Aldy Hernandez via Gcc-patches wrote:
Right now we have GTY support for static storage iranges
(int_range<>). However, there's no reason why the base
class can't be used with GC, other than it was an oversight.
For that matter, the base class has a pointer to the
On 30/04/21 12:43 -0500, Tim Song via Libstdc++ wrote:
On Fri, Apr 30, 2021 at 12:11 PM Patrick Palka via Libstdc++
wrote:
+ template
+ _Tp&
+ _M_emplace_deref(const _Iter& __i)
+ {
+ this->reset();
+ return this->emplace(*__i);
+ }
On 30/04/21 17:34 -0400, Patrick Palka via Libstdc++ wrote:
On Fri, 30 Apr 2021, Tim Song wrote:
On Fri, Apr 30, 2021 at 12:11 PM Patrick Palka via Libstdc++
wrote:
>
> + template
> + _Tp&
> + _M_emplace_deref(const _Iter& __i)
> + {
> + this->reset();
Hi David-
With GCC 11 released now, I thought it might be a good time to ping this patch
that supports -finput-charset for diagnostics please?
[https://gcc.gnu.org/pipermail/gcc-patches/2021-January/564527.html]
Patch still applies to master, and tests still look good as before. If you
have any
On 4/30/2021 12:36 PM, Simon Marchi via Gcc-patches wrote:
On 2021-04-26 7:32 a.m., Nick Clifton via Gdb-patches wrote:> Hi Guys,
Given that gcc, gdb and now binutils are all now requiring C99 as a
minimum version of C, are there any objections to updating
configure.ac to reflect
Hi!
On Thu, Apr 29, 2021 at 05:50:48PM +0800, Jiufu Guo wrote:
> When there is the possibility that overflow may happen on the loop index,
> a few optimizations would not happen. For example code:
>
> foo (int *a, int *b, unsigned k, unsigned n)
> {
> while (++k != n)
> a[k] = b[k] + 1;
>
On Fri, 30 Apr 2021, Tim Song wrote:
> On Fri, Apr 30, 2021 at 12:11 PM Patrick Palka via Libstdc++
> wrote:
> >
> > + template
> > + _Tp&
> > + _M_emplace_deref(const _Iter& __i)
> > + {
> > + this->reset();
> > + return this->emplace(*__i);
> >
On 28/04/21 16:14 +0100, Jonathan Wakely wrote:
As noted in r11-1339-gb6ab9ecd550227684643b41e9e33a4d3466724d8 we define
a non-standard __cpp_lib_constexpr_char_traits feature test macro to
indicate support for P0426R1 and P1032R1. At some point last year the
__cpp_lib_constexpr_string macro was
On Fri, Apr 30, 2021 at 1:03 AM gengqi-linux
wrote:
> Thanks for your replies.
>
I would suggest filing a bug report, and adding useful info from this
thread to the bug report. Then we can track it.
Jim
On Fri, Apr 30, 2021 at 3:31 PM Jonathan Wakely wrote:
>
> On 29/04/21 16:06 -0400, David Edelsohn wrote:
> >On Fri, Jan 8, 2021 at 1:37 PM Jonathan Wakely wrote:
> >>
> >> On 06/01/21 19:41 -0500, David Edelsohn wrote:
> >> >Thanks for clarifying the issue.
> >> >
> >> >As you implicitly point
Bill Schmidt via Gcc-patches wrote:
2021-03-04 Bill Schmidt
gcc/
* config/rs6000/darwin.h (SUBTARGET_INIT_BUILTINS): Use the new
decl when new_builtins_are_live.
* config/rs6000/rs6000-builtin-new.def (__builtin_cfstring): New
built-in.
This is fine from
On 29/04/21 16:06 -0400, David Edelsohn wrote:
On Fri, Jan 8, 2021 at 1:37 PM Jonathan Wakely wrote:
On 06/01/21 19:41 -0500, David Edelsohn wrote:
>Thanks for clarifying the issue.
>
>As you implicitly point out, GCC knows the type of INT64 and defines
>the macro __INT64_TYPE__ . The
Senthil Kumar Selvaraj via Gcc-patches:
John Paul Adrian Glaubitz writes:
On 4/28/21 7:59 PM, Senthil Kumar Selvaraj wrote:
https://gcc.gnu.org/git?p=gcc.git;a=commit;h=3ba781d3b5c8efadb60866c9743b657e8f0eb222
Awesome \o/. Should we wait for the second patch [1] to be merged as well
before
On 4/27/21 10:32 AM, Bill Schmidt wrote:
The design of the target-specific built-in function support in the
Power back end has not stood the test of time. The machinery is
grossly inefficient, confusing, and arcane; and adding new built-in
functions is inefficient and error-prone. This patch
My r11-295 patch for PR68942 didn't consider that the callee of an
ADL-eligible function call can be a TEMPLATE_ID_EXPR, and we don't want
to disable mark_used when substituting into the template arguments of
this TEMPLATE_ID_EXPR because the arguments are clearly used regardless
of the outcome of
On 4/30/21 9:11 AM, Jose E. Marchesi via Gcc-patches wrote:
>
>>> For a moment, for the sake of this question, if we establish that CTF/BTF
>>> generation always feeds off DWARF DIEs (so there is no need to access
>>> type/decl tree nodes), what will it take to keep LTO support while keeping
On 2021-04-26 7:32 a.m., Nick Clifton via Gdb-patches wrote:> Hi Guys,
>
> Given that gcc, gdb and now binutils are all now requiring C99 as a
> minimum version of C, are there any objections to updating
> configure.ac to reflect this ?
>
> Cheers
> Nick
>
> diff --git a/configure.ac
Richard Sandiford via Gcc-patches writes:
> Jonathan Wright writes:
>> diff --git a/gcc/config/aarch64/aarch64-simd.md
>> b/gcc/config/aarch64/aarch64-simd.md
>> index
>> bdee49f74f4725409d33af733bb55be290b3f0e7..234762960bd6df057394f753072ef65a6628a43d
>> 100644
>> ---
Hi Richard,
On 21/04/2021 13:05, Richard Sandiford wrote:
> Alex Coplan writes:
> > Hi Richard,
> >
> > On 15/04/2021 18:45, Richard Sandiford wrote:
> >> Looks good in general, but like you say, it's GCC 12 material.
> >
> > Thanks for the review. The attached patch addresses these comments and
On Thu, 29 Apr 2021, Jim Wilson wrote:
> Note that only in the -mfoo6= case are the duplicate options removed from
> the command line. So pruning options requires that you have both
> RejectNegative and Negative pointing at yourself, which is not what the
> documentation says.
Thanks for the
Hello! Looping back around to this. re:
https://gcc.gnu.org/pipermail/gcc-patches/2021-March/567334.html
On 3/25/21, Jason Merrill wrote:
> On 3/1/21 8:12 AM, Jeff Chapman wrote:
>> On 1/18/21, Jason Merrill wrote:
>>> On 1/4/21 9:58 AM, Jeff Chapman wrote:
Ping. re:
On Fri, Apr 30, 2021 at 12:11 PM Patrick Palka via Libstdc++
wrote:
>
> + template
> + _Tp&
> + _M_emplace_deref(const _Iter& __i)
> + {
> + this->reset();
> + return this->emplace(*__i);
> + }
This incurs a move, avoiding of which is the
ere is no need to spill:
[hjl@gnu-cfl-2 pieces]$ cat spill1.i
extern void *ops1;
extern void *ops2;
extern void bar (void);
void
foo (void)
{
__builtin_memcpy (ops1, ops2, 32);
bar ();
__builtin_memcpy (ops1, ops2, 32);
}
[hjl@gnu-cfl-2 pieces]$ make spill1.s
/export/build/gnu/tools-build/gcc-g
On Thu, 29 Apr 2021, Segher Boessenkool wrote:
> > > > gcc/
> > > > 2021-04-29 Michael Meissner
> > > >
> > > > PR bootstrap/100327
> > > > * config/rs6000/rs6000.c
> > > > (TARGET_LIBGCC_FLOATING_MODE_SUPPORTED_P): Define.
> > >
> > > I don't see this used anywhere
On 30/04/21 11:07 -0400, Patrick Palka via Libstdc++ wrote:
Tested on x86_64-pc-linux-gnu, committed as "obvious".
Thanks. OK for 11 and 10 too.
libstdc++-v3/ChangeLog:
* include/std/ranges (split_view::_InnerIter::operator++):
Depend on _Base instead of _Vp directly, as per
On 30/04/21 10:38 -0400, Patrick Palka via Libstdc++ wrote:
This implements the wording changes of "join_view should join all views
of ranges".
Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
OK, thanks.
libstdc++-v3/ChangeLog:
* include/std/ranges
Jonathan Wright writes:
> Updated the patch to implement suggestions - restricting these tests to run on
> only aarch64 targets.
>
> Tested and all new tests pass on aarch64-none-linux-gnu.
>
> Ok for master?
OK, thanks.
Richard
> Thanks,
> Jonathan
>
Updated the patch to implement suggestions - restricting these tests to run on
only aarch64 targets.
Tested and all new tests pass on aarch64-none-linux-gnu.
Ok for master?
Thanks,
Jonathan
From: Richard Sandiford
Sent: 28 April 2021 16:46
To: Jonathan Wright
Jonathan Wright writes:
> Updated the patch to be more consistent with the others in the series.
>
> Tested and bootstrapped on aarch64-none-linux-gnu - no issues.
>
> Ok for master?
OK, thanks.
Richard
>
> Thanks,
> Jonathan
>
Updated the patch to be more consistent with the others in the series.
Tested and bootstrapped on aarch64-none-linux-gnu - no issues.
Ok for master?
Thanks,
Jonathan
From: Gcc-patches on behalf of Jonathan
Wright via Gcc-patches
Sent: 28 April 2021 15:42
To:
On 4/29/2021 3:50 AM, Jiufu Guo via Gcc-patches wrote:
When there is the possibility that overflow may happen on the loop index,
a few optimizations would not happen. For example code:
foo (int *a, int *b, unsigned k, unsigned n)
{
while (++k != n)
a[k] = b[k] + 1;
}
For this code,
I may just do that :).
Thanks.
Aldy
On Fri, Apr 30, 2021 at 6:10 PM Jeff Law wrote:
>
>
> On 4/28/2021 11:12 AM, Aldy Hernandez wrote:
> > This refactors the registry and the profitability code from the
> > backwards threader into two separate classes. It cleans up the code,
> > and makes it
>> For a moment, for the sake of this question, if we establish that CTF/BTF
>> generation always feeds off DWARF DIEs (so there is no need to access
>> type/decl tree nodes), what will it take to keep LTO support while keeping
>> ctf_debug_finalize in dwarf2out_finish ?
>
> I don't think it's
On 4/28/2021 11:12 AM, Aldy Hernandez wrote:
This refactors the registry and the profitability code from the
backwards threader into two separate classes. It cleans up the code,
and makes it easier for alternate implementations to share code.
Tested on x86-64 Linux.
gcc/ChangeLog:
"H.J. Lu via Gcc-patches" writes:
> On Fri, Apr 30, 2021 at 5:49 AM H.J. Lu wrote:
>>
>> On Fri, Apr 30, 2021 at 5:42 AM Richard Sandiford
>> wrote:
>> >
>> > "H.J. Lu via Gcc-patches" writes:
>> > > On Fri, Apr 30, 2021 at 2:06 AM Richard Sandiford
>> > > wrote:
>> > >>
>> > >> "H.J. Lu via
On 4/28/2021 11:12 AM, Aldy Hernandez wrote:
This is an overall refactor of the jump threader, both for the low level
bits in tree-ssa-threadupdate.* and the high level bits in
tree-ssa-threadedge.*.
There should be no functional changes.
Some of the benefits of the refactor are:
a)
Jonathan Wright writes:
> Patch updated as per suggestion (similar to patch 10/20.)
>
> Tested and bootstrapped on aarch64-none-linux-gnu - no issues.
>
> Ok for master?
OK, thanks.
Richard
> Thanks,
> Jonathan
> ---
>
Jonathan Wright writes:
> Patch updated as per your suggestion.
>
> Tested and bootstrapped on aarch64-none-linux-gnu - no issues.
>
> Ok for master?
OK, thanks.
Richard
> Thanks,
> Jonathan
> ---
> From: Richard
Jonathan Wright writes:
> Thanks for the review, I've updated the patch as per option 1.
>
> Tested and bootstrapped on aarch64-none-linux-gnu with no issues.
>
> Ok for master?
OK, thanks,
Richard
> Thanks,
> Jonathan
>
Hi
As discussed on irc with Tobias…
(I’ve included the changes to configure in this case since
they are the only changes in the patch)
bootstrapped on x86-64-linux-gnu
pushed to releases/gcc-9.
thanks
Iain
==
It appears that at some point the configure file has been
regenerated with
Hi,
This is a backport to GCC-10 to fix PR97205, patch applies
cleanly on the branch.
Regression tested and found no issues.
Ok for GCC-10 backport?
Regards,
Srinath.
This makes sure that stack allocated SSA_NAMEs are
at least MODE_ALIGNED. Also increase the MEM_ALIGN
for the
On 4/28/2021 6:51 PM, Martin Sebor via Gcc-patches wrote:
When the compute_objsize_r() function sees a pointer whose target
it can't determine it sets the size of the pointed to object to
the maximum but it doesn't clear the base0 flag to indicate that
the offset need not be zero-based. This
On 4/27/2021 7:01 PM, Tom Tromey wrote:
This patch completes the transition of libcc1 from the use of separate
template functions for different arities to the use of variadic
functions. This is how I had wanted it to work from the very
beginning, and is possible now with C++11.
I had thought
On 4/27/2021 7:01 PM, Tom Tromey wrote:
Both the C and C++ side of the GDB plugin in libcc1 share a lot of
code relating to the base GCC interface. It was all copy-and-pasted,
but is essentially identical between the two. This is by design, as
the base GCC API is intended to be shared.
This
Tested on x86_64-pc-linux-gnu, committed as "obvious".
libstdc++-v3/ChangeLog:
* include/std/ranges (split_view::_InnerIter::operator++):
Depend on _Base instead of _Vp directly, as per LWG 3532.
---
libstdc++-v3/include/std/ranges | 2 +-
1 file changed, 1 insertion(+), 1
Patch updated as per suggestion (similar to patch 10/20.)
Tested and bootstrapped on aarch64-none-linux-gnu - no issues.
Ok for master?
Thanks,
Jonathan
From: Richard Sandiford
Sent: 28 April 2021 16:37
To: Jonathan Wright via Gcc-patches
Cc: Jonathan Wright
On 4/27/2021 7:01 PM, Tom Tromey wrote:
The two GDB plugins in libcc1 share a fair amount of code. This was
done by copy-and-paste, though in reality the underlying code is
nearly identical.
libcc1/ChangeLog
2021-04-27 Tom Tromey
* libcp1.cc (struct libcp1): Derive from
This is another small step towards avoiding the problems described in PR
60497, by using std::addressof to avoid ADL, so that we don't require
all template arguments to be complete.
libstdc++-v3/ChangeLog:
PR libstdc++/60497
* include/bits/basic_ios.tcc (basic_ios::copyfmt): use
On 4/28/2021 10:26 PM, Alexandre Oliva wrote:
On Feb 22, 2021, Richard Biener wrote:
On Fri, Feb 19, 2021 at 9:08 AM Alexandre Oliva wrote:
Here's an improved version of the patch. Regstrapped on
x86_64-linux-gnu, with and without a patchlet that moved multi-pieces
ahead of setmem, and
This implements the wording changes of "join_view should join all views
of ranges".
Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
libstdc++-v3/ChangeLog:
* include/std/ranges (__detail::__non_propating_cache): Define
as per P2328.
(join_view): Remove
Patch updated as per your suggestion.
Tested and bootstrapped on aarch64-none-linux-gnu - no issues.
Ok for master?
Thanks,
Jonathan
From: Richard Sandiford
Sent: 28 April 2021 16:11
To: Jonathan Wright via Gcc-patches
Cc: Jonathan Wright
Subject: Re: [PATCH
Thanks for the review, I've updated the patch as per option 1.
Tested and bootstrapped on aarch64-none-linux-gnu with no issues.
Ok for master?
Thanks,
Jonathan
From: Richard Sandiford
Sent: 28 April 2021 15:11
To: Jonathan Wright via Gcc-patches
Cc: Jonathan
ping?
On Wed, 21 Apr 2021 at 22:48, Christophe Lyon
wrote:
>
> The acle/saturation.c test uses __[su]sat() and
> __saturation_occurred() intrinsics but __[su]sat() are defined in
> acle.h if __ARM_FEATURE_SAT true, while __saturation_occurred()
> depends on __ARM_FEATURE_QBIT.
>
> QBIT is a v5te
ping?
On Thu, 22 Apr 2021 at 09:01, Christophe Lyon
wrote:
>
> arm.h has had this error message since 1997, and was never updated to
> take softfp into account. Anyway, it seems it was useful long ago, but
> it is no longer needed since option parsing has been improved:
> -mfloat-abi is handled
ping?
On Thu, 22 Apr 2021 at 15:32, Christophe Lyon
wrote:
>
> The test requires an FPU, so use -march=armv7-a+fp -mfpu=auto instead
> of -march=armv7-a.
>
> We also remove dg-require-effective-target arm_fp_ok, but keep
> dg-add-options arm_fp: this enables the test to pass on arm-eabi
>
This patch enables MVE vld4/vst4 instructions for auto-vectorization.
We move the existing expanders from neon.md and enable them for MVE,
calling the respective emitter.
2021-03-12 Christophe Lyon
gcc/
* config/arm/neon.md (vec_load_lanesxi)
(vec_store_lanexoi): Move
This patch enables MVE vld2/vst2 instructions for auto-vectorization.
We move the existing expanders from neon.md and enable them for MVE,
calling the respective emitter.
2021-03-12 Christophe Lyon
gcc/
* config/arm/neon.md (vec_load_lanesoi)
(vec_store_lanesoi): Move
Since MVE has a different set of vector comparison operators from
Neon, we have to update the expansion to take into account the new
ones, for instance 'NE' for which MVE does not require to use 'EQ'
with the inverted condition.
Conversely, Neon supports comparisons with #0, MVE does not.
For:
This patch adds __fp16 support to the previous patch that added vcmp
support with MVE. For this we update existing expanders to use VDQWH
iterator, and add a new expander vcond. In the
process we need to create suitable iterators, and update v_cmp_result
as needed.
2021-04-26 Christophe Lyon
This patch brings more unification in the vector comparison builtins,
by removing the useless 's' (signed) suffix since we no longer need
unsigned versions.
2021-03-01 Christophe Lyon
gcc/
* config/arm/arm_mve.h (__arm_vcmp*): Remove 's' suffix.
*
Like in the previous, we factorize the vcmp_*f* patterns to make
maintenance easier.
2021-03-12 Christophe Lyon
gcc/
* config/arm/iterators.md (MVE_FP_COMPARISONS): New.
* config/arm/mve.md (mve_vcmpq_f)
(mve_vcmpq_n_f): New, merge all vcmp_*f*
After removing the signed and unsigned suffixes in the previous
patches, we can now factorize the vcmp* patterns: there is no longer
an asymmetry where operators do not have the same set of signed and
unsigned variants.
The will make maintenance easier.
MVE has a different set of vector
After the previous patch, we no longer need to emit the unsigned
variants of vcmpneq/vcmpeqq. This patch removes them as well as the
corresponding iterator entries.
2021-03-01 Christophe Lyon
gcc/
* config/arm/arm_mve_builtins.def (vcmpneq_u): Remove.
(vcmpneq_n_u):
There is no need to have a signed and an unsigned version of these
builtins. This is similar to what we do for Neon in arm_neon.h.
This mechanical patch enables later cleanup patches.
2021-03-01 Christophe Lyon
gcc/
* config/arm/arm_mve.h (__arm_vcmpeq*u*, __arm_vcmpne*u*):
This patch adds a test for the scalar mode of vadd, precisely noting
that we do not yet use the T2 variants of vadd, which take a scalar as
final argument.
2021-04-22 Christophe Lyon
gcc/testsuite/
* gcc.target/arm/simd/mve-vadd-scalar-1: New.
---
Support for vmul has been present for a while, but it was lacking a
test for the scalar variant.
This patch adds one, precisely noting that we do not yet use the T2
variants of vmul, which take a scalar as final argument.
2021-04-22 Christophe Lyon
gcc/testsuite/
*
This patchs adds a test similar to mve-vsub_1.c, but operates on a
scalar as second argument. For the moment we do not select the T2 vsub
variant operating on a scalar final argument, and we use vadd of the
opposite.
2021-04-26 Christophe Lyon
gcc/testsuite/
*
This implements the resolution of LWG 1203 so that the constraints for
rvalue stream insertion/extraction are simpler, and the return type is
the original rvalue stream type not its base class.
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
* include/std/istream
This makes the uses of getsockopt and setsockopt in
conditional on the availability of .
It also fixes a test to check for instead of .
libstdc++-v3/ChangeLog:
PR libstdc++/100285
* include/experimental/socket (__basic_socket_impl::set_option)
Define a new effective-target keyword so that tests for the Networking
TS header can be skipped on targets where none
of it can be usefully defined.
libstdc++-v3/ChangeLog:
PR libstdc++/100180
PR libstdc++/100286
PR libstdc++/100351
*
On Fri, Apr 30, 2021 at 5:49 AM H.J. Lu wrote:
>
> On Fri, Apr 30, 2021 at 5:42 AM Richard Sandiford
> wrote:
> >
> > "H.J. Lu via Gcc-patches" writes:
> > > On Fri, Apr 30, 2021 at 2:06 AM Richard Sandiford
> > > wrote:
> > >>
> > >> "H.J. Lu via Gcc-patches" writes:
> > >> > gen_reg_rtx
On Fri, Apr 23, 2021 at 05:24:00PM -0400, Jason Merrill via Gcc wrote:
> On Fri, Apr 23, 2021 at 7:55 AM Jakub Jelinek wrote:
> >
> > Status
> > ==
> >
> > GCC 8.5 release and closing of the 8 branch is several months overdue,
> > we don't have enough time to maintain trunk and 4 supported
gcc/ChangeLog:
* config/csky/csky.c (ck810_legitimate_index_p): Modified for
support "base + index" with DF mode.
* config/csky/constraints.md ("Y"): New constraint for memory operands
without index register.
* config/csky/csky_insn_fpuv2.md
gcc/ChangeLog:
* config/csky/csky.c (TARGET_PROMOTE_PROTOTYPES): Use default.
---
gcc/config/csky/csky.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/gcc/config/csky/csky.c b/gcc/config/csky/csky.c
index 67cdf9c..e4c92fe 100644
--- a/gcc/config/csky/csky.c
+++
gcc/ChangeLog:
* config/csky/csky.md (untyped_call): Emit clobber for return
registers to mark them used.
---
gcc/config/csky/csky.md | 4
1 file changed, 4 insertions(+)
diff --git a/gcc/config/csky/csky.md b/gcc/config/csky/csky.md
index b980d4c..f91d851 100644
---
gcc/ChangeLog:
* config/csky/csky.c (csky_can_change_mode_class): Delete.
For csky, HF/SF mode use the low bits of VREGS.
---
gcc/config/csky/csky.c | 16
1 file changed, 16 deletions(-)
diff --git a/gcc/config/csky/csky.c b/gcc/config/csky/csky.c
index
gcc/testsuite/ChangeLog:
* gcc/testsuite/gcc.target/csky/fpuv3/fpuv3.exp: New.
* gcc/testsuite/gcc.target/csky/fpuv3/fpv3_div.c: New.
* gcc/testsuite/gcc.target/csky/fpuv3/fpv3_fadd.c: New.
* gcc/testsuite/gcc.target/csky/fpuv3/fpv3_fdtos.c: New.
*
gcc/ChangeLog:
config/csky/csky.md (cskyv2_sextend_ldbs): New insn.
---
gcc/config/csky/csky.md | 10 ++
1 file changed, 10 insertions(+)
diff --git a/gcc/config/csky/csky.md b/gcc/config/csky/csky.md
index c27d627..b980d4c 100644
--- a/gcc/config/csky/csky.md
+++
gcc/ChangeLog:
* config/csky/csky.h
(FRAME_POINTER_REGNUM): Use HARD_FRAME_POINTER_REGNUM and
FRAME_POINTER_REGNUM instead of the signle definition. The
signle definition may not work well at simplify_subreg_regno().
(ELIMINABLE_REGS): Add for
gcc/ChangeLog:
* config/csky/csky.c (csky_option_override):
Init csky_arch_isa_features[] advanced, so TARGET_DSP
and TARGET_DIV can be set well.
---
gcc/config/csky/csky.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git
gcc/ChangeLog:
* config/csky/constraints.md ("l", "h"): Delete.
* config/csky/csky.h (reg_class, REG_CLASS_NAMES,
REG_CLASS_CONTENTS): Delete LO_REGS and HI_REGS.
* config/csky/csky.c (regno_reg_classm,
csky_secondary_reload, csky_register_move_cost):
Wilco Dijkstra via Gcc-patches writes:
> Hi Richard,
>> Hmm, OK. I guess it makes things more consistent in that sense
>> (PIC vs. non-PIC). But on the other side it's making things less
>> internally consistent for non-PIC, since we don't use the GOT for
>> anything else there. I guess in
On Fri, Apr 30, 2021 at 5:42 AM Richard Sandiford
wrote:
>
> "H.J. Lu via Gcc-patches" writes:
> > On Fri, Apr 30, 2021 at 2:06 AM Richard Sandiford
> > wrote:
> >>
> >> "H.J. Lu via Gcc-patches" writes:
> >> > gen_reg_rtx tracks stack alignment needed for pseudo registers so that
> >> >
"H.J. Lu via Gcc-patches" writes:
> On Fri, Apr 30, 2021 at 2:06 AM Richard Sandiford
> wrote:
>>
>> "H.J. Lu via Gcc-patches" writes:
>> > gen_reg_rtx tracks stack alignment needed for pseudo registers so that
>> > associated hard registers can be properly spilled onto stack. But there
>> >
On 4/27/21 10:32 AM, Bill Schmidt wrote:
The design of the target-specific built-in function support in the
Power back end has not stood the test of time. The machinery is
grossly inefficient, confusing, and arcane; and adding new built-in
functions is inefficient and error-prone. This patch
On 4/27/21 10:32 AM, Bill Schmidt wrote:
The design of the target-specific built-in function support in the
Power back end has not stood the test of time. The machinery is
grossly inefficient, confusing, and arcane; and adding new built-in
functions is inefficient and error-prone. This patch
gcc/ChangeLog:
* config/csky/constraints.md ("W"): New constriant for mem operand
with base reg, index register.
("Q"): Renamed and modified "csky_valid_fpuv2_mem_operand" to
"csky_valid_mem_constraint_operand" to deal with both "Q" and "W"
constraint.
This adds another testcase for PR95719.
Tested on x86_64-unknown-linux-gnu, pushed.
2021-04-30 Richard Biener
PR c++/98032
* g++.dg/pr98032.C: New testcase.
---
gcc/testsuite/g++.dg/pr98032.C | 20
1 file changed, 20 insertions(+)
create mode 100644
Hi Richard,
> Hmm, OK. I guess it makes things more consistent in that sense
> (PIC vs. non-PIC). But on the other side it's making things less
> internally consistent for non-PIC, since we don't use the GOT for
> anything else there. I guess in principle there's a danger that a
> custom *-elf
On Fri, Apr 30, 2021 at 2:06 AM Richard Sandiford
wrote:
>
> "H.J. Lu via Gcc-patches" writes:
> > gen_reg_rtx tracks stack alignment needed for pseudo registers so that
> > associated hard registers can be properly spilled onto stack. But there
> > are cases where associated hard registers
Status
==
It's time for the GCC 9.4 release, I therefore plan to do a GCC 9.4
release candidate on May 19th and the release about a week after
that if no unforseen problems arise.
We have one P1 regression, PR98032 which is a C++ frontend issue.
Please make sure to backport regression fixes
David Edelsohn via Gcc-patches writes:
> -fdata-sections places data symbols into their own, unique, named
> sections.
> -fsection-anchors create an anchor to access neighboring symbols
> within a section.
>
> When both are enabled, a separate section anchor is created for each
>
This adds a testcase for a bug that was fixed with the
hybrid SLP detection rewrite.
Tested on x86_64-unknown-linux-gnu, pushed.
2021-04-30 Richard Biener
PR tree-optimization/96513
* gcc.dg/torture/pr96513.c: New testcase.
---
gcc/testsuite/gcc.dg/torture/pr96513.c | 26
1 - 100 of 114 matches
Mail list logo
