Thanks a lot for the review, Richard!
- I have updated the patch.
- Had done a full "make check" with the
second draft.
- Did a "make check-gcc" with the final
patch.
- Both tests have the same tests
failing, that always fail:
g++.dg/pr80481.C
g++.dg/pr83239.C
Would be great if anyone willing
co
On Thursday, 9/13/2018 13:02:21 EEST Richard Sandiford wrote:
> Dimitar Dimitrov writes:
> > +(define_insn
> > "sub_impl_ > _zext_op2>" + [(set (match_operand:EQD 0 "register_operand" "=r,r,r")
> > + (minus:EQD
> > +(zero_extend:EQD
> > + (match_operand:EQS0 1 "reg_or_ubyte_operand" "r,
Yet another 'obvious' deferred character fix. Committed to trunk as
r264502. Will backport in about ten days time.
Paul
2018-09-22 Paul Thomas
PR fortran/85603
* trans-array.c (gfc_alloc_allocatable_for_assignment): Test
the charlen backend_decl before using the VAR_P macro.
2018
* Iain Buclaw:
> This patch adds part of the D2 testsuite, which includes D source code
> files that are considered compilable; files that are considered
> uncompilable, but should not ICE; and files that should execute on
> targets with crash or assertion failures.
>
> ftp://ftp.gdcproject.org/pa
On 22 September 2018 at 15:23, Florian Weimer wrote:
> * Iain Buclaw:
>
>> This patch adds part of the D2 testsuite, which includes D source code
>> files that are considered compilable; files that are considered
>> uncompilable, but should not ICE; and files that should execute on
>> targets with
I noticed this when pointing someone to this document. Clearly it
does not make much sense to have those empty sections which just
carry a title but no content, so I commented those (both in case
someone is adding material later, and also since this is going to
be used as a template for the GCC 9
Hello world,
the attached patch lets the middle-end know that variables
associated with intent(out) arguments become undefined, by
issuing an assignment to a special value (a "clobber")
before entering the procedure.
Originally, I had also planned to do so on entry to the
procedure, see https://
Committed as OKed by Janus on bugzilla.
Author: jvdelisle
Date: Sat Sep 22 17:49:19 2018
New Revision: 264505
URL: https://gcc.gnu.org/viewcvs?rev=264505&root=gcc&view=rev
Log:
2018-09-22 Jerry DeLisle
PR fortran/87318
* gfortran.dg/dtio_1.f90: Update test to valid code.
Mod
Minor typo, see below.
On 9/22/18 10:23 AM, Thomas Koenig wrote:
Hello world,
the attached patch lets the middle-end know that variables
associated with intent(out) arguments become undefined, by
issuing an assignment to a special value (a "clobber")
before entering the procedure.
Originally,
Hi Jeff.
I noticed that your commit r264328 introduced this:
gcc/builtins.c:
...
579tree rhs1 = gimple_assign_rhs1 (stmt);
580tree_code code = gimple_assign_rhs_code (stmt);
581if (code == ADDR_EXPR
582&& TREE_CODE (TREE_OPERAND (rhs1, 0)) == ARRAY
Hi Jerry,
s/tue/due/
a = 12345689 < missing 7 digit?
Yep, you're right. Corrected, committed as r264506.
Regards
Thomas
On Sep 05 2018, wrote:
> At present, pointers passed to builtin functions, including atomic operators,
> are stripped of their address space properties. This doesn't seem to be
> deliberate, it just omits to copy them.
>
> Not only that, but it forces pointer sizes to Pmode, which isn't appropri
It was recently noticed that for a few of the coarray intrinsics array
index calculations were done in integer_type_node instead of
gfc_array_index_type. This patch fixes this.
Regtested on x86_64-pc-linux-gnu, Ok for trunk?
gcc/fortran/ChangeLog:
2018-09-22 Janne Blomqvist
* trans-
On 9/22/18 8:32 PM, Martin Liška wrote:
Hi Jeff.
I noticed that your commit r264328 introduced this:
gcc/builtins.c:
...
579 tree rhs1 = gimple_assign_rhs1 (stmt);
580 tree_code code = gimple_assign_rhs_code (stmt);
581 if (code == ADDR_EXPR
582 &
14 matches
Mail list logo
