I have committed the attach patch after testing on
i586-*-freebsd and x86_64-*-freebsd.
2019-06-15 Steven G. Kargl
* decl.c (gfc_match_derived_decl): Dummy argument cannot be a derived
type.
2019-06-15 Steven G. Kargl
* gfortran.dg/dummy_derived_typed.f90: New
On Mon, 10 Jun 2019, Martin Liška wrote:
> I'm fine with the Gerald. Thank you for it.
I went ahead and committed this, thanks.
Sandra, if you have any comments still happy to update.
Gerald
On Sun, 9 Jun 2019, Maya Rashish wrote:
> doc/invoke.texi: Update fortran file locations.
Thank you. I added a full ChangeLog entry and committed this to
trunk.
If I had more time, I'd push back to the GCC 9 branch as well;
anyone who wants to pick doc changes and push them?
Gerald
On 6/15/19 9:45 PM, Gerald Pfeifer wrote:
On Sun, 15 Jul 2018, Basile Starynkevitch wrote:
Basile, should we generally remove this reference to GCC MELT?
Yes. I am no more working on MELT, but I did begin to work on its successor:
Sorry for the delay - I finally applied the patch below.
On Sun, 15 Jul 2018, Basile Starynkevitch wrote:
>> Basile, should we generally remove this reference to GCC MELT?
> Yes. I am no more working on MELT, but I did begin to work on its successor:
Sorry for the delay - I finally applied the patch below.
If/when you want that successor to be listed
Continuing to clean out old patches. I've un-xfailed
a test for i?86-*-freebsd. This test has been passing
(at least on my laptop) for a very long time.
2019-06-15 Steven G. Kargl
* gfortran.dg/ieee/ieee_4.f90: Un-xfail on i?86-*-freebsd.
Index:
On Sat, Jun 15, 2019 at 04:33:26PM +0200, Jakub Jelinek wrote:
> On Sat, Jun 15, 2019 at 10:29:17AM -0400, Marek Polacek wrote:
> > [dcl.attr.noreturn] says "The first declaration of a function shall specify
> > the
> > noreturn attribute if any declaration of that function specifies the
> >
On Sat, Jun 15, 2019 at 10:29:17AM -0400, Marek Polacek wrote:
> [dcl.attr.noreturn] says "The first declaration of a function shall specify
> the
> noreturn attribute if any declaration of that function specifies the noreturn
> attribute" meaning that we should diagnose
>
> void func ();
>
[dcl.attr.noreturn] says "The first declaration of a function shall specify the
noreturn attribute if any declaration of that function specifies the noreturn
attribute" meaning that we should diagnose
void func ();
void func [[noreturn]] ();
but we do not. I'd been meaning to issue a hard
Use the CF-CFString.h, F-NS*.h proxy headers where needed in the objective-c++
testsuite. Make minor adjustments to tests as required, providing that those
do not alter the test intent.
applied to mainline
thanks
Iain
2019-06-15 Iain Sandoe
PR objc/90709
*
Use the CF-CFString.h, F-NS*.h proxy headers where needed in the objective-c
testsuite. Make minor adjustments to tests as required, providing that those
do not alter the test intent.
applied to mainline
thanks
Iain
2019-06-15 Iain Sandoe
PR objc/90709
*
Am Sa., 15. Juni 2019 um 12:52 Uhr schrieb Daniel Krügler
:
>
> Am Fr., 14. Juni 2019 um 16:05 Uhr schrieb Jonathan Wakely
> :
> >
> > These types are not constructible by design, so we never want warnings
> > for them, even with -Wsystem-headers.
> >
> > *
[ was: Re: [PATCH V8] Remove empty loop with assumed finiteness (PR
tree-optimization/89713) ]
On 12-06-19 11:42, Richard Biener wrote:
> On Tue, Jun 11, 2019 at 4:40 AM Feng Xue OS
> wrote:
>>
>> Reformat to comply with gcc coding style.
>
> OK for trunk.
>
Committed patch to update nvptx
Am Fr., 14. Juni 2019 um 16:05 Uhr schrieb Jonathan Wakely :
>
> These types are not constructible by design, so we never want warnings
> for them, even with -Wsystem-headers.
>
> * include/experimental/type_traits (experimental::nonesuch): Use
> pragma to disable
On 13-06-19 10:34, Jakub Jelinek wrote:
> Hi!
>
> The OpenMP specification isn't clear on this, I'll work on getting that
> clarified for 5.1, but the agreement on omp-lang has been that it should
> work the way the patch implements it, static block scope variables inside of
> #pragma omp target
Attached patch moves splitting of double-word patterns that do not
result in a special instructions when split (e.g. anddi ->
andsi/andsi, ...) before reload. Before STV pass was introduced, 32bit
targets didn't define double-mode patterns, so middle-end expanded
double-mode operations to
16 matches
Mail list logo
