On 2/15/23 01:39, Martin Liška wrote:
gcc/ChangeLog:
* doc/invoke.texi: Document --param=asan-kernel-mem-intrinsic-prefix.
I noticed this new text was missing Texinfo markup, so I've committed
the attached followup patch.
I also wonder why this thing and several of the other asan th
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 Length."
>>
>> gcc/ChangeLog:
>> * doc/invoke.texi (Warning Options): Remove
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
From: Jonathan Yong<10wa...@gmail.com>
Date: T
On 2/4/23 13:33, Roger Sayle wrote:
This patch (primarily) documents the VEC_PERM_EXPR tree code in
generic.texi. For ease of review, it is provided below as a pair
of diffs. The first contains just the new text added to describe
VEC_PERM_EXPR, the second tidies up this part of the documentati
The reason would be to show that they continue to not ICE as they used to.
No go paths are just as useful as go paths.
On Sat, Mar 11, 2023, 10:57 Jeff Law wrote:
>
>
> On 2/16/23 01:16, Eric Botcazou via Gcc-patches wrote:
> >> This fixes dg.exp/stack-check-2.c, -7, 8, and -16.c, which is great
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 Length."
>
>gcc/ChangeLog:
> * doc/invoke.texi (Warning Options): Remove errant 'See'
> before @xref.
>---
> gcc/doc/invoke.texi | 2 +-
> 1
This aspect I missed in my previous change.
Easy enough to fix. Pushed.
Gerald
---
htdocs/testing/testing-ftensor.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/testing/testing-ftensor.html
b/htdocs/testing/testing-ftensor.html
index 7b1f4675..1f9de177 100644
-
Pushed.
Gerald
gcc/ChangeLog:
* doc/extend.texi (Named Address Spaces): Drop a redundant link
to AVR-LibC.
---
gcc/doc/extend.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index e0c5357291b..fd3745c5608 100644
On Sat, Mar 11, 2023 at 12:32 PM Andrew Pinski wrote:
>
> On Sat, Mar 11, 2023 at 12:27 PM Sam James via Gcc-patches
> wrote:
> >
> > This fixes errors like:
> > ```
> > In file included from /usr/include/pthread.h:30,
> > from
> > /usr/lib/gcc/riscv64-gentoo-linux-musl/12/inclu
This flag allows us to restore old (pre-6.8) behavior of the
@{summary,}content commands, so that texi2any continues to emit
summarycontents first.
maintainer-scripts/ChangeLog:
* update_web_docs_git: Set CONTENTS_OUTPUT_LOCATION=inline in
order to put @shortcontents above content
On Sat, Mar 11, 2023 at 12:27 PM Sam James via Gcc-patches
wrote:
>
> This fixes errors like:
> ```
> In file included from /usr/include/pthread.h:30,
> from
> /usr/lib/gcc/riscv64-gentoo-linux-musl/12/include/g++-v12/riscv64-gentoo-linux-musl/bits/gthr-default.h:35,
>
This fixes errors like:
```
In file included from /usr/include/pthread.h:30,
from
/usr/lib/gcc/riscv64-gentoo-linux-musl/12/include/g++-v12/riscv64-gentoo-linux-musl/bits/gthr-default.h:35,
from
/usr/lib/gcc/riscv64-gentoo-linux-musl/12/include/g++-v12/riscv64-ge
I looked at this older release notes "by chance" and notice some minor
editorial changes.
Pushed (but let me know if you disagree with any of these).
Gerald
---
htdocs/gcc-10/changes.html | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/htdocs/gcc-10/changes.html b/
Gerald Pfeifer writes:
> On Sat, 11 Mar 2023, Arsen Arsenović wrote:
>> OK, changed up a bit, what do you think of this:
>
>> maintainer-scripts/ChangeLog:
>>
>> * update_web_docs_git: Set CONTENTS_OUTPUT_LOCATION=inline in
>> order to put @shortcontents above contents. See
>> 9dd
This fixes errors like:
```
In file included from /usr/include/pthread.h:30,
from
/usr/lib/gcc/riscv64-gentoo-linux-musl/12/include/g++-v12/riscv64-gentoo-linux-musl/bits/gthr-default.h:35,
from
/usr/lib/gcc/riscv64-gentoo-linux-musl/12/include/g++-v12/riscv64-ge
Sandra Loosemore writes:
> On 3/11/23 05:22, Arsen Arsenović wrote:
>> OK, changed up a bit, what do you think of this:
>> maintainer-scripts/ChangeLog:
>> * update_web_docs_git: Set CONTENTS_OUTPUT_LOCATION=inline in
>> order to put @shortcontents above contents. See
>> 9dd976a4-
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/libiberty/unlink-if-ordinary.c b/libiber
On 3/1/23 06:07, Richard Biener via Gcc-patches wrote:
When combining -g1 with -flto we run into the DIE location annotation
machinery for globals calling dwarf2out_late_global_decl but not
having any early generated DIE for function scope statics. In
this process we'd generate a limbo DIE si
On Fri, 10 Mar 2023, Sandra Loosemore wrote:
> I've checked in the attached patch per discussion in another thread about
> possibly updating the minimum required Texinfo version.
Thank you, Sandra!
I was going to udpate the comment in doc/install.texi2html just now, and
saw you beat me to it (an
On 3/11/23 05:22, Arsen Arsenović wrote:
OK, changed up a bit, what do you think of this:
maintainer-scripts/ChangeLog:
* update_web_docs_git: Set CONTENTS_OUTPUT_LOCATION=inline in
order to put @shortcontents above contents. See
9dd976a4-4e09-d901-b949-6d5037567...@cod
On Sat, 11 Mar 2023, Arsen Arsenović wrote:
> OK, changed up a bit, what do you think of this:
> maintainer-scripts/ChangeLog:
>
> * update_web_docs_git: Set CONTENTS_OUTPUT_LOCATION=inline in
> order to put @shortcontents above contents. See
> 9dd976a4-4e09-d901-b949-6d5037567..
Hi,
This fixes a minor issue where the zero-length-bound docs read "See See
Zero Length."
gcc/ChangeLog:
* doc/invoke.texi (Warning Options): Remove errant 'See'
before @xref.
---
gcc/doc/invoke.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/invoke.texi
On 3/9/23 16:27, Lewis Hyatt via Gcc-patches wrote:
On Fri, Nov 04, 2022 at 10:03:13AM +0100, Jakub Jelinek via Gcc-patches wrote:
Hi!
The following pseudo-patch (for uname2c.h part
just a pseudo patch with a lot of changes replaced with ...
because it is too large but the important changes
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
From: Jonathan Yong<10wa...@gmail.com>
Date: Tue, 14 Feb 2023 10:37:03 +
Sub
On 1/14/23 11:46, Lewis Hyatt via Gcc-patches wrote:
get__Pragma_string() in directives.cc is responsible for lexing the parens
and the string argument from a _Pragma("...") operator. This function does
not handle the case when the closing paren is not on the same line as the
string; in that c
On 3/1/23 04:35, Khem Raj via Gcc-patches wrote:
Currently, if the gcc toolchain is relocated and installed from shared state
cache, then you try and compile
preprocessed source (.i or .ii files), the compiler will try and access the
builtin sysroot location
rather than the --sysroot option
On 1/5/23 06:05, Yoshinori Sato wrote:
Subject:
[PATCH] PR target/89828 Inernal compiler error on -fno-omit-frame-pointer
From:
Yoshinori Sato
Date:
1/5/23, 06:05
To:
gcc-patches@gcc.gnu.org
CC:
Yoshinori Sato
The problem was caused by an erroneous note about creating a stack frame,
which
On 3/1/23 05:54, Jonny Grant wrote:
Hello
I don't have write access, could someone review and apply this please?
Done. Edited the ChangeLog a bit and pushed to the trunk.
Thanks,
jeff
On 1/10/23 21:20, Takayuki 'January June' Suwa via Gcc-patches wrote:
Currently, cond_move_process_if_block() does the conversion without
balancing the cost of the converted sequence with the original one, but
this should be checked by calling targetm.noce_conversion_profitable_p().
Doing so
On 1/24/23 05:24, Cupertino Miranda wrote:
Thank you for the comments and suggestions.
I have changed the patch.
Unfortunately in case of rx target I could not make
scan-assembler-symbol-section to match. I believe it is because the
.section and .global entries order is reversed in this targe
On 1/17/23 05:00, Martin Liška wrote:
When opening files, preserve CR characters. By default, open
accepts universal newlines, but I think we should only split with '\n'.
Ready to be installed?
Thanks,
Martin
contrib/ChangeLog:
* update-copyright.py: Split lines only with '\n'.
OK.
On 2/28/23 00:23, Jonathan Yong via Gcc-patches wrote:
On 2/28/23 02:10, Hans-Peter Nilsson wrote:
On Sun, 26 Feb 2023, Jonathan Yong via Gcc-patches wrote:
Patch OK for master branch? I did not see any obvious issues to
exclude LLP64
specifically.
I see "lp64 || lp64" in that patch (whi
On 2/27/23 06:58, Richard Biener via Gcc-patches wrote:
After fixing PR107561 the following avoids looking at VR_ANTI_RANGE
ranges where it doesn't seem obvious the code does the correct
thing here (lower_bound and upper_bound do not work as expected).
Bootstrapped and tested on x86_64-unknow
On 3/7/23 04:08, Richard Biener via Gcc-patches wrote:
The following addresses PR109046 by adding an optimization to forwprop
to combine a piecewise complex load to a complex load when there are
no uses of the components. That's something useful in general and
easier to do than avoiding the s
On 2/16/23 01:16, Eric Botcazou via Gcc-patches wrote:
This fixes dg.exp/stack-check-2.c, -7, 8, and -16.c, which is great!
Try the attached patch.
I'd suggest going ahead and applying the fix to
check_effective_target_supports_stack_clash_protection.
There's really not a strong reason to
On 2/28/23 09:42, Maciej W. Rozycki wrote:
On Mon, 13 Feb 2023, Jeff Law via Gcc-patches wrote:
3. The canaonical conditional-zero-or-value assumes the target can do a
generic SEQ/SNE of two register values. As you know, on RISC-V we have
SEQZ/SNEZ. So we've added another fallback path to
On 2/20/23 19:39, Xin Liu wrote:
From: Matthew Fortune
---
gcc/testsuite/gcc.target/mips/mips.exp | 1 +
1 file changed, 1 insertion(+)
Unfortunately, you haven't given anyone any background that would allow
them to evaluate/review this patch.
I'm guessing that MSA does not support mic
On 2/24/23 00:28, Vít Kabele wrote:
Hello,
I changed the tested pattern to match even on targets with different
alignment.
So this needs to wait for stage1 development to open -- we're in
regression bugfixing phase only right now. I would expect that to
happen in April/May.
You might con
On 3/1/23 05:32, Jakub Jelinek via Gcc-patches wrote:
Hi!
On Wed, Nov 16, 2022 at 12:51:14PM +0100, Jakub Jelinek via Gcc-patches wrote:
On Wed, Nov 16, 2022 at 10:06:17AM +0100, Jakub Jelinek via Gcc-patches wrote:
Thoughts on this? I guess my preference would be the BF -> SF -> TI
path b
Dear all,
I've committed the attached patch to mainline as obvious after
regtesting on x86_64-pc-linux-gnu.
https://gcc.gnu.org/g:2cf5f485e0351bb1faf46196a99e524688f3966e
commit r13-6605-g2cf5f485e0351bb1faf46196a99e524688f3966e
Author: Harald Anlauf
Date: Sat Mar 11 15:37:37 2023 +0100
Sandra Loosemore writes:
> On 3/9/23 13:38, Arsen Arsenović wrote:
>> Found the change. HTML got support for CONTENTS_OUTPUT_LOCATION,
>> which defaults to after_top, which ignores the inline location of
>> these elements. Here's a patch:
>> maintainer-scripts/ChangeLog:
>> * update_web_d
Hi Sir
How are you?
I need a post on your website https://www.gnu.org/
1 Article with permanent 2 do-follow with link
Google indexed
Normal price?
Casino price?
Vape Price
Link Insertion Price?
Please send me your best post price my email id
I am waiting for your positive response
Thanks
On Fri, Mar 10, 2023 at 7:11 PM Ian Lance Taylor wrote:
>
> Jakub Jelinek writes:
>
> > On Wed, Mar 01, 2023 at 01:32:43PM +0100, Jakub Jelinek via Gcc-patches
> > wrote:
> >> On Wed, Nov 16, 2022 at 12:51:14PM +0100, Jakub Jelinek via Gcc-patches
> >> wrote:
> >> > On Wed, Nov 16, 2022 at 10:0
Hi Richard,
Since this appeared only in gcc13, I see no need for a backport.
I will also document this in the changes file.
The „problem“
It's a real problem, I am afraid...
is latent forever, I’m not sure it’s good to amend the kitchen-sink >std=legacy
option with -fwrapv since that has q
44 matches
Mail list logo
