I've backported several patches having to do with Fortran/C
interoperability from mainline to the OG11 branch. See attached log for
details.
-Sandra
commit d554155c07771935778f557e9ef649cc3624d1ce
Author: Sandra Loosemore
Date: Wed Aug 11 19:24:17 2021 -0700
Fortran: Fix c_float128
Hi Martin,
on 2021/8/20 上午12:30, Martin Sebor wrote:
> On 8/19/21 9:03 AM, Martin Sebor wrote:
>> On 8/18/21 11:56 PM, Kewen.Lin wrote:
>>> Hi David,
>>>
>>> on 2021/8/19 上午11:26, David Edelsohn via Gcc-patches wrote:
Hi, Martin
A few PowerPC-specific testcases started failing
On Thu, Aug 19, 2021 at 12:12 PM Harald Anlauf via Gcc-patches
wrote:
>
> Hi Tobias,
>
> > I am inclined to say that the Intel compiler has a bug by not
> > accepting it – but as written before, I regard sub-string length
> > (esp. with const expr) inquiries as an odd corner case which
> > is
On Thu, Aug 19, 2021 at 4:18 PM Roger Sayle wrote:
>
>
> Whilst working on a backend patch, I noticed that the middle-end's
> RTL optimizers weren't simplifying a truncation of a paradoxical
> subreg extension, though it does transform closely related (more
> complex) expressions. The main
On 8/13/21 12:15 PM, Bill Schmidt wrote:
> Honestly, I don't see how it matters. So far as I can tell, all you've done
> here is hand-inlined what build_simple_mem_ref would do. So I guess I have
> a slight preference for your original patch (but with the new test case,
> of course).
Ok, I
Whilst working on a backend patch, I noticed that the middle-end's
RTL optimizers weren't simplifying a truncation of a paradoxical
subreg extension, though it does transform closely related (more
complex) expressions. The main (first) part of this patch
implements this simplification, reusing
The attached patch changes the new access warning pass to use
the per-function ranger instance. To do that it makes a number
of the global static functions members of the pass (that involved
moving one to a later point in the file, increasing the diff;
the body of the function hasn't changed
This patch adds a __PTX_ISA__ predefined macro to the nvptx backend that
allows code to check the compute model being targeted by the compiler.
This is equivalent to the __CUDA_ARCH__ macro defined by CUDA's nvcc
compiler, but to avoid causing problems for source code that checks
for that
On 8/19/2021 12:24 PM, Gerald Pfeifer wrote:
On Thu, 19 Aug 2021, Jeff Law via Gcc-patches wrote:
Whee, two more ports dropping stabs. Committed to the trunk.
Are you saying you're on a mission to stab wodden stakes into stabs?
Seems that way :-) I hadn't really set out to do that, but
Hi,
This patch is on behalf of John Henning, who opened PR 101843:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101843
He proposed the following doc change, please take a look and let me know
whether this is Okay for commit?
Thanks.
Qing
>From
On Thu, Aug 19, 2021 at 06:10:46PM -0400, Michael Meissner wrote:
> On Wed, Aug 18, 2021 at 06:11:03PM -0500, Segher Boessenkool wrote:
> > I think the current vector.md / altivec.md / vsx.md / rs6000.md
> > division is artificial at best. Most of the basic (movement etc.)
> > things are in
On Wed, Aug 18, 2021 at 06:11:03PM -0500, Segher Boessenkool wrote:
> On Wed, Aug 18, 2021 at 04:42:42PM -0400, David Edelsohn wrote:
> > I wanted to give Segher a chance to comment on the structure.
>
> I think the current vector.md / altivec.md / vsx.md / rs6000.md
> division is artificial at
Hi,
I totally biffed the previous version of this patch, as it was built
against an experimental tree instead of trunk. Trying again...
Although safe_inc_pos avoids buffer overruns in rs6000-gen-builtins.c,
there are some other routines where we fail to detect the possibility.
Clean those up!
Hi!
Richard, maybe you have an opinion here, in particular about my
"SLP vectorizer" comment below? Please see
<87r1f2puss.fsf@euler.schwinge.homeip.net">http://mid.mail-archive.com/87r1f2puss.fsf@euler.schwinge.homeip.net>
for the full context.
On 2021-08-16T10:21:04+0200, Jakub Jelinek
Hi,
A while ago had a report of build failure against a Darwin branch on
the latest OS release. This was because (temporarily) the symlink
from libm.dylib => libSystem.dylib had been removed/omitted.
libm is not needed on Darwin, and should not be added unconditionally
even if that is (mostly)
Hi,
Although the cctools assembler is based of GNU GAS, it is from a
very old version (1.38) which does not support many of the features
that the target supports test is expecting***.
tested on i686 and x86_64 darwin versions using the cctools as.
OK for master?
thanks
Iain
*** I guess we
On Thu, Aug 19, 2021 at 12:53:16PM -0600, Martin Sebor wrote:
> That said, I introduced
> the variable in r243470 to begin with and I consider its removal
> a trivially correct and appropriate part of refactoring.
It is not a refactoring. It changes behaviour.
Segher
Hi!
On Thu, Aug 19, 2021 at 01:16:16PM -0500, Paul A. Clarke wrote:
> On Wed, Aug 18, 2021 at 05:46:58PM -0500, Segher Boessenkool wrote:
> > There are __builtin_set_fpscr_rn and friends, please use those, those
> > are optimised for any platform.
>
> I do. (Unless I missed an opportunity
Hi Tobias,
> I am inclined to say that the Intel compiler has a bug by not
> accepting it – but as written before, I regard sub-string length
> (esp. with const expr) inquiries as an odd corner case which
> is unlikely to occur in real-world code.
ok.
> Still does not work – or rather:
Hi,
Preface:
this is the last patch for now in my series - with this applied Darwin
reports the same results as Linux (at least, for modern x86_64
platform versions).
Note
a) that the expect expression in {fixed}host_execute seems to depend
on the assumption that the dejagnu.h output is used
On 8/19/21 9:36 AM, Segher Boessenkool wrote:
On Thu, Aug 19, 2021 at 09:03:44AM -0600, Martin Sebor via Gcc-patches wrote:
On 8/18/21 11:56 PM, Kewen.Lin wrote:
To get rid of GTY variable alloc_object_size_limit looks suspicious,
maybe tree objects returned by alloc_max_size after the change
Hi,
This concerns the settings of flags (using the host makefile fragment) for
tools that will run on the host.
At present the (no)PIE flags are computed in gcc/configure but it is not
possible to override them (either from higher level Makefile or from the
command line). Secondly the ordering
The changes in last night's patch to the new access warning pass
(somewhat prematurely) included a call to enable_ranger() with no
matching call to disable_ranger(). The two calls must be paired
in order for the latter to release resources allocated by
the former, otherwise the resources leak
Hi,
It is intended that the default for the NeXT runtime at ABI 2 is to
check for nil message receivers. This updates this to match the
documented behaviour and to match the behaviour of the system tools.
tested on x86_64, i686-darwin, x86_64-linux,
pushed to master, thanks
Iain
Signed-off-by:
On Thu, 19 Aug 2021, Jeff Law via Gcc-patches wrote:
> Whee, two more ports dropping stabs. Committed to the trunk.
Are you saying you're on a mission to stab wodden stakes into stabs?
SCNR :-)
Gerald
On 6/28/2021 1:16 AM, CHIGOT, CLEMENT wrote:
On 6/23/2021 12:53 AM, CHIGOT, CLEMENT via Gcc-patches wrote:
Hi David,
Did you have a chance to take look at this patch ?
Thanks,
Clément
+DavidMalcolm
Can you review this patch when you have a moment?
Thanks, David
On Mon, May 17, 2021
Whee, two more ports dropping stabs. Committed to the trunk.
Jeff
commit 18e9e7db7afb8635316414b560c10852db13c4c1
Author: Jeff Law
Date: Thu Aug 19 14:15:03 2021 -0400
Drop stabs from h8/300 and v850 ports
gcc/
* config.gcc (h8300-*-elf*): Do not include dbxelf.h.
On Wed, Aug 18, 2021 at 05:46:58PM -0500, Segher Boessenkool wrote:
> On Mon, Aug 09, 2021 at 03:23:50PM -0500, Paul A. Clarke wrote:
> > Suppress exceptions (when specified), by saving, manipulating, and
> > restoring the FPSCR. Similarly, save, set, and restore the floating-point
> > rounding
On 8/19/21 2:00 PM, David Malcolm wrote:
On Thu, 2021-08-19 at 11:30 -0600, Martin Sebor via Gcc-patches wrote:
Hey Aldy & Andrew,
I introduced a leak by calling enable_ranger() without pairing it
with one to disable_ranger() on the same function (PR 101984).
I didn't realize (or look to see)
On 8/9/2021 12:46 AM, Serge Belyshev wrote:
Jeff Law writes:
On 7/20/2021 9:44 AM, Serge Belyshev wrote:
Special-casing checks for in-tree gas features is unnecessary since
r17 which made configure-gcc depend on all-gas, and thus making
alternate code path in gcc_GAS_CHECK_FEATURE for
On 8/19/21 1:30 PM, Martin Sebor wrote:
Hey Aldy & Andrew,
I introduced a leak by calling enable_ranger() without pairing it
with one to disable_ranger() on the same function (PR 101984).
I didn't realize (or look to see) that enable_ranger() dynamically
allocates memory.
The patch below adds
On 8/19/2021 9:53 AM, Roger Sayle wrote:
An issue with a backend patch I've been investigating has revealed
a missed optimization opportunity during GCC's vector lowering pass.
An unrecognized insn for "(set (reg:SI) (not:SI (const_int 0))"
revealed that not only was my expander not expecting
On Thu, 2021-08-19 at 11:30 -0600, Martin Sebor via Gcc-patches wrote:
> Hey Aldy & Andrew,
>
> I introduced a leak by calling enable_ranger() without pairing it
> with one to disable_ranger() on the same function (PR 101984).
> I didn't realize (or look to see) that enable_ranger() dynamically
>
Hey Aldy & Andrew,
I introduced a leak by calling enable_ranger() without pairing it
with one to disable_ranger() on the same function (PR 101984).
I didn't realize (or look to see) that enable_ranger() dynamically
allocates memory.
The patch below adds comments to make it clear that the calls
On 7/27/21 5:07 AM, Tobias Burnus wrote:
Hi Sandra, hi Thomas, hi all,
@Thomas K: Comments about the following - and of course to the
testsuite itself - are highly welcome.
In my opinion, the testsuite LGTM and can be committed.
@Sandra:
- Thoughts on the directory name? (cf. below)
- Give
On 8/19/21 9:03 AM, Martin Sebor wrote:
On 8/18/21 11:56 PM, Kewen.Lin wrote:
Hi David,
on 2021/8/19 上午11:26, David Edelsohn via Gcc-patches wrote:
Hi, Martin
A few PowerPC-specific testcases started failing yesterday on AIX with
a strange failure mode: the compiler runs out of memory. As
On 8/17/2021 2:41 AM, Sebastian Huber wrote:
abort() is used in gcc_assert() and gcc_unreachable() which is used by target
libraries such as libgcov.a. This patch changes the abort() definition under
certain conditions. If inhibit_libc is defined and abort is not already
defined, then
On 8/19/2021 6:11 AM, Dragan Mladjenovic wrote:
Since 'Remove obsolete IRIX 6.5 support' [1] we only use
gp-relative jump-tables for PIC code. We can fall back to
default behaviour for asm_function_rodata_section.
[1] https://gcc.gnu.org/ml/libstdc++/2012-03/msg00067.html
2018-06-04 Dragan
Hi, Kewen
Good catch!
The patch is in the right direction, but gimple-ssa-warn-access.cc is
the first file that requires GTY and ends in ".cc". The GCC Makefile
machinery to create the GTY headers performs the substitution for
files with file extension ".c", so this requires more adjustment in
Doh! ENOPATCH.
-Original Message-
From: Roger Sayle
Sent: 19 August 2021 16:59
To: 'GCC Patches'
Subject: [x86_64 PATCH] Tweak -Os costs for scalar-to-vector pass.
Back in June I briefly mentioned in one of my gcc-patches posts that a
change that should have always reduced code
Back in June I briefly mentioned in one of my gcc-patches posts that
a change that should have always reduced code size, would mysteriously
occasionally result in slightly larger code (according to CSiBE):
https://gcc.gnu.org/pipermail/gcc-patches/2021-June/573233.html
Investigating further,
An issue with a backend patch I've been investigating has revealed
a missed optimization opportunity during GCC's vector lowering pass.
An unrecognized insn for "(set (reg:SI) (not:SI (const_int 0))"
revealed that not only was my expander not expecting a NOT with
a constant operand, but also that
Tested on hppa2.0w-hp-hpux11.11. Committed to trunk.
Dave
Define STAGE1_LIBS to link against libcl.a in stage1 on hpux.
2021-08-19 Arnaud Charlet
PR ada/101924
gcc/ada/ChangeLog:
* gcc-interface/Make-lang.in (STAGE1_LIBS): Define on hpux.
diff --git
On Thu, Aug 19, 2021 at 09:03:44AM -0600, Martin Sebor via Gcc-patches wrote:
> On 8/18/21 11:56 PM, Kewen.Lin wrote:
> >To get rid of GTY variable alloc_object_size_limit looks suspicious,
> >maybe tree objects returned by alloc_max_size after the change are out
> >of GC's tracking?
>
> I
> Hmm, well. How about emitting .BTF.ext.string from GCC and have the linker
> merge the .BTF.ext.string section with the CTF string section then? You can't
> really say "the ship has sailed" if I read the CTF webpage - there seems to be
> many format changes planned.
Forgot to mention that
On 8/18/21 11:56 PM, Kewen.Lin wrote:
Hi David,
on 2021/8/19 上午11:26, David Edelsohn via Gcc-patches wrote:
Hi, Martin
A few PowerPC-specific testcases started failing yesterday on AIX with
a strange failure mode: the compiler runs out of memory. As you may
expect from telling you this in an
> On Tue, Aug 17, 2021 at 7:26 PM Indu Bhagat wrote:
>>
>> On 8/17/21 1:04 AM, Richard Biener wrote:
>> > On Mon, Aug 16, 2021 at 7:39 PM Indu Bhagat wrote:
>> >>
>> >> On 8/10/21 4:54 AM, Richard Biener wrote:
>> >>> On Thu, Aug 5, 2021 at 2:52 AM Indu Bhagat via Gcc-patches
>> >>> wrote:
>>
Hi all,
This patch generates FRINTZ instruction to optimize type casts.
The changes in this patch covers:
* Generate FRINTZ for (double)(int) casts.
* Add new test cases.
The intermediate type is not checked according to the C99 spec.
Overflow of the integral part when casting floats to
Hi!
On Thu, Aug 19, 2021 at 01:56:56PM +0800, Kewen.Lin via Gcc-patches wrote:
> on 2021/8/19 上午11:26, David Edelsohn via Gcc-patches wrote:
> > A few PowerPC-specific testcases started failing yesterday on AIX with
> > a strange failure mode: the compiler runs out of memory. As you may
> >
On 19/08/21 13:03 +0100, Jonathan Wakely wrote:
We should document the status of this unimplemented feature.
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
PR libstdc++/100139
* doc/xml/manual/status_cxx2020.xml: Add P1739R4 to status table.
*
This adds my new SHOW_HEADERFILE option, and removes some obsolete
options.
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
* doc/doxygen/user.cfg.in: Update to Doxygen 1.9.2
Tested powerpc64le-linux. Committed to trunk.
commit 778044ccf59205e85bc5fdcd1760d789fdd05022
Author:
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
PR libstdc++/101965
* include/std/charconv (__to_chars_i): Remove redundant check.
Tested powerpc64le-linux. Committed to trunk.
commit 85a709595005b5df4b2ee9d81717a5df19c0023f
Author: Jonathan Wakely
Date: Thu Aug 19
> On Aug 19, 2021, at 4:00 AM, Richard Biener wrote:
>
> On Wed, 18 Aug 2021, Qing Zhao wrote:
>
>>
>>
>>> On Aug 18, 2021, at 2:15 AM, Richard Biener wrote:
>>>
>>> On Tue, 17 Aug 2021, Qing Zhao wrote:
>>>
> On Aug 17, 2021, at 9:50 AM, Qing Zhao via Gcc-patches
>
On Tue, 17 Aug 2021, Joel Hutton wrote:
> Ping. Is there still interest in refactoring vect-patterns to internal_fn's?
Yes, sorry ...
+ internal_fn fn = as_internal_fn ((combined_fn) wide_code_or_ifn);
maybe add an overload to as_internal_fn.
+ pattern_stmt =
Currently we ICE when non-decl base-pointers (like struct members) are
used in OpenACC non-contiguous array sections.
This patch is kind of a band-aid to reject such cases ATM. We'll deal
with the more elaborate middle-end stuff to fully support them later.
Committed to devel/omp/gcc-11 after
Since 'Remove obsolete IRIX 6.5 support' [1] we only use
gp-relative jump-tables for PIC code. We can fall back to
default behaviour for asm_function_rodata_section.
[1] https://gcc.gnu.org/ml/libstdc++/2012-03/msg00067.html
2018-06-04 Dragan Mladjenovic
gcc/
* config/mips/mips.c
On Tue, 17 Aug 2021, Xionghu Luo wrote:
>
>
> On 2021/8/17 15:12, Richard Biener wrote:
> > On Tue, 17 Aug 2021, Xionghu Luo wrote:
> >
> >> Hi,
> >>
> >> On 2021/8/16 19:46, Richard Biener wrote:
> >>> On Mon, 16 Aug 2021, Xiong Hu Luo wrote:
> >>>
> It seems to me that
An array member cannot be direct-initialized in a ctor-initializer-list,
so use the base class' move constructor, which does the right thing for
both arrays and non-arrays.
This constructor could be defaulted, but that would make it trivial for
some specializations, which would change the
We should document the status of this unimplemented feature.
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
PR libstdc++/100139
* doc/xml/manual/status_cxx2020.xml: Add P1739R4 to status table.
* doc/html/manual/status.html: Regenerate.
Tested
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
* include/bits/shared_ptr.h: Add @since and @headerfile tags.
* include/bits/unique_ptr.h: Add @headerfile tags.
Tested powerpc64le-linux. Committed to trunk.
commit 30b300de8eb9a53c8ad8d80caf06e386e916bc66
Author:
The current code assumes that system_clock::duration is nanoseconds, and
also performs a value-changing conversion from nanoseconds::max() to
double (which doesn't matter after dividing by 1e9, but triggers a
warning with Clang nonetheless).
A better solution is to use
Tested powerpc64le-linux. Committed to trunk.
commit c8a1cf1a7a8be1dc0de48035d88fecf4954e37ba
Author: Jonathan Wakely
Date: Wed Aug 18 16:57:47 2021
libstdc++: Tweak whitespace
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
*
On Thu, Aug 19, 2021 at 08:59:16AM +0200, Christophe Lyon wrote:
> This patch ( r12-2975) is causing regressions on arm and aarch64:
>
> g++:g++.target/aarch64/aarch64.exp=g++.target/aarch64/no_unique_address_1.C
> check-function-bodies _Z8caller_pR1P
>
>
On Thu, 19 Aug 2021, Richard Sandiford wrote:
> Richard Biener writes:
> > On Wed, 18 Aug 2021, Richard Sandiford wrote:
> >> I think it would be OK/sensible to use the larger of the index or
> >> result vectors to determine the mask, if that helps. There just
> >> wasn't any need to make a
Richard Biener writes:
> On Wed, 18 Aug 2021, Richard Sandiford wrote:
>> I think it would be OK/sensible to use the larger of the index or
>> result vectors to determine the mask, if that helps. There just
>> wasn't any need to make a distinction for SVE, since there the
>> mask type is
On Wed, 18 Aug 2021, Qing Zhao wrote:
>
>
> > On Aug 18, 2021, at 2:15 AM, Richard Biener wrote:
> >
> > On Tue, 17 Aug 2021, Qing Zhao wrote:
> >
> >>
> >>
> >>> On Aug 17, 2021, at 9:50 AM, Qing Zhao via Gcc-patches
> >>> wrote:
> >>>
> >>>
> >>>
> On Aug 17, 2021, at 3:29 AM,
On Thu, 19 Aug 2021, Jakub Jelinek wrote:
> Hi!
>
> As suggested in the PR, the following patch adds two new clrsb
> expansion possibilities if target doesn't have clrsb_optab for the
> requested nor wider modes, but does have clz_optab for the requested
> mode.
> One expansion is
> clrsb (op0)
On Wed, 18 Aug 2021, Richard Sandiford wrote:
> Richard Biener writes:
> > On Wed, 18 Aug 2021, Hongtao Liu wrote:
> >
> >> On Wed, Aug 18, 2021 at 7:37 PM Hongtao Liu wrote:
> >> >
> >> > On Wed, Aug 18, 2021 at 7:30 PM Hongtao Liu wrote:
> >> > >
> >> > > On Wed, Aug 18, 2021 at 6:28 PM
Hi!
When working on error directive, I've noticed the C FE ICEs on
#pragma omp requires atomic_default_mem_order (
where it tries to peek 2nd token after the CPP_PRAGMA_EOL (or CPP_EOF)
in there in order to improve error-recovery on say
atomic_default_mem_order (acquire)
or
Hi!
When working on error directive, I've noticed that while C FE diagnosed
clauses on nothing directive which doesn't allow any, the C++ FE silently
accepted it.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux,
committed to trunk.
2021-08-19 Jakub Jelinek
*
Hi David,
> On 18 Aug 2021, at 20:54, David Malcolm via Gcc-patches
> wrote:
>
> On Wed, 2021-08-18 at 20:40 +0100, Iain Sandoe wrote:
>> Hi,
>>
>> * Note, the strategy in jit.exp has the assumption that
>> $target==$host
>> the patches here adhere to that - there is far less testsuite
>>
Hi!
As suggested in the PR, the following patch adds two new clrsb
expansion possibilities if target doesn't have clrsb_optab for the
requested nor wider modes, but does have clz_optab for the requested
mode.
One expansion is
clrsb (op0)
expands as
clz (op0 ^ (((stype)op0) >> (prec-1))) - 1
which
Hi Harald,
On 18.08.21 23:01, Harald Anlauf wrote:
Von: "Tobias Burnus"
Note, however, that gfc_simplify_len still won't handle neither
deferred strings nor their substrings.
Obviously, nonsubstrings cannot be simplified but I do not
see why len(str(1:2)) cannot or should not be simplified.
Hi!
On 2021-08-18T16:56:18-0700, "H.J. Lu" wrote:
> On Tue, Aug 17, 2021 at 12:01 AM Thomas Schwinge
> wrote:
>> On 2016-12-14T21:31:05-0500, David Malcolm wrote:
>> > On Wed, 2016-12-14 at 15:02 +0100, Bernd Schmidt wrote:
>> >> On 12/09/2016 08:32 PM, David Malcolm wrote:
>> >> > Thanks.
Hi Jakub,
On Tue, Aug 17, 2021 at 5:35 PM Jason Merrill via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> On 8/17/21 10:55 AM, Jakub Jelinek wrote:
> > On Tue, Aug 17, 2021 at 07:10:28AM -0700, Jason Merrill wrote:
> >> Looks good, thanks. I think you didn't see that I also asked for some
>
PING^3 https://gcc.gnu.org/pipermail/gcc-patches/2021-May/570139.html
On Fri, Jun 4, 2021 at 3:04 PM Fāng-ruì Sòng wrote:
>
> PING^2 https://gcc.gnu.org/pipermail/gcc-patches/2021-May/570139.html
>
> On Mon, May 24, 2021 at 9:43 AM Fāng-ruì Sòng wrote:
> >
> > Ping
76 matches
Mail list logo
