On Sun, May 1, 2022 at 2:15 PM Aldy Hernandez via Gcc-patches
wrote:
>
> We are ICEing in set_range_info_raw because value_range_kind cannot be
> VR_VARYING, since SSA_NAME_RANGE_TYPE can only hold VR_RANGE /
> VR_ANTI_RANGE. Most of the time setting a VR_VARYING as a global
> range makes no sens
> @@ -385,7 +395,11 @@ gcov_read_bytes (void *buffer, unsigned count)
>
>unsigned read = fread (buffer, count, 1, gcov_var.file);
>if (read != 1)
> -return NULL;
> +{
> + if (feof (gcov_var.file))
> + gcov_var.error = GCOV_FILE_EOF;
> + return NULL;
> +}
Hello.
On Sat, Apr 30, 2022 at 1:26 AM Bernhard Reutner-Fischer
wrote:
>
> On Fri, 29 Apr 2022 20:03:55 +0200
> Thomas Koenig wrote:
>
> > On 28.04.22 19:17, Bernhard Reutner-Fischer wrote:
> > > ISTM that this should be s/mod.e/mode./ ?
> >
> > Yep, fixed as obvious and simple on trunk with
> > r13-49-
On Fri, Apr 29, 2022 at 6:22 PM Aldy Hernandez wrote:
>
> On Fri, Apr 29, 2022 at 12:13 PM Richard Biener
> wrote:
> >
> > On Fri, Apr 29, 2022 at 11:53 AM Aldy Hernandez wrote:
> > >
> > > On Fri, Apr 29, 2022 at 9:09 AM Richard Biener
> > > wrote:
> > > >
> > > > On Thu, Apr 28, 2022 at 8:44
On Sun, May 01, 2022 at 07:06:53PM +0100, Jonathan Wakely wrote:
> > >> the reason is that "gcc/analyzer/region-model.cc” uses
> > >> initializer_lists, and it seems that
> > >> is not transitively included by any used headers for _LIBCPP_VERSION <
> > >> 4000. I fixed that locally by
> > >> ad
On Sun, May 01, 2022 at 08:09:05PM +0100, Jonathan Wakely via Gcc-patches wrote:
> On Sun, 1 May 2022 at 19:22, Patrick Palka via Libstdc++
> wrote:
> >
> > The hexfloat parser for binary32/64 added in r12-6645-gcc3bf3404e4b1c
> > overlooked that the exponent part can also begin with an uppercase
Mitigates the following clang warning:
libgcc/libgcov-driver.c:416:1: warning: unused function 'dump_string'
[-Wunused-function]
libgcc/ChangeLog:
* libgcov-driver.c: Add ATTRIBUTE_UNUSED.
---
libgcc/libgcov-driver.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libgcc/libgcov-dri
Ack, I am OoO during 5/1-5/4, I'll start looking at those patches in
the GCC 13 queue including this one :)
On Fri, Apr 29, 2022 at 6:12 AM Philipp Tomsich
wrote:
>
> Kito,
>
> Did you have a chance to take a look at this one?
>
> I assume this will have to wait until we reopen for 13...
> OK for
On Sun, 1 May 2022 at 19:22, Patrick Palka via Libstdc++
wrote:
>
> The hexfloat parser for binary32/64 added in r12-6645-gcc3bf3404e4b1c
> overlooked that the exponent part can also begin with an uppercase 'P'.
>
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk/11, and possibly
> the
On Sun, 1 May 2022 at 19:21, Patrick Palka via Libstdc++
wrote:
>
> As in r12-6281-gc83ecfbe74a5cf for std::isdigit, shouldn't
> use std::tolower either I think.
>
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk/11 and the
> 12 branch after it's thawed?
OK, thanks.
>
> PR l
As in r12-6281-gc83ecfbe74a5cf for std::isdigit, shouldn't
use std::tolower either I think.
Tested on x86_64-pc-linux-gnu, does this look OK for trunk/11 and the
12 branch after it's thawed?
PR libstdc++/103911
libstdc++-v3/ChangeLog:
* src/c++17/floating_from_chars.cc (find_en
The hexfloat parser for binary32/64 added in r12-6645-gcc3bf3404e4b1c
overlooked that the exponent part can also begin with an uppercase 'P'.
Tested on x86_64-pc-linux-gnu, does this look OK for trunk/11, and possibly the
12 branch now for 12.1?
PR libstdc++/105441
libstdc++-v3/ChangeLog
On Tue, Feb 8, 2022 at 7:05 PM H.J. Lu via Gcc-patches
wrote:
>
> On Tue, Feb 8, 2022 at 6:38 PM Hongtao Liu wrote:
> >
> > On Fri, Jan 28, 2022 at 5:53 AM H.J. Lu via Gcc-patches
> > wrote:
> > >
> > > The v3 patch was posted at
> > >
> > > https://gcc.gnu.org/pipermail/gcc-patches/2021-July/57
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-12.1-b20220403.sv.po'
Pinging this again. This time with i386 port maintainers in CC.
Summary: The macro guards for TARGET_CAN_SPLIT_STACK on i386 are not
aligned with the implementation of ix86_supports_split_stack. That is,
on systems using musl libc ix86_supports_split_stack errors-out (since
-fsplit-stack is not su
We are ICEing in set_range_info_raw because value_range_kind cannot be
VR_VARYING, since SSA_NAME_RANGE_TYPE can only hold VR_RANGE /
VR_ANTI_RANGE. Most of the time setting a VR_VARYING as a global
range makes no sense. However, we can have a range spanning the
entire domain (VR_RANGE of [MIN,MA
Hi,
I just pushed the attached patch to update the mail links and dates for
GCC 12 and GCC 13, as simple and obvious.
Regards
Thomasdiff --git a/htdocs/index.html b/htdocs/index.html
index 199181b1..e1bb584e 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -172,7 +172,7 @@ Mor
17 matches
Mail list logo
