> Some x86 tests of stack realignment, that disaligned the stack with
> pushes and pops, failed when the compiler was configured to tune for a
> target that preferred to accumulate outgoing arguments: the stack
> space is reserved before the asm push, the call sequence overwrites
> the saved
On Mon, 30 Sep 2019 at 18:48, Richard Sandiford
wrote:
> Richard Sandiford writes:
> > [This follows on from:
> > https://gcc.gnu.org/ml/gcc-patches/2019-09/msg00778.html
> > https://gcc.gnu.org/ml/gcc-patches/2019-09/msg01456.html]
> >
> > With the function ABI stuff, we can now support
'}' is missed at the end.
gcc/ChangeLog:
tree-sra.c (dump_access): Add missing braces.
---
gcc/tree-sra.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/tree-sra.c b/gcc/tree-sra.c
index 48589323a1e..cb59b91f20e 100644
--- a/gcc/tree-sra.c
+++
On Tue, Oct 08, 2019 at 11:53:52AM +0200, Tobias Burnus wrote:
> Simple patch for better diagnostics:
>
> Before:
>
>17 | !$omp end target simd hjgfhg
> |1
> Error: Unclassifiable OpenMP directive at (1)
>
> Now:
>17 | !$omp end target simd hjgfhg
> |
Leaving the main review to Richard, just some comments...
Prathamesh Kulkarni writes:
> @@ -9774,6 +9777,10 @@ vect_is_simple_cond (tree cond, vec_info *vinfo,
>
> When STMT_INFO is vectorized as a nested cycle, for_reduction is true.
>
> + For COND_EXPR if T comes from masked load,
Christophe Lyon writes:
> On Mon, 30 Sep 2019 at 18:48, Richard Sandiford
> wrote:
>
> Richard Sandiford writes:
> > [This follows on from:
> > https://gcc.gnu.org/ml/gcc-patches/2019-09/msg00778.html
> > https://gcc.gnu.org/ml/gcc-patches/2019-09/msg01456.html]
> >
>
Simple patch for better diagnostics:
Before:
17 | !$omp end target simd hjgfhg
|1
Error: Unclassifiable OpenMP directive at (1)
Now:
17 | !$omp end target simd hjgfhg
|1
Error: Unexpected junk at (1)
OK for the trunk?
Cheers,
Tobias
Hi,
This is the formal documentation patch for IPA passes. Thanks.
None of the IPA passes are documented in passes.texi. This patch adds
a section IPA passes just before GIMPLE passes and RTL passes in
Chapter 9 "Passes and Files of the Compiler". Also, a short description
for each IPA pass
Hi!
On 2015-03-11T22:48:22+0100, I wrote:
> On Fri, 14 Nov 2014 18:08:32 +0100, Bernd Schmidt
> wrote:
>> New patch below, [...]
>
> ... got committed. I now committed the following in r221363:
> libgfortran LIBGFOR_MINIMAL enhancements.
..., and in r276690 have now committed the
Hi!
On 2019-09-02T22:16:52+0200, "Ulrich Weigand" wrote:
> * MAINTAINERS: Remove spu port maintainers.
> --- MAINTAINERS (revision 275321)
> +++ MAINTAINERS (working copy)
> @@ -109,9 +109,6 @@
> sh port Oleg Endo
> sparc port
In the large memory model, MSP430 instructions have some useful properties when
performing byte, word or address-word writes to registers or memory:
- Byte-writes to registers clear bits 19:8
- Word-writes to registers clear bits 19:16
- PSImode writes to memory clear bits 16:4 of the second
This patch has the functional changes to optimize zero_extend insns and pointer
manipulation in the large memory model.
>From f8156e115c4743ce94a86835ffa5601b6d28a555 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Mon, 7 Oct 2019 11:44:16 +0100
Subject: [PATCH 2/2] MSP430: PSImode
On Tue, Oct 08, 2019 at 12:46:13PM +0200, Tobias Burnus wrote:
> commit 4958da0be3f08d5f715dc4b74a8e93db18ca1a9e
> Author: burnus
> Date: Tue Oct 8 09:35:56 2019 +
>
> Remove '>>>' merge marker from changelog
> git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@276689
>
This builds upon the previous refactorings and does the following
1) move the reduction meta to the outermost PHI stmt_info (from the
inner loop computation stmt), the new info_for_reduction gets
you to that.
2) Merge STMT_VINFO_VEC_REDUCTION_TYPE and STMT_VINFO_REDUC_TYPE
into
Hi!
On 2019-08-16T17:31:36+0300, Janne Blomqvist wrote:
> Improve the error message that is printed when a memory allocation
> fails, by including the location, and the size of the allocation that
> failed.
> * runtime/error.c (os_error_at): New function.
Committed the attached in
This is an "obvious" mechanical patch which just reorders and groups the
zero_extend insns in msp430.md, in preparation for the next functional patch.
>From 8810aa7a19569d7e49e898613736d793c43c20a1 Mon Sep 17 00:00:00 2001
From: Jozef Lawrynowicz
Date: Mon, 7 Oct 2019 11:24:31 +0100
Subject:
On 07/10/19 20:54 +0200, Thomas Schwinge wrote:
Hi!
On 2019-09-05T08:45:50+0100, Jonathan Wakely wrote:
Committed to trunk. I think I'll backport this too, so we don't keep a
non-working link in the docs on release branches.
commit 45a605e970ea6db474e40c02aef6b18993fea05c
Author: Jonathan
commit 4958da0be3f08d5f715dc4b74a8e93db18ca1a9e
Author: burnus
Date: Tue Oct 8 09:35:56 2019 +
Remove '>>>' merge marker from changelog
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@276689 138bc75d-0d04-0410-961f-82ee72b054a4
diff --git a/gcc/fortran/ChangeLog
Hi,
On Tue, Oct 08 2019, luoxhu wrote:
> '}' is missed at the end.
heh, yeah, I wonder for how long.
If it irritates you, I'd say the patch is obvious (though note that I
cannot approve a patch in this area).
Thanks,
Martin
>
> gcc/ChangeLog:
> tree-sra.c (dump_access): Add missing
Also remove the creation of the html/ext sub-directory, which has been
unused since revision r245258.
* doc/Makefile.am (doc-html-docbook-regenerate): New target.
(${docbook_outdir}/html): Do not create unused 'html/ext' directory.
* doc/Makefile.in: Regenerate.
*
Hi,
On Tue, Oct 08 2019, Marc Glisse wrote:
> On Mon, 7 Oct 2019, Aldy Hernandez wrote:
>>
>> In testing this patch in isolation from the non-zero canonicalization patch,
>> I found one regression due to the fact that:
>>
>> a) As discussed, two non-zero representations currently exist for
Both my mailer and
https://gcc.gnu.org/ml/gcc-patches/2019-10/msg00528.html show an empty
line before the "" – as does the file itself.
Thus, there is already one – which should be enough.
Cheers,
Tobias,
who also thinks that email clients could be better in terms of line
breaks and
On Tue, Oct 08, 2019 at 01:52:17PM +0200, Tobias Burnus wrote:
> Both my mailer and https://gcc.gnu.org/ml/gcc-patches/2019-10/msg00528.html
> show an empty line before the "" – as does the file itself.
>
> Thus, there is already one – which should be enough.
Guess some issue in the mutt
* Tobias Burnus:
> Both my mailer and
> https://gcc.gnu.org/ml/gcc-patches/2019-10/msg00528.html show an empty
> line before the "" – as does the file itself.
>
> Thus, there is already one – which should be enough.
Inline patches with
Content-Type: text/plain; charset="utf-8";
I noticed we've fixed this DR already. It added [conv.prom]/4 and
type_promotes_to implements it:
/* ISO C++17, 7.6/4. A prvalue of an unscoped enumeration type
whose underlying type is fixed (10.2) can be converted to a
prvalue of its underlying type. Moreover, if
Hi,
This patch series is aimed at fixing an issue when cloning a function
with 'cmse_nonsecure_entry' attribute.
Currently if gcc determines to clone a function with this attribute,
both the cloned and original declarations will be compiled as nonsecure
entry functions. The linker eventually
Hi,
This patch adds a new target hook called
TARGET_HOOK_SANITIZE_CLONE_ATTRIBUTES. This hook is meant to give each
target the ability to sanitize a cloned's declaration attribute list.
Is this OK for trunk?
Cheers,
Andre
gcc/ChangeLog:
2019-10-08 Andre Vieira
*
Hi,
This patch implements the TARGET_HOOK_SANITIZE_CLONE_ATTRIBUTES for the
arm backend to remove the 'cmse_nonsecure_entry' attribute from cmse.
Bootstrapped the series on x86_64 and built arm-none-eabi, running the
cmse testsuite for armv8-m.main and armv8-m.base.
Is this OK for trunk?
Hi Richard,
As I mentioned in the IRC channel, I managed to get "most" of the
regression testsuite working for x86_64 (avx512) and aarch64.
On x86_64 I get a failure that I can't explain, was hoping you might be
able to have a look with me:
"PASS->FAIL: gcc.target/i386/vect-perm-odd-1.c
On 10/4/19 8:23 PM, Indu Bhagat wrote:
> Hello,
>
> At GNU Tools Cauldron this year, some folks were curious to know more on how
> the "type representation" in CTF compares vis-a-vis DWARF.
I was one of those, and I brought this up to Jose, after your
presentation. Glad to see the follow up!
Hi,
I've been looking at PR 70929 and at the newly reported duplicate PR
91988 and would like to propose the following patch to address them.
Basically, the idea is that if the types or arguments in TYPE_ARG_TYPES
(as opposed to DECL_ARGUMENTS) from both the type from the target fndecl
and from
On Tue, Oct 08, 2019 at 06:30:36PM +0200, Tom de Vries wrote:
> I just build gcc trunk with nvptx offloading, and ran libgomp on a
> Quadro M1200 with driver version 390.87.
>
> On the OpenMP side, there are the known errors plus a new internal
> compiler error.
One issue is the usleep problem
Hi Chung-Lin!
While we're all waiting for Tom to comment on this ;-) -- here's another
item I realized:
On 2019-09-10T19:41:59+0800, Chung-Lin Tang wrote:
> The libgomp nvptx plugin changes are also quite contained, with lots of
> now unneeded [...] code deleted (since we no longer first
Hi Tom!
On 2019-10-08T18:30:36+0200, Tom de Vries wrote:
> I just build gcc trunk with nvptx offloading, and ran libgomp on a
> Quadro M1200 with driver version 390.87.
>
> On the OpenMP side, there are the known errors plus a new internal
> compiler error.
>
> On the OpenACC side, there's the
Hi Richi,
Thanks for the review, I've added some comments inline.
The 10/07/2019 12:15, Richard Biener wrote:
> On Tue, 1 Oct 2019, Tamar Christina wrote:
>
> > Hi All,
> >
> > This adds a framework to allow pattern matchers to be written at based on
> > the
> > SLP tree. The difference
Hi,
I just build gcc trunk with nvptx offloading, and ran libgomp on a
Quadro M1200 with driver version 390.87.
On the OpenMP side, there are the known errors plus a new internal
compiler error.
On the OpenACC side, there's the usual lib-81.c timeout, plus a large
number of new failures in
Thomas Schwinge wrote:
> In r276692, I committed the attached to "Add back Trevor Smigiel; move
> into Write After Approval section", assuming that it was just an
> oversight that he got dropped from the file, as he -- in contrast to
> David and Ulrich -- doesn't remain listed with other roles.
This patch provides basic support for Fortran (2003) polymorphic class
pointers. Such pointers have a descriptor that is somewhat like an array
descriptor, so I re-used the GOMP_MAP_TO_PSET mapping to transfer such
class descriptors from the host to the target. That seems to work well,
though I
On Thu, 3 Oct 2019, Jeff Law wrote:
> You may want to review the 2018 discussion:
>
> https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg185287.html
>
> THe 2018 discussion was primarily concerned with fixing the CFG
> inaccuracies which would in turn fix 61118. But would not fix 21161.
On Fri, Oct 04, 2019 at 06:31:34PM -0300, Tulio Magno Quites Machado Filho
wrote:
> Remove all -L directories from LINK_OS_EXTRA_SPEC32 and
> LINK_OS_EXTRA_SPEC64 so that user directories specified at
> build time have higher preference over the advance toolchain libraries.
>
> Set
Hi,
On Tue, Oct 08 2019, Andre Vieira (lists) wrote:
> Hi,
>
> This patch adds a new target hook called
> TARGET_HOOK_SANITIZE_CLONE_ATTRIBUTES. This hook is meant to give each
> target the ability to sanitize a cloned's declaration attribute list.
>
>
> Is this OK for trunk?
>
> Cheers,
>
The following patch uses correct SSE register class; vzeroupper
operates only on lower 16 (8 on 32bit target) SSE registers.
2019-10-08 Uroš Bizjak
PR target/91994
* config/i386/i386.c (x86_avx_u128_mode_needed): Use SSE_REG
instead of ALL_SSE_REG to check if function call
The test cases in GCC's libraries run via DejaGNU's "[find_gcc]" –
unless the compiler has been explicitly provided. [1] That means that by
default everything runs with "/gcc/xgcc" – at least for an
in-build-dir test run.
As that's the C driver, specific libraries such as "-lgfortran" or
Hi Thomas,
On 10/6/19 5:26 PM, Thomas Koenig wrote:
+/* Under certain conditions, a scalar actual argument can be passed
+ to an array dummy argument - see F2018, 15.5.2.4, clause 14. This
+ functin returns true for these conditions so that an error or
function ("o" missing); I think it
Hi,
this patch fixes an overzealous interpretation of F2018 15.5.2.4, where
an idiom of passing an array element to an array was rejected. This
also restores Lapack compilation without warning.
Regression-tested. OK for trunk?
Would it be possible to get a speedy review on this? I'd like to
On Mon, 2019-10-07 at 12:04 +0200, Richard Biener wrote:
> On Tue, Oct 1, 2019 at 1:48 PM Dmitrij Pochepko
> wrote:
> >
> > Hi Richard,
> >
> > I updated patch according to all your comments.
> > Also bootstrapped and tested again on x86_64-pc-linux-gnu and
> > aarch64-linux-gnu, which took
This removes some code that should be dead.
Given no reported problems from the warning since 4.6 this seems reasonable.
It also happens to clear another build warning by deleting the offending code.
tested on x86_64-darwin16, applied to mainline,
thanks
Iain
gcc/ChangeLog:
2019-10-08 Iain
On 10/7/19 8:56 PM, Martin Sebor wrote:
-Wclass-memaccess doesn't trigger for access to arrays of
objects whose type it's designed to trigger for. It looks
to me like a simple oversight in maybe_warn_class_memaccess.
Attached is a trivial patch to correct it tested on
x86_64-linux.
OK,
I've been messing with compare_ics recently and noticed that we don't
implement CWG 1601, which should be fairly easy.
The motivating example is
enum E : char { e };
void f(char);
void f(int);
void g() {
f(e);
}
where the call to f was ambiguous but we should choose f(char).
On 10/7/19 6:58 PM, Martin Sebor wrote:
Last week's enhancement to detect one-byte buffer overflows exposed
a bug that let the warning use the size of a prior MEM_REF access
and "override" the size of the actual store to the character array.
When the store was smaller than the prior access
On 10/7/19 7:26 PM, Marek Polacek wrote:
On Mon, Oct 07, 2019 at 02:56:10PM -0400, Jason Merrill wrote:
@@ -1378,7 +1381,7 @@ standard_conversion (tree to, tree from, tree expr, bool
c_cast_p,
if (same_type_p (from, to))
/* OK */;
- else if (c_cast_p &&
This caches a check for the requirement to indirect a symbol in the Darwin
ABI, and uses it where needed. We also ensure that we place the indirection
pointers into the non-lazy symbol pointers section. Other placements have
occurred with various platform toolchains - but these seem to have been
On 10/8/19 2:52 AM, luoxhu wrote:
Hi,
This is the formal documentation patch for IPA passes. Thanks.
None of the IPA passes are documented in passes.texi. This patch adds
a section IPA passes just before GIMPLE passes and RTL passes in
Chapter 9 "Passes and Files of the Compiler". Also, a
Hi,
Thanks for explain that.
Add isa_rev=2 and -mfpxx to dg-options fix the fallout.
On Sun, Oct 6, 2019 at 8:03 PM Dragan Mladjenovic
wrote:
>
>
>
> On 06.10.2019. 08:43, Paul Hua wrote:
> > Hi:
> >
> > The testsuite has a typo in "dg-final scan-assembler", s/mthc1/mtc1/.
> >
>
>
> Hi,
>
> I
On Tue, 8 Oct 2019 at 13:21, Richard Sandiford
wrote:
>
> Leaving the main review to Richard, just some comments...
>
> Prathamesh Kulkarni writes:
> > @@ -9774,6 +9777,10 @@ vect_is_simple_cond (tree cond, vec_info *vinfo,
> >
> > When STMT_INFO is vectorized as a nested cycle,
Hi
Following what has been done for std::copy_n I think we could
simplify the __copy_move_a2 overload to also use sgetn. Code is simpler
and we avoid a friend declaration.
Tested under Linux x86_64.
* include/std/streambuf (__copy_move_a2): Remove friend declaration.
*
On 10/08/2019 08:37 AM, Pedro Alves wrote:
On 10/4/19 8:23 PM, Indu Bhagat wrote:
Hello,
At GNU Tools Cauldron this year, some folks were curious to know more on how
the "type representation" in CTF compares vis-a-vis DWARF.
I was one of those, and I brought this up to Jose, after your
Attached is a resubmission of the -Wrestrict implementation for
the sprintf family of functions. The original patch was posted
in 2017 but never approved. This revision makes only a few minor
changes to the original code, mostly necessitated by rebasing on
the top of trunk.
The description
I've done the move of GCC wwwdocs to git (using the previously posted and
discussed scripts), including setting up the post-receive hook to do the
same things previously covered by the old CVS hooks, and minimal updates
to the web pages dealing with the CVS setup for wwwdocs.
Note 1: someone
Hi -
Thanks - good job with moving this to git!
> Note 1: someone with the right access needs to create the symlink
> /sourceware/git/gcc-wwwdocs.git ->
> /sourceware/projects/gcc-home/wwwdocs.git (and anything else needed for
> anonymous git access to that repository).
Done.
- FChE
Following recently committed patches some changes that couldn't be
committed are now part of this patch.
Moreover testing istreambuf_iterator std::copy changes I realized that
this specialization was broken because order of function declarations in
stl_algobase.h was wrong. I'll check if I
Tested on x86_64-*-freebsd. OK to commit?
A BOZ literal constant can be an actual argument in a
very limited number of intrinsic subprograms. For those
intrinsics subprograms, the BOZ literal constant is converted
either during checking (see check.c) or simplification
(see simplify.c). In
Hi, Michael,
Would you please take a look at this modified version?
Thanks,
Feng
From: Feng Xue OS
Sent: Thursday, September 12, 2019 6:21 PM
To: Michael Matz
Cc: Richard Biener; gcc-patches@gcc.gnu.org
Subject: Re: Ping agian: [PATCH V2] Loop split
Seemingly, 'target simd' was forgotten – which yielded the error:
"Unexpected !$OMP TARGET SIMD statement"
OK for the trunk?
Tobias
PS: The test case should also work as 'dg-do run' test, if it makes more
sense. (Only tested on a system w/o offloading, but I would test it with
nvptx before
I have now also committed the patch to the OG9 branch.
Tobias
PS: I added the review comment to add more test cases to my to-do list.
On 10/8/19 11:53 AM, Tobias Burnus wrote:
Simple patch for better diagnostics:
Before:
17 | !$omp end target simd hjgfhg
| 1
Error:
On Tue, Oct 08, 2019 at 02:04:17PM +0200, Tobias Burnus wrote:
> Seemingly, 'target simd' was forgotten – which yielded the error:
> "Unexpected !$OMP TARGET SIMD statement"
>
> OK for the trunk?
>
> Tobias
>
> PS: The test case should also work as 'dg-do run' test, if it makes more
> sense.
Trunk (r276698): I have tested it with nvptx, it worked; hence, I moved
it to libgomp as run-time test.
OG9: I have also committed the patch to the OG9 / openacc-gcc-9 branch.
(54fbada7d4d38e420efb5a10d39e03b02533b1e7)
Thanks,
Tobias
On 10/8/19 2:12 PM, Jakub Jelinek wrote:
On Tue, Oct
67 matches
Mail list logo
