In the edge case of a coroutine not containing any locals, the ifcd/switch
temporaries would get added to the coroutine frame, corrupting its
layout. To prevent this, we can make sure there is always a BIND_EXPR at
the top of the function body, and thus, always a place for our new
temporaries to go
Hi Segher,
on 2023/3/9 22:55, Segher Boessenkool wrote:
> Hi!
>
> On Thu, Mar 09, 2023 at 05:30:53PM +0800, Kewen.Lin wrote:
>> on 2023/3/9 07:01, Peter Bergner via Gcc-patches wrote:
>>> PR109073 shows a problem where GCC 11 and GCC 10 do not accept a const
>>> __vector_pair pointer operand to s
On 3/12/2023 1:48 AM, Jeff Law wrote:
On 1/6/23 01:31, anothername27-unity--- via Gcc-patches wrote:
From: Himal
Hi,
This might be a better fix.
Regards.
PS. I had to use a different email.
---
libiberty/unlink-if-ordinary.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/li
On Mon, 2023-03-13 at 12:58 +0800, Lulu Cheng wrote:
>
> 在 2023/3/13 下午12:54, Xi Ruoyao 写道:
> > On Mon, 2023-03-13 at 12:40 +0800, WANG Xuerui wrote:
> > > This is ugly. The fact all current LA32 models don't support CRC
> > > ops is
> > > just a coincidence; it's entirely possible for a future pr
在 2023/3/13 下午12:54, Xi Ruoyao 写道:
On Mon, 2023-03-13 at 12:40 +0800, WANG Xuerui wrote:
This is ugly. The fact all current LA32 models don't support CRC ops is
just a coincidence; it's entirely possible for a future product
iteration to introduce such functionality. It's not like the CRC*.W.W
On Mon, 2023-03-13 at 12:40 +0800, WANG Xuerui wrote:
> This is ugly. The fact all current LA32 models don't support CRC ops is
> just a coincidence; it's entirely possible for a future product
> iteration to introduce such functionality. It's not like the CRC*.W.W.W
> ops require anything wider
On 2023/3/13 11:52, Lulu Cheng wrote:
LoongArch 32-bit instruction set does not support crc* and crcc* instructions.
gcc/ChangeLog:
* config/loongarch/larchintrin.h (__crc_w_b_w): Add macros for control.
(__crc_w_h_w): Likewise.
(__crc_w_w_w): Likewise.
(__crcc
On Mon, 2023-03-13 at 11:52 +0800, Lulu Cheng wrote:
> diff --git a/gcc/config/loongarch/larchintrin.h
> b/gcc/config/loongarch/larchintrin.h
> index e571ed27b37..09f9a5db846 100644
> --- a/gcc/config/loongarch/larchintrin.h
> +++ b/gcc/config/loongarch/larchintrin.h
> @@ -145,6 +145,7 @@ __asrtgt_
LoongArch 32-bit instruction set does not support crc* and crcc* instructions.
gcc/ChangeLog:
* config/loongarch/larchintrin.h (__crc_w_b_w): Add macros for control.
(__crc_w_h_w): Likewise.
(__crc_w_w_w): Likewise.
(__crcc_w_b_w): Likewise.
(__crcc_w_h_w):
Kindly reminder for this PR. Thank you all in advance.
Pan
-Original Message-
From: Li, Pan2
Sent: Wednesday, March 8, 2023 7:31 PM
To: gcc-patches@gcc.gnu.org
Cc: juzhe.zh...@rivai.ai; kito.ch...@sifive.com
Subject: RE: [PATCH] RISC-V: Bugfix for rvv bool mode size adjustment
Completed
Because GO_IF_LEGITIMATE_ADDRESS was deprecated a long time ago
(see commit c6c3dba931548987c78719180e30ebc863404b89).
gcc/ChangeLog:
* config/xtensa/xtensa.h (REG_OK_STRICT, REG_OK_FOR_INDEX_P,
REG_OK_FOR_BASE_P): Remove.
---
gcc/config/xtensa/xtensa.h | 11 +--
1 file c
On 3/2/23 17:03, Qing Zhao via Gcc-patches wrote:
Ping.
It looks to me like there is an associated code patch (for PR101832)
that is still under technical discussion? Or is this documentation
patch independent of that change?
-Sandra
Gerald Pfeifer writes:
> Note that in HTML < and > have a special meaning, so we cannot simply
> write "<* noreturn *>", but need to escape it as "<* noreturn *>".
>
> Pushed.
>
> Gerald
apologies and thanks for correcting this bug
regards,
Gaius
On Sun, 12 Mar 2023 at 18:46, Sandra Loosemore wrote:
>
> On 3/10/23 16:08, Jonny Grant wrote:
> > docs: update copyright year in libstdc++ manual
> >
> > gcc/ChangeLog
> > * libstdc++-v3/doc/xml/faq.xml: update copyright year in
> > libstdc++ manual
>
> This change looks trivial
On 3/12/23 01:12, Bernhard Reutner-Fischer via Gcc-patches wrote:
On 12 March 2023 03:47:08 CET, Sean Bright via Gcc-patches
wrote:
On 3/11/2023 6:39 PM, Bernhard Reutner-Fischer wrote:
On 11 March 2023 18:33:46 CET, Sean Bright via Gcc-patches
wrote:
Hi,
This fixes a minor issue where th
On 3/10/23 16:08, Jonny Grant wrote:
docs: update copyright year in libstdc++ manual
gcc/ChangeLog
* libstdc++-v3/doc/xml/faq.xml: update copyright year in libstdc++
manual
This change looks trivial enough, but IIUC the corresponding HTML file
also needs to be regenerated w
On 3/12/23 11:40, Tobias Burnus wrote:
Hi Sandra,
can you check the PR number? The following looks wrong:
https://gcc.gnu.org/PR88578>>
On 11.03.23 02:33, Sandra Loosemore wrote:
--- a/gcc/doc/install.texi2html
+++ b/gcc/doc/install.texi2html
...
- # Use sed to work around makeinfo 4.7 b
This is no longer used since 0a62889c7a155f8ed971860d68870dc9c46bb004, so
let's clean it up.
gcc/ChangeLog:
* system.h: Drop unused INCLUDE_PTHREAD_H.
Signed-off-by: Sam James
---
gcc/system.h | 4
1 file changed, 4 deletions(-)
diff --git a/gcc/system.h b/gcc/system.h
index cf45d
On 3/12/23 09:04, Roger Sayle wrote:
This patch fixes a P1 regression, a problem with my February 2022 patch
to improve folding for final value replacement:
https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590618.html
The motivation for the original patch is that because we know the n
On 3/11/23 18:54, Jonathan Yong wrote:
On 3/11/23 17:29, Jeff Law wrote:
On 2/14/23 03:42, Jonathan Yong via Gcc-patches wrote:
Attached patches OK?
0002-gcc-testsuite-gcc.dg-fix-pic-test-case-for-PE-target.patch
From 616e43ac41879040e73a266065874148553cddcc Mon Sep 17 00:00:00 2001
Fro
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Swedish team of translators. The file is available at:
https://translationproject.org/latest/gcc/sv.po
(This file, 'gcc-13.1-b20230212.sv.po'
This patch fixes a P1 regression, a problem with my February 2022 patch
to improve folding for final value replacement:
https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590618.html
The motivation for the original patch is that because we know the number
of loop iterations can't be negative
Gerald Pfeifer writes:
> On Sat, 11 Mar 2023, Arsen Arsenović wrote:
>> Sandra Loosemore writes:
>>> Hmmm, first off, I think somebody other than me needs to approve the
>>> configure and makefile pieces, as well as the maintainer-scripts part.
>>> It looks conceptually right to me
>
> Per gc
On Sat, 11 Mar 2023, Arsen Arsenović wrote:
> Sandra Loosemore writes:
>> Hmmm, first off, I think somebody other than me needs to approve the
>> configure and makefile pieces, as well as the maintainer-scripts part.
>> It looks conceptually right to me
Per gcc/MAINTAINERS that'd be
build ma
With this there should be only one or two problem links left in all of the
libstdc++ docs. :-)
Pushed.
Gerald
libstdc++-v3/ChangeLog:
* doc/xml/manual/documentation_hacking.xml: Move www.graphviz.org
to https.
* doc/html/manual/documentation_hacking.html: Regenerate.
-
Hi Jonathan,
On Tue, 27 Jul 2021, Jonathan Wakely via Gcc-patches wrote:
> Firstly, these bullet points are full sentences and so should end with
> a period (or smiley, in some cases).
>
> Secondly, releases are not issued by the GNU Project at all, they're
> issued by the GCC release managers.
>
On 12 March 2023 03:47:08 CET, Sean Bright via Gcc-patches
wrote:
>On 3/11/2023 6:39 PM, Bernhard Reutner-Fischer wrote:
>> On 11 March 2023 18:33:46 CET, Sean Bright via Gcc-patches
>> wrote:
>>> Hi,
>>>
>>> This fixes a minor issue where the zero-length-bound docs read "See See
>>> Zero Lengt
27 matches
Mail list logo
