On September 15, 2015 7:39:39 PM GMT+02:00, Mike Stump
wrote:
>On Sep 14, 2015, at 3:37 PM, Jeff Law wrote:
>>> Maybe GCC-6 can bump the required
>>> dejagnu version to allow for getting rid of all these superfluous
>>> load_gcc_lib? *blink* :)
>> I'd support that as a direction.
>>
>> Certainl
On September 15, 2015 10:05:27 PM GMT+02:00, Jeff Law wrote:
>On 09/15/2015 01:21 PM, David Malcolm wrote:
>> On Tue, 2015-09-15 at 10:39 -0700, Mike Stump wrote:
>>> On Sep 14, 2015, at 3:37 PM, Jeff Law wrote:
> Maybe GCC-6 can bump the required
> dejagnu version to allow for getting ri
On September 16, 2015 7:57:03 PM GMT+02:00, Mike Stump
wrote:
>On Sep 16, 2015, at 9:25 AM, Ramana Radhakrishnan
> wrote:
>>
>> Sorry about the obvious (possibly dumb) question.
>
>> Can't we just import a copy of dejagnu each year and install it as
>part of the source tree?
>
>TL;DR: No.
>
>We
On September 16, 2015 7:39:42 PM GMT+02:00, David Malcolm
wrote:
>On Wed, 2015-09-16 at 10:36 -0600, Jeff Law wrote:
>> On 09/16/2015 10:25 AM, Ramana Radhakrishnan wrote:
>> >
>> >
>> > On 16/09/15 17:14, Mike Stump wrote:
>> >> On Sep 16, 2015, at 12:29 AM, Andreas Schwab
>> >> wrote:
>> >>> M
Trying to bootstrap m68k i hit an assert in emit_library_call_value_1
that wants to assure that the stack is aligned properly.
PUSH_ROUNDING(GET_MODE_SIZE(QImode)) for m5206 is currently 1 so
the testcase below has stack_pointer_delta = 1 + 1 + 4
but emit_library_call_value_1() has this:
/* Sta
On 11 September 2014 20:19:31 Jakub Jelinek wrote:
On Thu, Sep 11, 2014 at 07:26:37PM +0200, Jakub Jelinek wrote:
> right now. The patch below intends to serialize the content of the
> problematic *.exp tests (the first runtest to reach one of those will simply
> run all the tests from that *.
On 12 September 2014 19:46:33 Mike Stump wrote:
On Sep 12, 2014, at 9:32 AM, Jakub Jelinek wrote:
> Here is my latest version of the patch.
>
> With this patch I get identical test_summary output on make -k check
> (completely serial testing) and make -j48 -k check from toplevel directory.
>
>
On 13 September 2014 02:04:51 Jakub Jelinek wrote:
On Fri, Sep 12, 2014 at 04:42:25PM -0700, Mike Stump wrote:
> curious, when I run atomic.exp=stdatom\*.c:
>
> gcc.dg/atomic/atomic.exp completed in 30 seconds.
>
> atomic.exp=c\*.c takes 522 seconds with 3, 2, 5 and 4 being the worst
offende
On Tue, Sep 15, 2015 at 10:50:12PM +0200, Bernhard Reutner-Fischer wrote:
> On September 15, 2015 10:05:27 PM GMT+02:00, Jeff Law wrote:
> >On 09/15/2015 01:21 PM, David Malcolm wrote:
> >> On Tue, 2015-09-15 at 10:39 -0700, Mike Stump wrote:
> >>> On Sep 14, 201
On 16 May 2017 11:54:18 CEST, Jonathan Wakely wrote:
>On 13 May 2017 at 11:38, Jakub Jelinek wrote:
>> On Sat, May 13, 2017 at 12:24:12PM +0200, Bernhard Reutner-Fischer
>wrote:
>>> I guess neither redhat
>>> (https://access.redhat.com/downloads/content/dejagnu/ red
On 16 May 2017 at 14:16, Jonathan Wakely wrote:
> On 16 May 2017 at 13:13, Bernhard Reutner-Fischer wrote:
>> 1.5.0 wouldn't buy us anything as the "libdirs" handling is only in 1.5.2
>> and later.
>
> Ah I missed that in the earlier discussion.
>
>
On Tue, 16 May 2017 at 21:08, Mike Stump wrote:
>
> On May 16, 2017, at 5:16 AM, Jonathan Wakely wrote:
> > The change I care about in 1.5.3
>
> So, we haven't talked much about the version people want most. If we update,
> might as well get something that more people care about. 1.5.3 is in u
On 7 August 2018 18:34:30 CEST, Segher Boessenkool
wrote:
>On Mon, Aug 06, 2018 at 08:25:49AM -0700, Mike Stump wrote:
>> Since g++ already requires 1.5.3, it make no sense to bump to
>anything older that 1.5.3, so let's bump to 1.5.3. Those packaging
>systems and OSes that wanted to update by n
Bernhard Reutner-Fischer
*/
/*
This file is part of GCC.
GCC is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free
Software Foundation; either version 3, or (at your option) any later
version.
GCC is distributed in
On Tue, May 18, 2010 at 06:53:18PM -0500, Joel Sherrill wrote:
>Would there be a way to exclude specific files? Say something like
>config.h that by convention you might want every file to include?
Adding a
-fplugin-arg-warn_include-exclude-from=
should be doable, sure.
cheers,
On Tue, May 18, 2010 at 11:05:46PM +0200, Bernhard Reutner-Fischer wrote:
>Hi,
>Observations while thinking about all this:
[]
>- should figure out how to print a help-text for the plugin
> Hints?
>- should handle structs.
updated variant that handles functions a little bit
Hi,
blindvt: BTW since you have looked at this piece of code, you
may give me some advice:
on darwin* all the tests compiled with -g generate *.dSYM
folders. I'ld like to clean them.
Perhaps something like the attached? I find it a bit difficult to fit
that into the testsuite proper
On Mon, 7 Jun 2021 15:30:22 +0200
Martin Liška wrote:
> Anyway, this is resolved as I use more appropriate directive:
> https://splichal.eu/scripts/sphinx/gfortran/_build/html/intrinsic-procedures/access-checks-file-access-modes.html
ISTM there's a typo s/Tailing/Trailing/ in gcc/fortran/intrins
On Sat, 4 Aug 2018 18:32:24 +0200
Bernhard Reutner-Fischer wrote:
> On Tue, 16 May 2017 at 21:08, Mike Stump wrote:
> >
> > On May 16, 2017, at 5:16 AM, Jonathan Wakely wrote:
> >
> > > The change I care about in 1.5.3
> >
> > So, we haven't
From: Bernhard Reutner-Fischer
Bump required DejaGnu version to 1.5.3 (or later).
Ok for trunk?
gcc/ChangeLog:
* doc/install.texi: Bump required minimum DejaGnu version.
---
gcc/doc/install.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/install.texi b
On Wed, 12 Jan 2022 16:54:46 +0100
Martin Liška wrote:
> +def replace_file_in_changelog(lines, filename):
> +if not filename.endswith('.cc'):
> +return
> +
> +# consider all componenets of a path: gcc/ipa-icf.cc
> +while filename:
> +for i, line in enumerate(lines):
>
On 13 June 2022 17:26:59 CEST, Jonathan Wakely via Fortran
wrote:
>https://gist.github.com/jwakely/95b3a790157f55d75e18f577e12b50d7#file-build_gcc_versions-sh
s/[[/[/
s/==/=/
The former are deprecated or obsolescent notations of test(1) syntax, fwiw.
PS: we should rm https://gcc.gnu.org/git/?
On 17 June 2022 21:55:47 CEST, Jakub Jelinek wrote:
>On Fri, Jun 17, 2022 at 08:45:04PM +0200, Bernhard Reutner-Fischer via Gcc
>wrote:
>> PS: we should rm
>> https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=contrib/gcc_build
>
>No. gcc_build is used by maintainer-scripts/gc
On 26 April 2023 20:31:10 CEST, Florian Weimer via Fortran
wrote:
>* Martin Liška:
>
>> On 11/15/22 16:47, Martin Liška wrote:
>>> Hi.
>>>
>>> I've just pushed libsanitizer update that was tested on x86_64-linux and
>>> ppc64le-linux systems.
>>> Moreover, I run bootstrap on x86_64-linux and ch
On 28 April 2023 11:23:55 CEST, Florian Weimer via Fortran
wrote:
>* Martin Liška:
>But that's okay for me as well.
Even better.
[I was torn towards asking gcc@ only, individual i386 maintainers in
private or bluntly asking for help on gcc-patches or re-iterate through
ABI, so in an attempt to cut off years of latency i hereby ask all and
everybody for assistance. Stage4 means any chances are low, i know..
hence stage 1 mate
Hi Joseph!
On Tue, 30 Jan 2024 14:54:49 + (UTC)
Joseph Myers wrote:
> On Tue, 30 Jan 2024, Bernhard Reutner-Fischer via Gcc wrote:
>
> > * builtin-attrs.def (ATTR_TM_NOTHROW_RT_LIST): Use ATTR_NOTHROW_LIST
> > instead of ATTR_TM_NOTHROW_LIST, thus removi
27 matches
Mail list logo
