On неделя, 9 юни 2019 г. 22:34:23 EEST Andreas Schwab wrote:
> On Jun 09 2019, Dimitar Dimitrov wrote:
> > diff --git a/gcc/testsuite/gcc.c-torture/execute/20101011-1.c
> > b/gcc/testsuite/gcc.c-torture/execute/20101011-1.c index
> > d2beeb52a0e..4a9cc63fde8 100644
> > ---
The problem here is that we're getting "requested alignment is not an
integer constant" since r261971, because of this part of the patch:
@ -4676,7 +4685,11 @@ cxx_eval_constant_expression (const constexpr_ctx *ctx,
tree t,
conversion. */
return fold (t);
- if (tcode ==
On 6/9/19 6:28 PM, Jonathan Wakely wrote:
On 10/06/19 00:03 +0200, Rainer Orth wrote:
Hi Ed,
I had supplied the option for gnu++2a by hand and they passed.?? They
were not UNSUPPORTED.
I just added the dg-options (at very top) and reran the testsuite
without fancy tricks (except for
This testcase used to ICE but was fixed by r259067. We now issue
67533.C:5:26: error: conversion from ‘void’ to non-scalar type ‘Tls’ requested
5 | thread_local Tls mytls = mytls; // { dg-error "" }
| ^
whereas clang++ and icc compile it. However, the
This one was fairly difficult to reduce but finally I've come up with something
that compiles without warnings with trunk/clang++/icc.
It was fixed by r261709 which has a much simpler test but I suppose there's
value in exercising more involved code.
Tested on x86_64-linux, applying to trunk.
Hi Dimitar,
Just some comments, do with it what you want :-)
On Sun, Jun 09, 2019 at 11:01:38PM +0300, Dimitar Dimitrov wrote:
> +; An unfortunate side effect is that quite a few invalid RTL patterns are
> +; generated. For example:
> +; ... (zero_extend:SI (match_operand:SI ...)) ...
You
On 10/06/19 00:03 +0200, Rainer Orth wrote:
Hi Ed,
I had supplied the option for gnu++2a by hand and they passed.?? They
were not UNSUPPORTED.
I just added the dg-options (at very top) and reran the testsuite
without fancy tricks (except for gnu++2a).
I also took out the #if __cplusplus.?? I
On Mon, 10 Jun 2019 at 01:03, Rainer Orth wrote:
>
> Hi Ed,
>
> >>> I had supplied the option for gnu++2a by hand and they passed.?? They
> >>> were not UNSUPPORTED.
> >>>
> >>> I just added the dg-options (at very top) and reran the testsuite
> >>> without fancy tricks (except for gnu++2a).
>
Hi Ed,
>>> I had supplied the option for gnu++2a by hand and they passed.?? They
>>> were not UNSUPPORTED.
>>>
>>> I just added the dg-options (at very top) and reran the testsuite
>>> without fancy tricks (except for gnu++2a).
>>>
>>> I also took out the #if __cplusplus.?? I was just playing
On 6/8/19 4:28 PM, Jonathan Wakely wrote:
On 08/06/19 12:05 -0400, Ed Smith-Rowland wrote:
On 6/7/19 11:42 AM, Jonathan Wakely wrote:
On 01/06/19 15:40 -0400, Ed Smith-Rowland via libstdc++ wrote:
On 6/1/19 2:42 PM, Ville Voutilainen wrote:
On Sat, 1 Jun 2019 at 21:09, Ed Smith-Rowland
On Jun 09 2019, Dimitar Dimitrov wrote:
> diff --git a/gcc/testsuite/gcc.c-torture/execute/20101011-1.c
> b/gcc/testsuite/gcc.c-torture/execute/20101011-1.c
> index d2beeb52a0e..4a9cc63fde8 100644
> --- a/gcc/testsuite/gcc.c-torture/execute/20101011-1.c
> +++
For variadic functions, the last named and all anonymous arguments
are passed on stack. Regular functions pass arguments in registers.
gcc/testsuite/ChangeLog:
2019-06-07 Dimitar Dimitrov
* gcc.dg/builtin-apply2.c: Skip for PRU.
* gcc.dg/torture/stackalign/builtin-apply-2.c:
gcc/testsuite/ChangeLog:
2019-06-07 Dimitar Dimitrov
* gcc.dg/tree-ssa/20040204-1.c: XFAIL on pru.
* gcc.dg/tree-ssa/reassoc-33.c: Ditto.
* gcc.dg/tree-ssa/reassoc-34.c: Ditto.
* gcc.dg/tree-ssa/reassoc-35.c: Ditto.
* gcc.dg/tree-ssa/reassoc-36.c:
gcc/testsuite/ChangeLog:
2019-06-07 Dimitar Dimitrov
* g++.old-deja/g++.abi/ptrmem.C: Add PRU to list.
Signed-off-by: Dimitar Dimitrov
---
gcc/testsuite/g++.old-deja/g++.abi/ptrmem.C | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Not all C language features are supported when -mabi=ti option is
used for PRU target.
gcc/testsuite/ChangeLog:
2019-06-07 Dimitar Dimitrov
* lib/gcc-dg.exp: Filter unsupported features in PRU's TI ABI mode.
* lib/target-utils.exp: Ditto.
* lib/target-supports.exp
gcc/testsuite/ChangeLog:
2019-06-07 Dimitar Dimitrov
* gcc.dg/stack-usage-1.c: Define PRU stack usage.
Signed-off-by: Dimitar Dimitrov
---
gcc/testsuite/gcc.dg/stack-usage-1.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.dg/stack-usage-1.c
gcc/testsuite/ChangeLog:
2019-06-07 Dimitar Dimitrov
* gcc.target/pru/abi-arg-struct.c: New test.
* gcc.target/pru/ashiftrt.c: New test.
* gcc.target/pru/builtins-1.c: New test.
* gcc.target/pru/builtins-error.c: New test.
* gcc.target/pru/clearbit.c:
gcc/testsuite/ChangeLog:
2019-06-07 Dimitar Dimitrov
* gcc.c-torture/execute/20101011-1.c: Define DO_TEST to 0 for PRU.
* gcc.dg/20020312-2.c: No PIC register for PRU.
Signed-off-by: Dimitar Dimitrov
---
gcc/testsuite/gcc.c-torture/execute/20101011-1.c | 2 ++
The floating point support has been borrowed from C6X libgcc port
to help with TI PRU toolchain ABI compatibility.
libgcc/ChangeLog:
2019-06-07 Dimitar Dimitrov
* config.host: Add PRU target.
* config/pru/asri.c: New file.
* config/pru/eqd.c: New file.
*
This is the latest patch set for adding TI PRU I/O processor backend to GCC.
Comments from all previous series have been addressed [1], [2], [3], [4], [5].
Test results can be downloaded from here:
http://dinux.eu/gnupru/testresults/20190607-c16eb7019be/
Changes since patch series v5 [5] are
PRU architecture supports maximum 256k program memory (IMEM). Some GCC
test cases manage to produce executables bigger than that.
gcc/testsuite/ChangeLog:
2019-06-07 Dimitar Dimitrov
* lib/gcc-dg.exp: Bail on region overflow for tiny targets.
* lib/target-utils.exp: Ditto.
So, this is probably the patch in GCC that's seen the longest delays
between different steps. :-o
On Mon, 30 Jan 2017, Jonathan Wakely wrote:
>> Thanks for doing that, Jonathan!
>>
>> Only one curious question: Why "Supported Releases" on our
>> main page versus "This release is no longer
On Thu, 30 May 2019, Jonathan Wakely wrote:
> I decided to make a few small changes, and ended up rewriting several
> sections. Committed to trunk.
Thank you! That also nicely addressed the changed URLs I had noticed.
Gerald
On Wed, 5 Dec 2018 21:10:45 +
Julian Brown wrote:
> Thanks for review! How's this version?
>
> I took the liberty of fixing the patch for Fortran array-descriptor
> mappings that use a PSET, also, and adding another test for that
> functionality.
This is a ping/new version of this patch,
doc/invoke.texi: Update fortran file locations.
---
gcc/doc/invoke.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 5e3e8873d35..f1d22e87cbc 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -29242,7 +29242,7 @@
In some interpretations "not...of all" may not be seen as
100% clear, so I propose to use "not...of any".
On the way fix the grammar in the next sentence.
Sandra, and Martin as the original author, does this makes
sense for you?
Gerald
2019-06-09 Gerald Pfeifer
* doc/extend.texi
This one ICEd but was, curiously, fixed very recently by r271811.
Tested x86_64-linux, applying to trunk.
2019-06-09 Marek Polacek
PR c++/60366
* g++.dg/cpp0x/lambda/lambda-ice32.C: New test.
diff --git gcc/testsuite/g++.dg/cpp0x/lambda/lambda-ice32.C
On 12/21/18 9:57 PM, Jonathan Wakely wrote:
On 29/10/18 07:06 +0100, François Dumont wrote:
Hi
Some feedback regarding this patch ?
Sorry this got missed, please resubmit during stage 1.
You haven't CC'd the original patch author (chang jc) to give them a
chance to comment on your
28 matches
Mail list logo
