On Mon, Apr 19, 2021 at 9:40 PM Michael Meissner via Fortran
wrote:
>
> Fix Fortran rounding issues, PR fortran/96983.
>
> I was looking at Fortran PR 96983, which fails on the PowerPC when trying to
> run the test PR96711.F90. The compiler ICEs because the PowerPC does not have
> a floating poin
This implements the wording changes of P2259R1 "Repairing input range
adaptors and counted_iterator", which resolves LWG 3283, 3289 and 3408.
The wording changes are relatively straightforward, but they require
some boilerplate to implement: the changes to make a type alias
"conditionally present"
Hi,
This patch adjusts the `read_encoded_value_with_base' function in
libphobos to correctly handle unaligned loads. Instead of unsafe
pointer dereferencing, use memcpy() to read encoded values from memory.
The function `read_encoded_value' has been updated to accept a ref
parameter, this simplif
> On Apr 19, 2021, at 7:26 PM, Martin Sebor via Gcc-patches
> wrote:
>
> On 4/19/21 3:13 PM, Koning, Paul wrote:
>>> On Apr 19, 2021, at 4:50 PM, Martin Sebor via Gcc-patches
>>> wrote:
>>>
>>> ...
>>> I was actually thinking of just #including each foo-tests.c file
>>> to bring in the cod
On 4/19/21 3:13 PM, Koning, Paul wrote:
On Apr 19, 2021, at 4:50 PM, Martin Sebor via Gcc-patches
wrote:
On 4/19/21 2:03 PM, David Malcolm wrote:
On Mon, 2021-04-19 at 13:47 -0600, Martin Sebor via Gcc-patches wrote:
The selftests at the end of many source files are only rarely read
or mo
On 4/19/21 5:17 PM, Marek Polacek wrote:
This is an ICE-on-invalid, but I keep seeing it when reducing code so
I'd like to fix it. We crash on
template void forward() {
concept C = true;
}
which breaks two requirements:
[temp.concept]/1: A concept is a template ...
[temp.concept]/3
On 4/16/21 6:58 PM, Patrick Palka wrote:
When pretty printing a function pointer type via
pp_cxx_parameter_declaration_clause, we end up always printing an empty
parameter list because the loop that's supposed to print the parameter
list iterates over 'args' instead of 'types', and 'args' is empt
This is an ICE-on-invalid, but I keep seeing it when reducing code so
I'd like to fix it. We crash on
template void forward() {
concept C = true;
}
which breaks two requirements:
[temp.concept]/1: A concept is a template ...
[temp.concept]/3: A concept-definition shall inhabit a namespa
> On Apr 19, 2021, at 4:50 PM, Martin Sebor via Gcc-patches
> wrote:
>
> On 4/19/21 2:03 PM, David Malcolm wrote:
>> On Mon, 2021-04-19 at 13:47 -0600, Martin Sebor via Gcc-patches wrote:
>>> The selftests at the end of many source files are only rarely read
>>> or modified, but they contribu
On 4/19/21 2:03 PM, David Malcolm wrote:
On Mon, 2021-04-19 at 13:47 -0600, Martin Sebor via Gcc-patches wrote:
The selftests at the end of many source files are only rarely read
or modified, but they contribute to the size/complexity of the files
and make moving within the rest of the code more
> On 19/04/2021 19:50 Iain Buclaw wrote:
>
>
> Hi,
>
> This patch fixes an ICE that occurred in the D front-end diagnostic
> handlers. The percentage character was being confused for a format
> specifier in pp_format(), whilst the backtick character was confused for
> the beginning of a quote
On 19/04/21 20:55 +0100, Jonathan Wakely wrote:
On 19/04/21 12:33 -0400, Richard Kenner wrote:
I don't see why we should have to "comply with the GNU style" if we're
truly an independent project run by the GCC developers and aided by
the steering committee.
I think it critical than any code ha
On Mon, 2021-04-19 at 13:47 -0600, Martin Sebor via Gcc-patches wrote:
> The selftests at the end of many source files are only rarely read
> or modified, but they contribute to the size/complexity of the files
> and make moving within the rest of the code more difficult.
>
FWIW I prefer having t
On 19/04/21 12:33 -0400, Richard Kenner wrote:
I don't see why we should have to "comply with the GNU style" if we're
truly an independent project run by the GCC developers and aided by
the steering committee.
I think it critical than any code have *some* style guidelines. If you
don't like th
Ping the patch for a logic error in setting up 32-bit trampolines.
| Subject: [PATCH] Fix logic error in 32-bit trampolines, PR target/98952
| Message-ID: <20210409210907.ga5...@ibm-toto.the-meissners.org>
| User-Agent: Mutt/1.5.21 (2010-09-15)
https://gcc.gnu.org/pipermail/gcc-patches/2021-April/
The selftests at the end of many source files are only rarely read
or modified, but they contribute to the size/complexity of the files
and make moving within the rest of the code more difficult.
Would anyone be opposed to moving any of them into new files of their
own? E.g., those in tree.c to t
This patch gives clean guality.exp test results for aarch64-linux-gnu
with modern (top-of-tree) gdb.
For people using older gdbs, it will trade one set of noisy results for
another set. I still think it's better to have the xfails based on
one “clean” and “modern” run rather than have FAILs and X
This patch adds target selectors of the form:
{ any-opts "opt1" ... "optn" }
{ no-opts "opt1" ... "optn" }
for skipping or xfailing tests based on compiler options. It only
works for dg-final selectors.
The patch then uses no-opts to exclude -O0 and (sometimes) -Og from
some guality.exp xfa
From: Thomas Rodgers
This patch address jwakely's feedback from 2021-04-15.
This is a substantial rewrite of the atomic wait/notify (and timed wait
counterparts) implementation.
The previous __platform_wait looped on EINTR however this behavior is
not required by the standard. A new _GLIBCXX_HA
Fix Fortran rounding issues, PR fortran/96983.
I was looking at Fortran PR 96983, which fails on the PowerPC when trying to
run the test PR96711.F90. The compiler ICEs because the PowerPC does not have
a floating point type with a type precision of 128. The reason is that the
PowerPC has 3 diffe
On 4/19/21 4:18 AM, Richard Biener wrote:
On Sun, Apr 18, 2021 at 4:40 AM Andrew MacLeod via Gcc-patches
wrote:
I also disable the logical cache since it isn't really doing anything
any more.
OK for trunk?
Please make
+#define LOGICAL_LIMIT 6
a --param (params.opt, documented in invok
On Sun, Apr 18, 2021 at 12:03:39PM -0500, Segher Boessenkool wrote:
> On Sun, Apr 18, 2021 at 05:24:50PM +0200, Jakub Jelinek wrote:
> > On Sun, Apr 18, 2021 at 03:03:07PM +, Segher Boessenkool wrote:
> > > If the register named in an existing REG_UNUSED note dies somewhere
> > > between where
Hi,
This patch fixes an ICE that occurred in the D front-end diagnostic
handlers. The percentage character was being confused for a format
specifier in pp_format(), whilst the backtick character was confused for
the beginning of a quoted string in expand_d_format().
Both are now properly escaped
Hi,
This patch fixes the section support code for libphobos on OpenBSD, this
is enough to get the library built, and most tests will pass now.
Testsuite hasn't been confirmed to pass cleanly just yet, so support for
libphobos on OpenBSD is still considered experimental.
Bootstrapped and regressi
Hi,
This patch fixes the thread support when building libphobos on Darwin,
this is enough to get the library built, and most tests to pass on a
fairly modern platform.
Testsuite hasn't been confirmed to pass cleanly on as broad a targets as
I'd like, so support is still very much experimental.
B
Hi,
This patch fixes libphobos support when building on MinGW, this is
enough to get the library built, and most tests to pass.
Testsuite haven't been confirmed to pass cleanly, so support is still
very much experimental.
Bootstrapped and regression tested on x86_64-linux-gnu/-m32/-mx32, as
well
Hi,
This patch merges the D runtime library with upstream druntime 89f870b7,
and phobos e6907ff3e. Synchronizes the C bindings with the latest port
fixes in upstream druntime, and adds a Config.stderrPassThrough enum
member to std.process (fixing PR98494).
Bootstrapped and regression tested on x
This commit adds a new testsuite for the CTF debug format.
2021-04-14 Indu Bhagat
David Faust
gcc/testsuite/
* lib/gcc-dg.exp (gcc-dg-frontend-supports-ctf): New procedure.
(gcc-dg-debug-runtest): Add -gctf support.
* gcc.dg/debug/btf/btf-1.c: New test.
This commit documents the new command line options introduced by the
CTF and BTF debug formats.
2021-04-14 Indu Bhagat
* doc/invoke.texi: Document the CTF and BTF debug info options.
---
gcc/doc/invoke.texi | 20
1 file changed, 20 insertions(+)
diff --git a/gcc/
This patch changes the BPF GCC backend in order to use the DWARF debug
hooks and therefore enables the user to generate BTF debugging
information with -gbtf. Generating BTF is crucial when compiling BPF
programs, since the CO-RE (compile-once, run-everwhere) mechanism
used by the kernel BPF loader
Move some functionality into a procedure of its own. This is only so that when
the patch for ctf comes along, the gcc-dg-debug-runtest procedure looks bit
more uniform.
gcc/testsuite/ChangeLog:
* lib/gcc-dg.exp (gcc-dg-target-supports-debug-format): New procedure.
---
gcc/testsuite/lib/g
This patch introduces a dwarf_debuginfo_p predicate that abstracts and
replaces complex checks on write_symbols.
2021-04-14 Indu Bhagat
gcc/ChangeLog
* flags.h (dwarf_debuginfo_p): New function declaration.
* opts.c (dwarf_debuginfo_p): New function definition.
* confi
This patch introduces a dwarf2int.h header, to be used by code that
needs access to the internal DIE structures and their attributes.
The following functions which were previously defined as static in
dwarf2out.c are now non-static, and extern prototypes for them have
been added to dwarf2int.h:
-
[Changes from V6:
- Rebased to today's master.
- A GC related regression introduced in V5 has been fixed. This
regression also uncovered a related bug that has been also fixed in
this version. Basically ctfc_types and ctfc_vars were being
incorrectly collected and this was uncovered by the f
> I don't see why we should have to "comply with the GNU style" if we're
> truly an independent project run by the GCC developers and aided by
> the steering committee.
I think it critical than any code have *some* style guidelines. If you
don't like the GNU coding convention, which do you propos
On 4/19/21 3:40 AM, Jakub Jelinek wrote:
On Sun, Apr 18, 2021 at 08:11:21PM -0400, Andrew MacLeod via Gcc-patches wrote:
--- a/gcc/gimple-range-gori.cc
+++ b/gcc/gimple-range-gori.cc
@@ -29,6 +29,36 @@ along with GCC; see the file COPYING3. If not see
#include "gimple-pretty-print.h"
#inclu
From: Richard Earnshaw
This is a partial revert of r11-8168. The overall purpose of the
commit is retained (to fix a bogus warning when -mfpu= is
used in combination with eg -mcpu=neoverse-v1), but it removes the
hunk that changed the subsequent feature bits for features of a
simd/fp unit that
On Mon, 19 Apr 2021 at 12:40, Tobias Burnus wrote:
>
> On 19.04.21 11:25, Tobias Burnus wrote:
> > On 19.04.21 10:48, Christophe Lyon wrote:
> >> The new test generates an ICE on aarch64-linux-gnu in the gcc-10 branch:
> > Looks as someone (like me) should backport https://gcc.gnu.org/97880 /
> >
David Malcolm writes:
> On Tue, 2021-04-13 at 10:52 +0100, Gaius Mulley wrote:
>>
>> Hello David and fellow GCC developers,
>>
>> [the proposed patches for GCC trunk are at the end of the email]
>>
Firstly many thanks for your excellent feedback. Initially I thought
I'd post the latest version
Hi Paul,
On 19.04.21 14:40, Paul Richard Thomas via Gcc-patches wrote:
I was just about to announce that I will only do backports and regressions,
while I finally attack the fundamental problem with the representation of
Parameterized Derived Types. Then this PR came up that was such clear low
h
On Fri, Apr 16, 2021 at 08:48:12PM +0200, Jakub Jelinek via Gcc-patches wrote:
> Tested on powerpc64{,le}-linux now (-m32/-m64 on be) and while the first
> patch works fine, the second one unfortunately doesn't on either be or le,
> so more work is needed there. Thus, I'm withdrawing the second
>
This removes pedantic_non_lvalue_loc which doesn't do what it says
since quite some time in favor of what it actually does and where
that's not a duplicate (protected_set_expr_location_unshare).
Bootstrap & regtest running on x86_64-unknown-linux-gnu, queued for stage1
2021-04-19 Richard Biener
Hi All,
I was just about to announce that I will only do backports and regressions,
while I finally attack the fundamental problem with the representation of
Parameterized Derived Types. Then this PR came up that was such clear low
hanging fruit that I decided to fix it right away.
Regtests on FC
Hi!
On 2021-04-19T10:29:17+0200, Thomas Schwinge wrote:
> On 2020-11-15T09:14:32+0100, Tobias Burnus wrote:
>> regarding the new option:
>>
>> +fopenacc-kernels=
>> +C ObjC C++ ObjC++ RejectNegative Joined Enum(openacc_kernels)
>> Var(flag_openacc_kernels) Init(OPENACC_KERNELS_PARLOOPS)
>> +-fo
On Mon, Apr 19, 2021 at 01:16:13PM +0200, Christophe Lyon via Gcc-patches wrote:
> > > Here is an updated patch that I've also successfully
> > > bootstrapped/regtested
> > > on aarch64-linux.
> > >
> > > 2021-04-16 Jakub Jelinek
> > >
> > > PR target/100075
> > > * config/aarch64/a
Hi,
(Chung-Lin, question for you buried below.)
On Thu, 15 Apr 2021 19:26:54 +0200
Thomas Schwinge wrote:
> Hi!
>
> On 2021-02-26T04:34:50-0800, Julian Brown
> wrote:
> > This patch
>
> Thanks, Julian, for your continued improving of these changes!
You're welcome!
> This has iterated thr
On Fri, 16 Apr 2021 at 13:29, Richard Sandiford via Gcc-patches
wrote:
>
> Jakub Jelinek writes:
> > On Thu, Apr 15, 2021 at 08:51:03PM +0200, Jakub Jelinek via Gcc-patches
> > wrote:
> >> Fixed, thanks for catching that (and the "r" -> "=r"; I've
> >> actually tested a patch that didn't have an
Hi!
On 2021-04-18T23:53:01+0100, Andrew Stubbs wrote:
> On 16/04/2021 18:30, Thomas Schwinge wrote:
>> On 2021-04-16T17:05:24+0100, Andrew Stubbs wrote:
>>> On 15/04/2021 18:26, Thomas Schwinge wrote:
> and optimisation, since shared memory might be faster than
> the main memory on a GPU
On 19.04.21 11:25, Tobias Burnus wrote:
On 19.04.21 10:48, Christophe Lyon wrote:
The new test generates an ICE on aarch64-linux-gnu in the gcc-10 branch:
Looks as someone (like me) should backport https://gcc.gnu.org/97880 /
r11-5489 to GCC 10.
("OpenACC: Fix integer-type issue with collapse/
On Mon, Apr 19, 2021 at 11:26:04AM +0200, Richard Biener wrote:
> This reverts a s/column_offset/column/ change in the fix for PR99446.
>
> This time with testcase included in the patch and the necessary reversion
> of the testsuite change of the offending rev.
>
> Bootstrapped and tested on x86_
On 18/04/21 10:06 -0700, H.J. Lu wrote:
On Fri, Apr 16, 2021 at 9:25 AM Jakub Jelinek via Gcc-patches
wrote:
Hi!
As we have only one P1 left right now, I think it is the right time
to update abi list files in libstdc++.
Attached are two patches, one is update for x86_64/i?86/s390x/ppc64
linu
Some of the CMSE tests have 'dg-do run', but qemu-arm does not support
the privileged instructions involved; one has to use qemu-system-arm
for this, which in turn requires modifications to the default
newlib/libgloss startup code to enable the FPU as the FP status
registers need to be saved when u
This reverts a s/column_offset/column/ change in the fix for PR99446.
This time with testcase included in the patch and the necessary reversion
of the testsuite change of the offending rev.
Bootstrapped and tested on x86_64-unknown-linux-gnu, OK?
Thanks,
Richard.
2021-04-19 Richard Biener
On 19.04.21 10:48, Christophe Lyon wrote:
The new test generates an ICE on aarch64-linux-gnu in the gcc-10 branch:
Looks as someone (like me) should backport https://gcc.gnu.org/97880 /
r11-5489 to GCC 10.
/gcc/testsuite/c-c++-common/goacc/collapse-2.c: In function 'f5._omp_fn.0':
/gcc/testsui
Pushed as obvious.
Martin
gcc/ChangeLog:
PR c/100143
* gengtype.c (finish_root_table): Align function arguments
in between declaration and definition.
---
gcc/gengtype.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/gengtype.c b/gcc/gengtype
switch_to_section warns if we try to output a retain decl in a
section without a retain flag, or if we try to output a non-retain
decl in a section with a retain flag. However, the warning only
applied if we were trying to “switch” to the current section.
This works if all decls that use a section
Hi,
On Fri, 9 Apr 2021 at 18:44, Hafiz Abid Qadeer wrote:
>
> Thanks for the review. Please see my comments below.
>
> On 09/04/2021 13:48, Tobias Burnus wrote:
> > Hi Abid,
> >
> > I think that's the same issue as https://gcc.gnu.org/PR98088
> > if so, please add 'PR middle-end/98088' to the c
Hi!
Would still like to get the following "cleanup" into GCC 11:
On 2020-11-15T09:14:32+0100, Tobias Burnus wrote:
> regarding the new option:
>
> +fopenacc-kernels=
> +C ObjC C++ ObjC++ RejectNegative Joined Enum(openacc_kernels)
> Var(flag_openacc_kernels) Init(OPENACC_KERNELS_PARLOOPS)
> +-f
Since GCC 8, the -freorder-blocks-and-partition pass can split a function into
hot and cold parts, thus generating 2 FDEs for a single function in DWARF for
exception purposes and doing an equivalent trick for Windows SEH on x86-64.
Now the Windows system unwinder does not support arbitrarily la
On Sun, Apr 18, 2021 at 4:40 AM Andrew MacLeod via Gcc-patches
wrote:
>
> The code presented at the time wrestrict was invoking ranger has a basic
> block with about 7200 statements, all of them calculations which fed
> into 2614 logical ORs and 1480 logical ANDs.
>
> the GORI component which calc
This reverts a s/column_offset/column/ change in the fix for PR99446.
Boostrapped on x86_64-unknown-linux-gnu, testing in progress.
OK for trunk?
Thanks,
Richard.
2021-04-19 Richard Biener
PR preprocessor/100142
libcpp/
* line-map.c (linemap_position_for_loc_and_offset): Rev
On Sun, Apr 18, 2021 at 08:11:21PM -0400, Andrew MacLeod via Gcc-patches wrote:
> --- a/gcc/gimple-range-gori.cc
> +++ b/gcc/gimple-range-gori.cc
> @@ -29,6 +29,36 @@ along with GCC; see the file COPYING3. If not see
> #include "gimple-pretty-print.h"
> #include "gimple-range.h"
>
> +// Limit
62 matches
Mail list logo
