For the past several months I've been working on developing a set of
tests for the Fortran/C interoperability features added to Fortran via
TS 29113, "Further Interoperability of Fortran with C":
https://wg5-fortran.org/N1901-N1950/N1942.pdf
The goal here is to exercise gfortran's
On Thu, Jul 1, 2021 at 1:48 PM liuhongt wrote:
>
> From: "Guo, Xuepeng"
>
> gcc/ChangeLog:
>
> * common/config/i386/cpuinfo.h (get_available_features):
> Detect FEATURE_AVX512FP16.
> * common/config/i386/i386-common.c
> (OPTION_MASK_ISA_AVX512FP16_SET,
>
On Thu, Jul 1, 2021 at 1:48 PM liuhongt wrote:
>
> 1. Add extendhftf2, extendhfxf2, truncxfhf2, trunctfhf2, fixhfti,
> fixunshfti, floattihf and floatuntihf.
> 2. Always add _divhc3.c and _mulhc3.c. If assembler doesn't support
> AVX512FP16, they are empty.
>
> 2019-01-01 H.J. Lu
>
On Thu, Jul 1, 2021 at 1:48 PM liuhongt wrote:
>
> Hi:
> AVX512FP16 is disclosed, refer to [1].
> There're 100+ instructions for AVX512FP16, 67 gcc patches, for the
> convenience of review, we divide the 67 patches into 2 major parts.
> The first part is 2 patches containing basic support
On Wed, Jun 9, 2021 at 12:10 PM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 6/3/2021 12:51 PM, Seija K. via Gcc-patches wrote:
> > This patch optimizes and simplifies many of the standard string functions.
> >
> > Since C99, some of the standard string functions have been changed to use
> > the
For code like:
unsigned foo(unsigned val, unsigned start)
{
unsigned cnt = 0;
for (unsigned i = start; i > val; ++i)
cnt++;
return cnt;
}
The number of iterations should be about UINT_MAX - start.
There is function adjust_cond_for_loop_until_wrap which
handles similar work for const
On 6/30/21 3:56 PM, Peter Bergner wrote:
> The following patch is bootstrapping and regtesting on powerpc64le-linux.
> Ok for trunk if there are no regressions? Ok to backport to GCC 11 and
> GCC 10 after baking on trunk for a while?
Bootstrap and regression testing came back clean.
Peter
This defines some new Doxygen groups for C++17 variable templates and
for the contents of . By documenting the group
as a whole and adding each template to a group we don't need to document
them individually.
Also mark more internals with "@cond undocumented" so that Doxygen
ignores them by
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
* include/experimental/simd: Do not define anything pre-C++17.
Tested powerpc64le-linux. Committed to trunk.
commit 36adced3b6b7cae17d7b42e4573bd0f4194b1f70
Author: Jonathan Wakely
Date: Wed Jun 30 21:35:51 2021
libstdc++:
Since C++17 the static members of the random number engines are
implicitly inline, so don't need definitions.
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
* include/bits/random.tcc [__cpp_inline_variables]: Remove
redundant definitions of static constexpr member
On Thu, 2021-06-10 at 17:30 -0600, Martin Sebor wrote:
> This final diff removes the handlers for %G and %K from the pretty
> printer and the support for the directives from c-format.c so that
> using them will be diagnosed.
I think this is OK once the other patches in the kit are approved.
On Wed, 2021-06-30 at 13:45 -0600, Martin Sebor wrote:
> On 6/30/21 9:39 AM, Martin Sebor wrote:
> > Ping. Attached is the same patch rebased on top the latest trunk.
>
> Please see the attached patch instead. The previous one had typo
> in it.
>
> >
> > As discussed in the review of Aldy's
On Tue, 2021-06-15 at 17:00 -0600, Martin Sebor wrote:
> On 6/11/21 11:04 AM, David Malcolm wrote:
> > On Thu, 2021-06-10 at 17:26 -0600, Martin Sebor wrote:
> > > This diff introduces the diagnostic infrastructure changes to
> > > support
> > > controlling warnings at any call site in the
[Noticed this failure on powerpc64. Committed as obvious.]
testsuite: Add missing dg-add-options to CTF testcase ctf-skip-types-4.c
The test already has the appropriate dg-require-effective-target, but requires
the dg-add-options to use the flags needed, if any. This patch fixes the
failure of
On Tue, 29 Jun 2021, Jeff Law wrote:
>> 2021-06-29 Gerald Pfeifer
>>
>> * make-temp-file.c (usrtmp): Remove.
>> (choose_tmpdir): Remove use of usrtmp.
> Yup. This is fine. You might consider updating the comment which
> references /usr/tmp in
LLVM added the __builtin_vsx_lxvp and __builtin_vsx_stxvp built-ins.
The following patch adds support for them to GCC so that we stay in sync
with LLVM.
The following patch is bootstrapping and regtesting on powerpc64le-linux.
Ok for trunk if there are no regressions? Ok to backport to GCC 11
Here any_template_parm_r is failing to mark the template parameters
that're implicitly used by the unqualified use of 'd' inside the constraint,
because the code to do so assumes each level of a template parameter
list points to the corresponding primary template, but here the
parameter level for
On Wed, 30 Jun 2021, Jason Merrill wrote:
> On 6/30/21 10:48 AM, Patrick Palka wrote:
> > On Tue, 29 Jun 2021, Jason Merrill wrote:
> >
> > > On 6/29/21 1:57 PM, Patrick Palka wrote:
> > > > r12-1829 corrected the access scope during partial specialization
> > > > matching of class templates,
PR testsuite/101269 - new test case gcc.dg/debug/btf/btf-datasec-1.c
fails with its introduction in r12-1852
BTF datasec records for .rodata/.data are expected for now for all targets.
For powerpc based targets, use -msdata=none when ilp32 is enabled.
2021-06-30 Indu Bhagat
On 6/30/21 4:18 PM, Patrick Palka wrote:
On Wed, Jun 30, 2021 at 3:51 PM Jason Merrill wrote:
On 6/30/21 11:58 AM, Patrick Palka wrote:
On Wed, 30 Jun 2021, Patrick Palka wrote:
On Fri, 25 Jun 2021, Jason Merrill wrote:
On 6/25/21 1:11 PM, Patrick Palka wrote:
On Fri, 25 Jun 2021, Jason
On Wed, Jun 30, 2021 at 3:51 PM Jason Merrill wrote:
>
> On 6/30/21 11:58 AM, Patrick Palka wrote:
> > On Wed, 30 Jun 2021, Patrick Palka wrote:
> >
> >> On Fri, 25 Jun 2021, Jason Merrill wrote:
> >>
> >>> On 6/25/21 1:11 PM, Patrick Palka wrote:
> On Fri, 25 Jun 2021, Jason Merrill wrote:
On 6/30/21 10:48 AM, Patrick Palka wrote:
On Tue, 29 Jun 2021, Jason Merrill wrote:
On 6/29/21 1:57 PM, Patrick Palka wrote:
r12-1829 corrected the access scope during partial specialization
matching of class templates, but neglected the variable template case.
This patch moves the access
Hi Tobias,
> this patch broke Solaris bootstrap (both 32 and 64-bit sparc and x86):
>
> /vol/gcc/src/hg/master/local/gcc/gcc.c: In function 'bool
> check_offload_target_name(const char*, ptrdiff_t)':
> /vol/gcc/src/hg/master/local/gcc/gcc.c:4010:23: error: writing 1 byte into
> a region of size 0
Alan Modra via Gcc-patches writes:
> Compiling gcc/testsuite/gcc.dg/split-*.c and others with -mcpu=power10
> and linking with a non-pcrel libgcc results in crashes due to the
> power10 pcrel code not having r2 set for the generic-morestack.c
> functions called from __morestack. There is also a
On 6/11/21 8:46 AM, Martin Sebor wrote:
On 6/11/21 3:58 AM, Richard Sandiford wrote:
Martin Sebor via Gcc-patches writes:
diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
index 7b37e1b602c..7cdc824730c 100644
--- a/gcc/config/arm/arm.c
+++ b/gcc/config/arm/arm.c
@@ -13242,13 +13242,8
Hi, Andrew:
> On Jun 30, 2021, at 2:20 PM, Andrew Pinski wrote:
>
Then, where is the correct place for “.DEFERRED_INIT(size2,2)?
The variable “size2” is a block scope variable which is declared inside
the “if” condition:
>>>
>>> But that's obviously not how it
On 6/30/21 11:58 AM, Patrick Palka wrote:
On Wed, 30 Jun 2021, Patrick Palka wrote:
On Fri, 25 Jun 2021, Jason Merrill wrote:
On 6/25/21 1:11 PM, Patrick Palka wrote:
On Fri, 25 Jun 2021, Jason Merrill wrote:
On 6/24/21 4:45 PM, Patrick Palka wrote:
In the first testcase below, during
On 6/30/21 9:39 AM, Martin Sebor wrote:
Ping. Attached is the same patch rebased on top the latest trunk.
Please see the attached patch instead. The previous one had typo
in it.
As discussed in the review of Aldy's recent changes to the backwards
threader, he has run into the same bug the
On Wed, Jun 30, 2021 at 11:14 AM David Malcolm via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> On Wed, 2021-06-30 at 01:35 -0400, Trevor Saunders wrote:
> > This makes it possible to assert if input_location is used during the
> > lifetime
> > of a scope. This will allow us to find places
On Wed, Jun 30, 2021 at 12:14 PM Qing Zhao wrote:
>
>
>
> > On Jun 30, 2021, at 1:59 PM, Richard Biener wrote:
> >
> > On June 30, 2021 8:07:43 PM GMT+02:00, Qing Zhao
> > wrote:
> >>
> >>
> >>> On Jun 30, 2021, at 12:36 PM, Richard Biener
> >> wrote:
> >>>
> >>> On June 30, 2021 7:20:18 PM
> On Jun 30, 2021, at 1:59 PM, Richard Biener wrote:
>
> On June 30, 2021 8:07:43 PM GMT+02:00, Qing Zhao wrote:
>>
>>
>>> On Jun 30, 2021, at 12:36 PM, Richard Biener
>> wrote:
>>>
>>> On June 30, 2021 7:20:18 PM GMT+02:00, Andrew Pinski
>> wrote:
On Wed, Jun 30, 2021 at 8:47 AM
> On Jun 30, 2021, at 1:59 PM, Richard Biener wrote:
>
> On June 30, 2021 8:07:43 PM GMT+02:00, Qing Zhao wrote:
>>
>>
>>> On Jun 30, 2021, at 12:36 PM, Richard Biener
>> wrote:
>>>
>>> On June 30, 2021 7:20:18 PM GMT+02:00, Andrew Pinski
>> wrote:
On Wed, Jun 30, 2021 at 8:47 AM
On June 30, 2021 2:33:30 PM GMT+02:00, Trevor Saunders
wrote:
>On Wed, Jun 30, 2021 at 11:00:37AM +0200, Richard Biener wrote:
>> On Wed, Jun 30, 2021 at 7:37 AM Trevor Saunders
> wrote:
>> >
>> > This makes it possible to assert if input_location is used during
>the lifetime
>> > of a scope.
Hi!
On Tue, Jun 08, 2021 at 08:24:47PM -0400, Michael Meissner wrote:
> In this patch, I simplified things compared to previous patches. Instead of
> allowing any four of the modes to be used for the conditional move comparison
> and the move itself could use different modes, I restricted the
Hi,
I came up with the following small testing case and compile it WITHOUT
-ftrivial-auto-var-init option, the same problem:
[qinzhao@localhost gcc]$ cat t1.c
extern void bar (int);
extern int ART_INIT(int, int);
void foo (int a)
{
int i;
for (i = 0; i < a; i++) {
if (__extension__({int
On June 30, 2021 8:07:43 PM GMT+02:00, Qing Zhao wrote:
>
>
>> On Jun 30, 2021, at 12:36 PM, Richard Biener
>wrote:
>>
>> On June 30, 2021 7:20:18 PM GMT+02:00, Andrew Pinski
> wrote:
>>> On Wed, Jun 30, 2021 at 8:47 AM Qing Zhao via Gcc-patches
>>> wrote:
I came up with a very
On Wed, 30 Jun 2021, Tobias Burnus wrote:
> While looking at that issue, Jakub and I wondered whether there
> should be some warning if a Driver option has a help text,
> which never appears.
Migrating from hardcoded help text in gcc.c to using .opt help text for
Driver options to generate
> On Jun 30, 2021, at 12:36 PM, Richard Biener wrote:
>
> On June 30, 2021 7:20:18 PM GMT+02:00, Andrew Pinski
> wrote:
>> On Wed, Jun 30, 2021 at 8:47 AM Qing Zhao via Gcc-patches
>> wrote:
>>>
>>> I came up with a very simple testing case that can repeat the same
>> issue:
>>>
>>>
Tamar Christina writes:
>> -Original Message-
>> From: Richard Sandiford
>> Sent: Monday, June 14, 2021 4:55 PM
>> To: Tamar Christina
>> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
>> ; Marcus Shawcroft
>> ; Kyrylo Tkachov
>> Subject: Re: [PATCH][RFC]AArch64 SVE: Fix multiple
Hi, Andrew,
Thanks a lot for your explanation.
On Jun 30, 2021, at 12:20 PM, Andrew Pinski
mailto:pins...@gmail.com>> wrote:
On Wed, Jun 30, 2021 at 8:47 AM Qing Zhao via Gcc-patches
mailto:gcc-patches@gcc.gnu.org>> wrote:
I came up with a very simple testing case that can repeat the same
On June 30, 2021 7:20:18 PM GMT+02:00, Andrew Pinski wrote:
>On Wed, Jun 30, 2021 at 8:47 AM Qing Zhao via Gcc-patches
> wrote:
>>
>> I came up with a very simple testing case that can repeat the same
>issue:
>>
>> [qinzhao@localhost gcc]$ cat t.c
>> extern void bar (int);
>> void foo (int a)
>>
On Mon, Jun 28, 2021 at 03:00:02PM -0400, Michael Meissner wrote:
> On Wed, Jun 23, 2021 at 06:56:37PM -0500, Segher Boessenkool wrote:
> > > The problem area is a power10 running in
> > > big endian mode and running 32-bit code. Because we don't have TImode, we
> > > can't enable the IEEE
On Wed, Jun 30, 2021 at 8:47 AM Qing Zhao via Gcc-patches
wrote:
>
> I came up with a very simple testing case that can repeat the same issue:
>
> [qinzhao@localhost gcc]$ cat t.c
> extern void bar (int);
> void foo (int a)
> {
> int i;
> for (i = 0; i < a; i++) {
> if (__extension__({int
On Tue, Jun 29, 2021 at 07:06:14PM -0500, Segher Boessenkool wrote:
> On Thu, Jun 17, 2021 at 06:56:09PM -0400, Michael Meissner wrote:
> > The 'lp64' test
> > was needed because big endian 32-bit code cannot enable the IEEE 128-bit
> > floating point instructions.
>
> No, *does not* enable them.
On 6/30/21 11:03 AM, Patrick Palka wrote:
On Tue, 29 Jun 2021, Jason Merrill wrote:
On 6/29/21 1:57 PM, Patrick Palka wrote:
When push_access_scope is passed a TYPE_DECL for a class type (which
can happen during e.g. satisfaction), we undesirably push only the
enclosing context of the class
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2021-June/572519.html
On 6/10/21 5:30 PM, Martin Sebor wrote:
This final diff removes the handlers for %G and %K from the pretty
printer and the support for the directives from c-format.c so that
using them will be diagnosed.
> -Original Message-
> From: Richard Sandiford
> Sent: Monday, June 14, 2021 4:55 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; Marcus Shawcroft
> ; Kyrylo Tkachov
> Subject: Re: [PATCH][RFC]AArch64 SVE: Fix multiple comparison masks on
> inverted
On Wed, 30 Jun 2021, Patrick Palka wrote:
> On Fri, 25 Jun 2021, Jason Merrill wrote:
>
> > On 6/25/21 1:11 PM, Patrick Palka wrote:
> > > On Fri, 25 Jun 2021, Jason Merrill wrote:
> > >
> > > > On 6/24/21 4:45 PM, Patrick Palka wrote:
> > > > > In the first testcase below, during parsing of
On Fri, 25 Jun 2021, Jason Merrill wrote:
> On 6/25/21 1:11 PM, Patrick Palka wrote:
> > On Fri, 25 Jun 2021, Jason Merrill wrote:
> >
> > > On 6/24/21 4:45 PM, Patrick Palka wrote:
> > > > In the first testcase below, during parsing of the alias template
> > > > ConstSpanType, transparency of
I came up with a very simple testing case that can repeat the same issue:
[qinzhao@localhost gcc]$ cat t.c
extern void bar (int);
void foo (int a)
{
int i;
for (i = 0; i < a; i++) {
if (__extension__({int size2;
size2 = 4;
size2 > 5;}))
bar (a);
}
}
> Cc: jos...@codesourcery.com, g...@gcc.gnu.org, gcc-patches@gcc.gnu.org
> From: Martin Liška
> Date: Wed, 30 Jun 2021 16:04:32 +0200
>
> > Thanks, but does that mean @var will no longer stand out in the
> > produced Info format? That'd be sub-optimal, I think, because a clear
> > reference to
"Kewen.Lin" writes:
> on 2021/6/28 下午3:20, Hongtao Liu wrote:
>> On Mon, Jun 28, 2021 at 3:12 PM Hongtao Liu wrote:
>>>
>>> On Mon, Jun 28, 2021 at 2:50 PM Kewen.Lin wrote:
Hi!
on 2021/6/9 下午1:18, Kewen.Lin via Gcc-patches wrote:
> Hi,
>
> PR100328 has some
Ping. Attached is the same patch rebased on top the latest trunk.
As discussed in the review of Aldy's recent changes to the backwards
threader, he has run into the same bug the patch fixes. Getting this
patch set reviewed and approved would be helpful in keeping him from
having to work around
On 2021-06-28 2:26 a.m., Kewen.Lin wrote:
Hi!
on 2021/6/9 下午1:18, Kewen.Lin via Gcc-patches wrote:
Hi,
PR100328 has some details about this issue, I am trying to
brief it here. In the hottest function LBM_performStreamCollideTRT
of SPEC2017 bmk 519.lbm_r, there are many FMA style
On 2021-06-28 2:26 a.m., Kewen.Lin wrote:
Hi!
on 2021/6/9 下午1:18, Kewen.Lin via Gcc-patches wrote:
Hi,
PR100328 has some details about this issue, I am trying to
brief it here. In the hottest function LBM_performStreamCollideTRT
of SPEC2017 bmk 519.lbm_r, there are many FMA style
On 29/06/2021 12:46, Prathamesh Kulkarni wrote:
On Mon, 28 Jun 2021 at 14:48, Christophe LYON
wrote:
On 28/06/2021 10:40, Kyrylo Tkachov via Gcc-patches wrote:
-Original Message-
From: Prathamesh Kulkarni
Sent: 28 June 2021 09:38
To: Kyrylo Tkachov
Cc: Christophe Lyon ; gcc
On Wed, 2021-06-30 at 01:35 -0400, Trevor Saunders wrote:
> This makes it possible to assert if input_location is used during the
> lifetime
> of a scope. This will allow us to find places that currently use it
> within a
> function and its callees, or prevent adding uses within the lifetime
> of
> On Jun 30, 2021, at 9:39 AM, Richard Biener wrote:
>
> On Wed, 30 Jun 2021, Qing Zhao wrote:
>
>>
>>
>> On Jun 30, 2021, at 2:46 AM, Richard Biener
>> mailto:rguent...@suse.de>> wrote:
>>
>> On Wed, 30 Jun 2021, Qing Zhao wrote:
>>
>> Hi,
>>
>> I am testing the 4th patch of
Successfully tested via:
pytest contrib/gcc-changelog/
contrib/ChangeLog:
* gcc-changelog/git_commit.py (ChangeLogEntry.__init__): Convert
ChangeLogEntry.opened_parentheses from an integer to a stack of
line strings.
(ChangeLogEntry.parse_changelog): Likewise.
On Tue, 29 Jun 2021, Jason Merrill wrote:
> On 6/29/21 1:57 PM, Patrick Palka wrote:
> > When push_access_scope is passed a TYPE_DECL for a class type (which
> > can happen during e.g. satisfaction), we undesirably push only the
> > enclosing context of the class instead of the class itself.
On 6/30/2021 4:50 AM, Richard Biener via Gcc-patches wrote:
On Wed, Jun 30, 2021 at 10:47 AM Uros Bizjak via Gcc-patches
wrote:
This RFC patch changes the type of predicates to bool. However, some
of the targets (e.g. x86) use indirect functions to call the
predicates, so without the local
On Tue, 29 Jun 2021, Jason Merrill wrote:
> On 6/29/21 1:57 PM, Patrick Palka wrote:
> > r12-1829 corrected the access scope during partial specialization
> > matching of class templates, but neglected the variable template case.
> > This patch moves the access scope adjustment to inside
> >
On Wed, 30 Jun 2021, Qing Zhao wrote:
>
>
> On Jun 30, 2021, at 2:46 AM, Richard Biener
> mailto:rguent...@suse.de>> wrote:
>
> On Wed, 30 Jun 2021, Qing Zhao wrote:
>
> Hi,
>
> I am testing the 4th patch of -ftrivial-auto-var-init with CPU2017 today, and
> found the following issues:
>
>
I rewrote the way the analyzer's region_model tracks the state of memory
in GCC 11 (in 808f4dfeb3a95f50f15e71148e5c1067f90a126d), which
introduced a store with a binding_map class, mapping binding keys to
symbolic values.
The GCC 11 implementation of binding keys has an enum binding_kind,
which
On Jun 30, 2021, at 2:46 AM, Richard Biener
mailto:rguent...@suse.de>> wrote:
On Wed, 30 Jun 2021, Qing Zhao wrote:
Hi,
I am testing the 4th patch of -ftrivial-auto-var-init with CPU2017 today, and
found the following issues:
In the dump file of “*t.i.031t.objsz1”, we have:
:
On 6/30/21 3:38 PM, Eli Zaretskii wrote:
Cc: jos...@codesourcery.com, g...@gcc.gnu.org, gcc-patches@gcc.gnu.org
From: Martin Liška
Date: Wed, 30 Jun 2021 15:28:40 +0200
‘@`file'’
Read command-line options from ‘`file'’. The options read are
inserted in place of the
I've noticed that overriding cpu/arch flags when running the testsuite
can cause this test to fail rather than being skipped because of
incompatible flags combination.
Since the test forces -march=armv7-a, make sure it is accepted in
combination with the current runtestflags.
2021-06-30
> Cc: jos...@codesourcery.com, g...@gcc.gnu.org, gcc-patches@gcc.gnu.org
> From: Martin Liška
> Date: Wed, 30 Jun 2021 15:28:40 +0200
>
> >‘@`file'’
> >
> > Read command-line options from ‘`file'’. The options read are
> > inserted in place of the original ‘@`file'’ option.
On 6/29/21 6:01 PM, Marek Polacek wrote:
On Tue, Jun 29, 2021 at 03:50:27PM -0400, Jason Merrill wrote:
On 6/29/21 3:25 PM, Marek Polacek wrote:
--- a/gcc/testsuite/g++.dg/cpp0x/auto3.C
+++ b/gcc/testsuite/g++.dg/cpp0x/auto3.C
@@ -10,7 +10,7 @@ auto x; // {
On 6/29/21 6:57 PM, Eli Zaretskii wrote:
2. The translation of @var produces double-quoting in Info, here's an
example:
The usual way to run GCC is to run the executable called ‘gcc’, or
‘`machine'-gcc’ when cross-compiling, or ‘`machine'-gcc-`version'’ to
run a specific version of
On 6/30/21 2:20 AM, Aldy Hernandez wrote:
On 6/29/21 9:09 PM, Andrew MacLeod wrote:
We added context to a lot of simplify_using_ranges, but we didn't
catch all the places. This provides the originating stmt to the
missing cases which resolve a few EVRP testcases when running in
ranger-only
Ping patch:
https://gcc.gnu.org/pipermail/gcc-patches/2021-June/573213.html
Status update: bootstrapped with BOOT_CFLAGS="-O3 -mmsa -mloongson-mmi"
(it failed without the patch), and regtested on mips64el-linux-gnu with
no new regression.
On Sat, 2021-06-19 at 15:34 +0800, Xi Ruoyao wrote:
>
> Cc: jos...@codesourcery.com, g...@gcc.gnu.org, gcc-patches@gcc.gnu.org
> From: Martin Liška
> Date: Wed, 30 Jun 2021 12:11:03 +0200
>
> > (Admittedly, Emacs by default hides some of the text of a
> > cross-reference, but not hiding them in this case produces an even
> > less legible text.)
>
RFC for this topic. Comments are welcome as is someone volunteering to
cleanup this mess :-)
On 30.06.21 14:24, Tobias Burnus wrote:
This is a side effect of removing 'foffload=' from Common
as Driver only does not show up with --help=... but only
as hard-coded list via display_help.
While
On 6/30/21 12:55 PM, Andrey Belevantsev wrote:
Hi Martin,
On 29.06.2021 13:09, Martin Liška wrote:
On 6/28/21 5:33 PM, Joseph Myers wrote:
Are formatted manuals (HTML, PDF, man, info) corresponding to this patch
version also available for review?
I've just uploaded them here:
On Wed, Jun 30, 2021 at 11:00:37AM +0200, Richard Biener wrote:
> On Wed, Jun 30, 2021 at 7:37 AM Trevor Saunders wrote:
> >
> > This makes it possible to assert if input_location is used during the
> > lifetime
> > of a scope. This will allow us to find places that currently use it within
> >
On Wed, Jun 30, 2021 at 02:24:51PM +0200, Tobias Burnus wrote:
> This is a side effect of removing 'foffload=' from Common
> as Driver only does not show up with --help=... but only
> as hard-coded list via display_help.
>
> OK?
>
> Tobias
>
> PS: additional remarks in the next email.
>
>
On 6/29/21 6:57 PM, Eli Zaretskii wrote:
5. There's some strange bug with symbols inside parentheses. For
example:
In GNU C and C++, you can use function attributes to specify certain
function properties that may help the compiler optimize calls or check
code more carefully for
This is a side effect of removing 'foffload=' from Common
as Driver only does not show up with --help=... but only
as hard-coded list via display_help.
OK?
Tobias
PS: additional remarks in the next email.
-
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München
On Wed, Jun 30, 2021 at 11:00 AM Richard Sandiford
wrote:
>
> Richard Biener via Gcc-patches writes:
> > Note there's also array_slice<> which could be used to pass non-const
> > vec<>s that are never resized but modified - the only "valid" case of
> > passing a non-const vec<> by value.
>
>
On 6/30/21 12:14 PM, Richard Earnshaw wrote:
On 30/06/2021 05:47, Martin Liška wrote:
On 6/29/21 12:50 PM, Richard Earnshaw wrote:
On 29/06/2021 11:09, Martin Liška wrote:
On 6/28/21 5:33 PM, Joseph Myers wrote:
Are formatted manuals (HTML, PDF, man, info) corresponding to this patch
Hi,
I have just committed the following small patch as obvious:
Author: Christophe Lyon
Date: Wed Jun 30 11:44:00 2021 +
[testsuite]: Add missing dg-add-options float16 to
gcc.dg/debug/ctf/ctf-skip-types-2.c
The test already checks dg-require-effective-target float16, but this
Hi Martin,
On 29.06.2021 13:09, Martin Liška wrote:
> On 6/28/21 5:33 PM, Joseph Myers wrote:
>> Are formatted manuals (HTML, PDF, man, info) corresponding to this patch
>> version also available for review?
>
> I've just uploaded them here:
> https://splichal.eu/gccsphinx-final/
>
> Martin
I've
This fixes the missed handling of external/constant mask SLP
operations, for the testcase in particular masked loads. The
patch adjusts the vect_check_scalar_mask API to reflect the
required vect_is_simple_use SLP compatible API plus adjusts
for the special handling of masked loads in SLP
On Wed, Jun 30, 2021 at 10:47 AM Uros Bizjak via Gcc-patches
wrote:
>
> This RFC patch changes the type of predicates to bool. However, some
> of the targets (e.g. x86) use indirect functions to call the
> predicates, so without the local change, the build fails. Putting the
> patch through CI
On 6/30/21 12:11 PM, Martin Liška wrote:
Seems correct to be, but it's likely not. Let me investigate that.
It's a real issue in Sphinx. I've just addressed that with:
https://github.com/sphinx-doc/sphinx/pull/9390
Cheers,
Martin
On Wed, 30 Jun 2021 10:28:00 +0200
Thomas Schwinge wrote:
> > - The OpenACC profiling-interface implementation did not measure
> >asynchronous operations properly.
>
> We'll need to be careful: (possibly, an older version of) that one we
> internally had identified to be causing some
On Wed, Jun 30, 2021 at 12:19:17PM +0200, Tobias Burnus wrote:
> gcc.c's check_offload_target_name: Fixes to inform hints
>
> gcc/ChangeLog:
>
> * gcc.c (close_at_file, execute): Replace alloca by XALLOCAVEC.
> (check_offload_target_name): Fix splitting OFFLOAD_TARGETS into
> a
As discussed at IRC:
* Replace alloca by XALLOCAVEC - and while being there, do it in the whole file.
* Fix splitting OFFLOAD_TARGETS at the ',' for the candidate list
* More helpful inform if no targets have been configured.
* For -foffload-options=, the 'target' argument may be 'nvptx,amdgcn'
On 30/06/2021 05:47, Martin Liška wrote:
On 6/29/21 12:50 PM, Richard Earnshaw wrote:
On 29/06/2021 11:09, Martin Liška wrote:
On 6/28/21 5:33 PM, Joseph Myers wrote:
Are formatted manuals (HTML, PDF, man, info) corresponding to this
patch
version also available for review?
I've just
On Wed, Jun 30, 2021 at 5:42 PM Kewen.Lin wrote:
>
> on 2021/6/30 下午4:53, Hongtao Liu wrote:
> > On Mon, Jun 28, 2021 at 3:27 PM Kewen.Lin wrote:
> >>
> >> on 2021/6/28 下午3:20, Hongtao Liu wrote:
> >>> On Mon, Jun 28, 2021 at 3:12 PM Hongtao Liu wrote:
>
> On Mon, Jun 28, 2021 at 2:50
On 6/29/21 6:57 PM, Eli Zaretskii wrote:
From: Martin Liška
Date: Tue, 29 Jun 2021 12:09:23 +0200
Cc: GCC Development , gcc-patches@gcc.gnu.org
On 6/28/21 5:33 PM, Joseph Myers wrote:
Are formatted manuals (HTML, PDF, man, info) corresponding to this patch
version also available for review?
on 2021/6/30 下午4:53, Hongtao Liu wrote:
> On Mon, Jun 28, 2021 at 3:27 PM Kewen.Lin wrote:
>>
>> on 2021/6/28 下午3:20, Hongtao Liu wrote:
>>> On Mon, Jun 28, 2021 at 3:12 PM Hongtao Liu wrote:
On Mon, Jun 28, 2021 at 2:50 PM Kewen.Lin wrote:
>
> Hi!
>
> on 2021/6/9
We have two families of routines to query entity properties: Known_XXX
and Unknown_XXX. They now simply negate each other instead of negating
their complex conditions.
Code cleanup only related to handling of Alignment in GNATprove;
semantics is unaffected.
Tested on x86_64-pc-linux-gnu,
When we make a copy of a tree containing a block, we need to make new
entities for variables declared in the block. If not, the entity
points to the wrong declaration, which is an invalid tree and can
cause issues when we need static links and that variable is an uplevel
reference. There may
The -gnatyr switch is supposed to generate a style warning if the case
of a usage name does not match that of the defining_identifier it
denotes. The warning was missing for component names appearing in record
representation clauses; this patch fixes that bug.
Tested on x86_64-pc-linux-gnu,
Compiler aborts on an object declaration for a limited array type,
when declaration includes an aggregate that must be built in place,
and declaration carries an aspect specification for Address of object.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_aggr.adb
The special case used for catching the 'mod -1' operation is not useful
to CodePeer, and in fact may be detrimental to its precision. Remove
it in CodePeer_Mode.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_ch4.adb (Expand_N_Op_Mod): Remove special case for mod -1
GNATprove no longer calls an obsolete variant of Adjust_Name_Case that
uses a global buffer.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* errout.ads (Adjust_Name_Case): Remove obsolete and now unused
variant.
* errout.adb (Adjust_Name_Case): Likewise; fix
This makes the comments use the same syntax as -gnatD/G for freeze nodes.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch12.adb (Freeze_Subprogram_Body): Add missing "freeze".
(Install_Body): Likewise.diff --git a/gcc/ada/sem_ch12.adb b/gcc/ada/sem_ch12.adb
1 - 100 of 140 matches
Mail list logo
