This adds support for preserving the content of parameter registers to
the stack and emit CFI for it. This useful for applications which want
to implement their own stack unwinding and need access to function
arguments without having to rely on debug information.
With the -mpreserve-args option GP
This patch introduces a new reg note which can be used to tell the CFI
verification in dwarf2cfi that a register is stored without intending
to restore from it.
This is useful when storing e.g. register contents to the stack and
generate CFI for it although the register is not really supposed to b
This adds support for preserving the content of parameter registers to
the stack and emit CFI for it. This useful for applications which want
to implement their own stack unwinding and need access to function
arguments without having to rely on debug information.
With the -mpreserve-args option GP
With this patch a scheduling barrier is created to prevent the insn
setting up the frame-pointer and instructions which save GPRs to the
stack to be swapped. Otherwise broken CFI information would be
generated since the stack save insns would use a base register which
is not currently declared as
On Tue, Jan 31, 2023 at 11:38:59PM -0800, Fangrui Song via Gcc-patches wrote:
> Follow aarch64 and riscv ports by using (global ? DW_EH_PE_indirect : 0)
> | DW_EH_PE_pcrel for -fno-pic code. This avoids a canonical PLT entry
> for a personality reference in .eh_frame and a copy relocation for a
>
On Wed, Feb 01, 2023 at 10:01:36AM +0100, Jakub Jelinek via Gcc-patches wrote:
> And, while I can understand the rationale for global cases
> (though am not sure I agree, as currently the user can choose
> by using -mno-direct-extern-access or not using it, the above change
> disallows the choice),
On Thu, 12 Jan 2023 at 21:21, Richard Sandiford
wrote:
>
> Prathamesh Kulkarni writes:
> > On Tue, 6 Dec 2022 at 07:01, Prathamesh Kulkarni
> > wrote:
> >>
> >> On Mon, 5 Dec 2022 at 16:50, Richard Sandiford
> >> wrote:
> >> >
> >> > Richard Sandiford via Gcc-patches writes:
> >> > > Prathames
Hi!
While potential_constant_expression_1 handled most of OMP_* codes (by saying
that
they aren't potential constant expressions), OMP_SCOPE was missing in that list.
I've also added OMP_SCAN, though that is less important (similarly to
OMP_SECTION
it ought to appear solely inside of OMP_{FOR,SI
I have noticed that the "length" "8" attribute is missing in a few
patterns in mve.md.
gcc/
* config/arm/mve.md (mve_vabavq_p_): Add length
attribute.
(mve_vqshluq_m_n_s): Likewise.
(mve_vshlq_m_): Likewise.
(mve_vsriq_m_n_): Likewise.
(mve_v
I have noticed some warnings when building GCC for arm-eabi:
pr-support.c:110:7: warning: variable ‘set_pac_sp’ set but not used
[-Wunused-but-set-variable]
pr-support.c:109:7: warning: variable ‘set_pac’ set but not used
[-Wunused-but-set-variable]
This small patch avoids them by defining these
A couple of tweaks to make g++.dg/gomp clean on aarch64.
Tested on aarch64-linux-gnu & pushed.
Richard
gcc/testsuite/
* g++.dg/gomp/attrs-10.C: Update warning strings for aarch64.
* g++.dg/gomp/declare-simd-8.C: Add expected warning for aarch64.
---
gcc/testsuite/g++.dg/gomp/at
find_flags_uses_in_insn used SET_SRC without first checking
for a SET. This showed up as an RTL checking failure in
g++.dg/torture/pr90994.C on aarch64.
Tested on aarch64-linux-gnu & pushed as obvious.
Richard
gcc/
* compare-elim.cc (find_flags_uses_in_insn): Guard use of SET_SRC.
---
The original page is gone, and search engines did not reveal a new
location.
If any of you has a new location, feel free to add that (or let me
know and I'll take care).
Gerald
---
htdocs/readings.html | 5 -
1 file changed, 5 deletions(-)
diff --git a/htdocs/readings.html b/htdocs/readings
www.netlib.org now redirects to netlib.org.
Gerald
---
htdocs/testing/testing-lapack.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/htdocs/testing/testing-lapack.html
b/htdocs/testing/testing-lapack.html
index 6416ac3e..3262d69c 100644
--- a/htdocs/testing/testing-l
On Tue, 17 Jan 2023 at 17:24, Prathamesh Kulkarni
wrote:
>
> On Mon, 26 Dec 2022 at 09:56, Prathamesh Kulkarni
> wrote:
> >
> > On Tue, 13 Dec 2022 at 11:35, Prathamesh Kulkarni
> > wrote:
> > >
> > > On Tue, 6 Dec 2022 at 21:00, Richard Sandiford
> > > wrote:
> > > >
> > > > Prathamesh Kulkarn
Hi!
On Mon, Jan 30, 2023 at 11:07:23PM +, Richard Sandiford wrote:
> Jakub Jelinek writes:
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605965.html
> > - ABI - aarch64: Add bfloat16_t support for aarch64 (enabling it in GCC 14
> > will be harder)
>
> Sorry for the delay
Hi!
The PR78437 r7-4871 changes made combine_reaching_defs punt on
WORD_REGISTER_OPERATIONS targets if a setter of smaller than word
register has wider uses. This unfortunately breaks -fcompare-debug,
because if such a use appears only in DEBUG_INSN(s), while all other
uses aren't wider than the
On Tue, 31 Jan 2023, Qing Zhao wrote:
> GCC extension accepts the case when a struct with a flexible array member
> is embedded into another struct (possibly recursively).
> __builtin_object_size should treat such struct as flexible size per
> -fstrict-flex-arrays.
>
> PR tree-optimization/
On Wed, 1 Feb 2023, Jakub Jelinek wrote:
> Hi!
>
> The PR78437 r7-4871 changes made combine_reaching_defs punt on
> WORD_REGISTER_OPERATIONS targets if a setter of smaller than word
> register has wider uses. This unfortunately breaks -fcompare-debug,
> because if such a use appears only in DEBU
Hi!
On 2022-01-13T14:53:16+, Hafiz Abid Qadeer wrote:
> Currently we only make use of this directive when it is associated
> with an allocate statement.
These changes (or a variant thereof; haven't checked)
are present on devel/omp/gcc-12 branch as
commit 491478d12b83e102f72858e8a871a25c951d
Hi Thomas,
On 01.02.23 12:59, Thomas Schwinge wrote:
+ ! Don't do this (..., but it does pass the checks).
+ !$omp allocate (var1) allocator(10_omp_allocator_handle_kind) ! { dg-bogus
"Expected integer expression of the 'omp_allocator_handle_kind' kind" }
+ allocate (var1(x))
+
+ ! Assumtio
From: Ju-Zhe Zhong
Hi, this patch is present for GCC 14 since I understand it's not appropriate
to land it in GCC 13.
NUM_FIXED_BLOCKS = 2 since GCC define each function has aleast 2 blocks
one is entry block, the other is exit block.
So according this code, the function will not do cprop optimi
On Wed, 1 Feb 2023, juzhe.zh...@rivai.ai wrote:
> From: Ju-Zhe Zhong
>
> Hi, this patch is present for GCC 14 since I understand it's not appropriate
> to land it in GCC 13.
>
> NUM_FIXED_BLOCKS = 2 since GCC define each function has aleast 2 blocks
> one is entry block, the other is exit block
I don't known whether CSE do the job. What I saw is CPROP do the optimization
when we have more than 1 block.
This the RTL dump before CPROP:
(insn 19 18 20 4 (set (reg:VNx1DI 151)
(if_then_else:VNx1DI (unspec:VNx1BI [
(const_vector:VNx1BI repeat [
On Wed, 1 Feb 2023, juzhe.zh...@rivai.ai wrote:
> I don't known whether CSE do the job. What I saw is CPROP do the
> optimization when we have more than 1 block.
>
> This the RTL dump before CPROP:
>
> (insn 19 18 20 4 (set (reg:VNx1DI 151)
> (if_then_else:VNx1DI (unspec:VNx1BI [
>
>> I see loads of UNSPECs, that might explain why some passes do something
>> and some not. That said, not sure what exactly CPROP does, the two
>> pred_broadcast insns look exactly the same so CSE should CSE them?
Yes, the "source" these 2 pred_broadcast the same. However, they have different
ps
PING^5
On 1/24/23 14:34, Martin Liška wrote:
PING^4
On 1/13/23 10:09, Martin Liška wrote:
PING^3
On 12/22/22 13:15, Martin Liška wrote:
PING^2
On 12/9/22 09:27, Martin Liška wrote:
PING^1
On 12/2/22 12:27, Martin Liška wrote:
If -w is used, warn_odr properly sets *warned = false and
so i
PING^2
On 1/24/23 14:34, Martin Liška wrote:
PING^1
On 1/10/23 16:10, Martin Liška wrote:
On 1/6/23 14:21, David Malcolm wrote:
On Fri, 2023-01-06 at 12:33 +0100, Martin Liška wrote:
Patch can bootstrap on x86_64-linux-gnu and survives regression
tests.
Thanks for the patch.
I noticed tha
On Tue, Jan 24 2023, Martin Liška wrote:
> We should not insert an empty value to the container.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
> PR ipa/108509
>
> gcc/ChangeLog:
>
> * cgraphunit.cc (walk_polymo
> On Feb 1, 2023, at 6:41 AM, Richard Biener wrote:
>
> On Tue, 31 Jan 2023, Qing Zhao wrote:
>
>> GCC extension accepts the case when a struct with a flexible array member
>> is embedded into another struct (possibly recursively).
>> __builtin_object_size should treat such struct as flexible
Hi,
On Fri, Dec 02 2022, Martin Liška wrote:
> If -w is used, warn_odr properly sets *warned = false and
> so it should be preserved when calling warn_types_mismatch.
>
> Noticed that during a LTO reduction where I used -w.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Tested cris-elf and native x86_64-pc-linux-gnu.
Ok to commit?
-8< --
For targets where the ABI mandates structure layout that has
no padding, like cris-elf, this test started failing when
introduced as an add-on to the existing 1.cc, thereby
effectively causing a regression in testsuite r
On 2/1/23 15:26, Martin Jambor wrote:
Hi,
On Fri, Dec 02 2022, Martin Liška wrote:
If -w is used, warn_odr properly sets *warned = false and
so it should be preserved when calling warn_types_mismatch.
Noticed that during a LTO reduction where I used -w.
Patch can bootstrap on x86_64-linux-gnu
Hello,
On Thu, Oct 20 2022, Richard Biener via Gcc-patches wrote:
>> Am 20.10.2022 um 14:41 schrieb Jakub Jelinek via Gcc-patches
>> :
>>
>> On Thu, Oct 20, 2022 at 12:33:28PM +, Michael Matz wrote:
>>> Hey,
>>>
On Thu, 20 Oct 2022, Thomas Schwinge wrote:
This had been done
This patch introduces an instruction pattern for conditional shift
operations (cond_{ashl|ashr|lshr}) in the GCN machine description.
Tested on GCN3 Fiji gfx803.
OK to commit?
--
PA
From e9c974670e8d37f725098eea97e22be5e2e9fd21 Mon Sep 17 00:00:00 2001
From: Paul-Antoine Arras
Date: Wed, 1 Feb
On Wed, 1 Feb 2023 at 14:38, Hans-Peter Nilsson via Libstdc++
wrote:
>
> Tested cris-elf and native x86_64-pc-linux-gnu.
> Ok to commit?
OK, thanks.
On Wed, 2023-02-01 at 10:56 +0100, Gerald Pfeifer wrote:
> The original page is gone, and search engines did not reveal a new
> location.
>
> If any of you has a new location, feel free to add that (or let me
> know and I'll take care).
FWIW the most recent version in archive.org is here:
https:
Prathamesh Kulkarni writes:
> On Thu, 12 Jan 2023 at 21:21, Richard Sandiford
> wrote:
>>
>> Prathamesh Kulkarni writes:
>> > On Tue, 6 Dec 2022 at 07:01, Prathamesh Kulkarni
>> > wrote:
>> >>
>> >> On Mon, 5 Dec 2022 at 16:50, Richard Sandiford
>> >> wrote:
>> >> >
>> >> > Richard Sandiford v
Instead of failing on first error, run all __builtin_object_size and
__builtin_dynamic_object_size tests to completion and then provide a
summary of which tests failed.
gcc/testsuite/ChangeLog:
* gcc.dg/builtin-dynamic-object-size-0.c: Move FAIL and nfail
into...
* gcc.dg/
On 2023-01-31 09:11, Qing Zhao wrote:
GCC extension accepts the case when a struct with a flexible array member
is embedded into another struct (possibly recursively).
__builtin_object_size should treat such struct as flexible size per
-fstrict-flex-arrays.
PR tree-optimization/101832
g
On 2023-01-31 09:11, Qing Zhao wrote:
Update documentation to clarify a GCC extension on structure with
flexible array member being nested in another structure.
gcc/ChangeLog:
* doc/extend.texi: Document GCC extension on a structure containing
a flexible array member to be a mem
On Wed, 1 Feb 2023 at 16:01, Jonathan Wakely wrote:
>
> On Wed, 1 Feb 2023 at 14:38, Hans-Peter Nilsson via Libstdc++
> wrote:
> >
> > Tested cris-elf and native x86_64-pc-linux-gnu.
> > Ok to commit?
>
> OK, thanks.
We could add the [[no_unique_address]] attribute to the _M_ss member,
so that it
We can reset SCEV after we fold, then SCEVs cache shouldn't have
anything in it when we go to remove ssa-names in remove_unreachable().
We were resetting it later sometimes if we were processing the array
bounds warning, so I removed that call and just always reset it now.
Bootstraps on x86_6
Hi Flávio and Thomas!
On Mon, 2023-01-30 16:44:29 +0100, Thomas Schwinge
wrote:
> On 2023-01-27T21:15:01-0500, Flávio Cruz wrote:
> > Not sure what happened, but here's the patch as an attachment. Thanks for
> > your patience.
>
> Thanks, that worked. Without any changes now pushed to master
Siddhesh,
Thanks. I will update the testing case per your change.
Qing
> On Feb 1, 2023, at 11:48 AM, Siddhesh Poyarekar wrote:
>
> On 2023-01-31 09:11, Qing Zhao wrote:
>> GCC extension accepts the case when a struct with a flexible array member
>> is embedded into another struct (possibly re
> On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar wrote:
>
> On 2023-01-31 09:11, Qing Zhao wrote:
>> Update documentation to clarify a GCC extension on structure with
>> flexible array member being nested in another structure.
>> gcc/ChangeLog:
>> * doc/extend.texi: Document GCC extensio
On 2023-02-01 13:24, Qing Zhao wrote:
On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar wrote:
On 2023-01-31 09:11, Qing Zhao wrote:
Update documentation to clarify a GCC extension on structure with
flexible array member being nested in another structure.
gcc/ChangeLog:
* doc/extend.t
> On Feb 1, 2023, at 1:57 PM, Siddhesh Poyarekar wrote:
>
> On 2023-02-01 13:24, Qing Zhao wrote:
>>> On Feb 1, 2023, at 11:55 AM, Siddhesh Poyarekar wrote:
>>>
>>> On 2023-01-31 09:11, Qing Zhao wrote:
Update documentation to clarify a GCC extension on structure with
flexible arra
Dear all,
the fix for PR108527 came with a testcase that revealed a latent
bug with array sections and invalid array declarations. The ICE
first popped up on powerpc64-linux-gnu (big endian), but the issue
was not so clear as such on x86_64-pc-linux-gnu, as it did not show
up e.g. in valgrind. T
The embedded tzdata.zi causes new build failures for small targets.
Tested x86_64-linux, built on avr and msp430-elf.
-- >8 --
The string literal containing the static tzdata.zi information is too
large for some targets, so do not enable it by default for avr-*-* and
msp430-*-*.
libstdc++-v3/Ch
Tested x86_64-linux, built on avr and msp430-elf.
This should be backported to the branches where avr fails to build
with --enable-libstdcxx due to these problems.
-- >8 --
The abr-libc does not define EOVERFLOW, which means that
std::errc::value_too_large is not defined, and so cannot be
comp
Tested x86_64-linux, built on avr and msp430-elf.
This should be backported to the affected branches.
-- >8 --
This fixes a build failure that affects avr, but could affect other
targets in theory. The _M_fini function should not try to use ::open or
::fopen if _GLIBCXX_USE_DEV_RANDOM is not def
> From: Jonathan Wakely
> Date: Wed, 1 Feb 2023 18:19:09 +0100
> On Wed, 1 Feb 2023 at 16:01, Jonathan Wakely wrote:
> >
> > On Wed, 1 Feb 2023 at 14:38, Hans-Peter Nilsson via Libstdc++
> > wrote:
> > >
> > > Tested cris-elf and native x86_64-pc-linux-gnu.
> > > Ok to commit?
> >
> > OK, thanks
Pushed.
Gerald
---
htdocs/readings.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index 6e640af1..4bad7e26 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -231,7 +231,7 @@ names.
Nios II
Manufacturer: In
On Tue, Jan 31, 2023 at 10:31:03PM -0500, Michael Meissner wrote:
> Ok, I tracked down the source of the bug. The CCP pass is depending on the
> precision field. Unfortunately in tree-core.h, the precision is a 10 integer
> bit field, so 1,024 will become 0.
>
> Having a 0 precision meant that t
What a difference a slash can make. (I'm pretty sure that same link
originally worked; someone somehow somewhen probably changed something
on the web server.)
Pushed.
Gerald
libstdc++-v3/ChangeLog:
* doc/xml/manual/debug.xml: Fix link to online GDB manual.
* doc/html/manual/de
Business as usual.
Pushed.
Gerald
---
htdocs/frontends.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/frontends.html b/htdocs/frontends.html
index 8e38838a..12af359b 100644
--- a/htdocs/frontends.html
+++ b/htdocs/frontends.html
@@ -48,7 +48,7 @@ the GCC trunk.
Pushed.
Gerald
libstdc++-v3/ChangeLog:
* doc/xml/manual/using_exceptions.xml: Update a www.open-std.org
link to https.
* doc/html/manual/using_exceptions.html: Regenerate.
---
libstdc++-v3/doc/html/manual/using_exceptions.html | 2 +-
libstdc++-v3/doc/xml/manual/using_exc
On Tue, Jan 31, 2023 at 9:27 PM David Malcolm wrote:
>
> Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
> Pushed to trunk as r13-5615-gd03ae4be2c6d48.
>
> gcc/testsuite/ChangeLog:
> * gcc.dg/analyzer/call-summaries-2.c: Add
> dg-require-effective-target alloca.
>
Normally when vf is not constant, it will be prevented by
vectorizable_nonlinear_inductions, but for this case, it failed going
into
if (STMT_VINFO_RELEVANT_P (stmt_info))
{
need_to_vectorize = true;
if (STMT_VINFO_DEF_TYPE (stmt_info) == vect_induction_def
&&
Yeah, Thanks. You are right. CSE should do the job.
Now I know the reason CSE failed to optimize is I include
VL_REGNUM(66)/VTYPE_RENUM(67) hard reg
as the dependency of pred_broadcast:
(insn 19 18 20 4 (set (reg:VNx1DI 152)
> (if_then_else:VNx1DI (unspec:VNx1BI [
> (c
This patch adds the 'Zfa' extension for riscv, which is based on:
(
https://github.com/riscv/riscv-isa-manual/commit/d74d99e22d5f68832f70982d867614e2149a3bd7
)
latest 'Zfa' change on the master branch of the RISC-V ISA Manual as
of this writing.
The Wiki Page (details):
( https://github.com/a4lg
> The above is incorrectly formatted, the GCC Coding Conventions
say || etc. shouldn't be at the end of lines, but rather at the
start of the next ones.
Ack.
> And, while I can understand the rationale for global cases
> (though am not sure I agree, as currently the user can choose
> by using -mn
contrib/ChangeLog:
* config-list.mk: Add x86_64-gnu to list of archs.
Signed-off-by: Flavio Cruz
---
contrib/config-list.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/config-list.mk b/contrib/config-list.mk
index 20b8f4a196f..661b11c9bbd 100644
--- a/cont
64 matches
Mail list logo
