Re: [PATCH v2 2/3] or1k: testsuite: initial support for openrisc

On Oct 3, 2018, at 8:48 PM, Stafford Horne wrote: > > -mm-dd Stafford Horne > Richard Henderson > > gcc/testsuite/ChangeLog: > > * gcc.c-torture/execute/20101011-1.c: Adjust for OpenRISC. > * gcc.dg/20020312-2.c: Likewise. > * gcc.dg/attr-alloc_size-11.c:

Re: [PATCH, rs6000] Fix expected error output for test case.

On Oct 3, 2018, at 1:32 PM, Bill Seurer wrote: > > [PATCH, rs6000] Fix expected error output for test case. > > Is this ok for trunk? Ok.

Re: [PR 87339, testsuite] Fix failure of gcc.dg/warn-abs-1.c on some targets

On Sep 24, 2018, at 11:45 AM, Martin Jambor wrote: > > the test added to check whether _Float128 types are handled correctly by > the new warning about suspicious calls to abs-like functions fails on > many platforms. The patch below circumvents the problem by running on > i686/x86_64 only. I

Re: [PATCH 08/14] Add D2 Testsuite files.

On Sep 21, 2018, at 2:38 PM, Iain Buclaw wrote: > > On 21 September 2018 at 22:54, Mike Stump wrote: >> On Sep 17, 2018, at 5:36 PM, Iain Buclaw wrote: >>> >>> This patch adds part of the D2 testsuite, which includes D source code >>> file

Re: [PATCH 10/14] Add GDC Testsuite files.

On Sep 17, 2018, at 5:37 PM, Iain Buclaw wrote: > This patch adds a further number of tests, but were added as part of > fixing gdc-specific bugs. Ok. Trivial, and self-review applicable.

Re: [PATCH 08/14] Add D2 Testsuite files.

On Sep 17, 2018, at 5:36 PM, Iain Buclaw wrote: > > 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

Re: [PATCH 10/14] Add GDC Testsuite files.

On Sep 17, 2018, at 5:37 PM, Iain Buclaw wrote: > > This patch adds a further number of tests, but were added as part of > fixing gdc-specific bugs. Ok. Trivial, and self-review applicable.

Re: [PATCH 13/14] Add D Phobos standard library and license.

On Sep 19, 2018, at 1:49 PM, Iain Buclaw wrote: > > On 18 September 2018 at 02:38, Iain Buclaw wrote: >> This patch add the Phobos runtime library and license (Boost) files. >> Phobos is the standard runtime library that comes with the D language >> compiler. The bulk of which is comprised

Re: [PATCH 09/14] Add D2 Testsuite Dejagnu files.

On Sep 19, 2018, at 1:36 PM, Iain Buclaw wrote: > > On 18 September 2018 at 02:36, Iain Buclaw wrote: >> >> This patch adds D language support to the GCC testsuite. >> >> As well as generating the DejaGNU options for compile and link tests, >> handles the conversion from DMD-style compiler

Re: [PATCH 09/14] Add D2 Testsuite Dejagnu files.

Ok.

Re: [PATCH 22/25] Add dg-require-effective-target exceptions

On Sep 5, 2018, at 4:52 AM, a...@codesourcery.com wrote: > There are a number of tests that fail because they assume that exceptions are > available, but GCN does not support them, yet. So, generally we don't goop up the testsuite with the day to day port stuff when it is being developed. If

Re: [PATCH][OBVIOUS] Close file on return from verify-intermediate

On Sep 5, 2018, at 6:29 AM, Joey Ye wrote: > This is a fix to an obvious issue in gcov.exp, where proc verify-intermediate > returns without closing the open file. > > This can be a possible fix to PR85871. gcov-8.C diffs to other gcov testcases > that it invokes verify-intermediate. Not

Re: [PATCH, Darwin, config] Arrange for configure to detect "otool".

On Aug 30, 2018, at 8:45 AM, Iain Sandoe wrote: > > Currently, we fail to detect some Darwin assembler capabilities because the > configure tests rely on a BINUTILS objdump, which isn’t generally available > on Darwin. > > Darwin uses a tool called "otool" to provide information about objects,

Re: [PATCH, testsuite] Stringify __USER_LABEL_PREFIX__ in pr85248.

On Aug 21, 2018, at 7:20 AM, Iain Sandoe wrote: > > another missing stringify for _U_L_P_ > > OK? Ok. =

Re: [PATCH, Darwin] Do not run dsymutil automatically, when -save-temps is on the command line.

On Aug 18, 2018, at 1:17 PM, Iain Sandoe wrote: > > The point of running dsymutil automatically from collect2 is that it > (collect2, lto-wrapper, etc) might be generating or using compiler > temporary files that will be deleted at the end of the link process. > > dsymutil requires that it can

Re: [PATCH, Darwin, drivers] Split DWARF is not supported on Darwin.

On Aug 16, 2018, at 6:55 AM, Iain Sandoe wrote: > > The Darwin toolchains have a separate debug linker (dsymutil) so that the > link-time penalty for debug data is not usually seen. At present, it's not > clear how we would support split DWARF on Darwin (or if it would bring > any additional

Re: [PATCH,testsuite, Darwin] Skip tests with pthread_barrier.

On Aug 15, 2018, at 7:22 AM, Iain Sandoe wrote: > Darwin is stated to be SUSv6 compliant and, at that revision, pthread_barrier > is optional. > It is not implemented on any version at least up to Darwin18. > > This skips the tests currently attempted which use pthread_barrier. > > OK for

Re: [PATCH, testsuite] Fix PR78544 for Darwin.

On Aug 15, 2018, at 6:20 AM, Iain Sandoe wrote: > > The fails on Darwin are because the section naming convention is different. > > The patch adds Darwin-specific section attributes and a corresponding > target-specific scan-assembler clause. > > OK for trunk? > affected branches (7, 8)? Ok.

Re: [PATCH] Fix P81033 for FDEs in partitioned code.

On Aug 14, 2018, at 4:20 AM, Iain Sandoe wrote: > When function sub-sections are enabled, Darwin’s assembler needs the FDE > local start > label for each sub-section to follow a linker-visible one so that the FDE > will be correctly > associated with the code of the subsection. > > The current

Re: [PATCH, Darwin] Remove unnecessary target hook.

On Aug 13, 2018, at 1:55 PM, Iain Sandoe wrote: > For Darwin when we switch between text sections a linker-visible symbol is > required to preserve the linker’s “atom model”. Some time ago we implemented > TARGET_ASM_FUNCTION_SWITCHED_TEXT_SECTIONS to provide this. > > A suitable symbol is now

Re: [PATCH, Darwin, Obvious] Fix PR81685, by adding DWARF 5 section names.

On Aug 14, 2018, at 4:38 AM, Iain Sandoe wrote: > Where possible (i.e. they are currently defined), I’ve synced the Darwin > names with the ones > emitted by clang. Thanks.

Re: dejagnu version update?

On Aug 4, 2018, at 9:32 AM, 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 talked much about the version

Re: dejagnu version update?

On Aug 4, 2018, at 9:32 AM, 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 talked much about the version

Re: [RFC, testsuite/guality] Use relative line numbers in gdb-test

On Jun 28, 2018, at 12:39 PM, Tom de Vries wrote: > This patch adds a dg-final override that passes it's first argument to the > gdb-test action. This allows us to use relative line numbers in gdb-test. > > Tested pr45882.c. > > Any comments? > 2018-06-28 Tom de Vries > > *

Re: [RFC] Add gcc.dg-selftests/dg-final.exp

On May 30, 2018, at 3:41 AM, Tom de Vries wrote: > > this patch tests the error behaviour of dg-final directives when called with > an > incorrect number of arguments. Seems reasonable. Unless someone wanted to argue against it for some reason (not portable, takes too much time, hard to

Re: RFC: Disable asan tests under ulimit -v

On Mar 23, 2018, at 11:52 AM, Jason Merrill wrote: > > asan doesn't work under ulimit -v, which I want to use on shared hosts > to avoid causing trouble with runaway processes. There doesn't seem > to be a way within expect to access getrlimit/setrlimit, so in this > patch I

Re: [PATCH, GCC/testsuite] Fix FAIL display for some scan-*-times directives

On Mar 13, 2018, at 10:12 AM, Thomas Preudhomme wrote: > > scan-assembler-times and scan-tree-dump-times dejagnu directives show a > different output in the summary files depending on whether they PASS or > FAIL. This means that dg-cmp-results would not show a

Re: [PATCH][darwin] Work around missing LTO debug support for Mach-O, PR82005

On Mar 1, 2018, at 1:56 AM, Dominique d'Humières wrote: > >> Le 1 mars 2018 à 09:37, Richard Biener a écrit : >> >> In the PR Dominique says "With the patch the failures (-m32/-m64) went >> down from 1059 to 467" which is a nice improvement. I'm not set

Re: Please accept this commit for the trunk

On Feb 8, 2018, at 12:36 PM, Segher Boessenkool <seg...@kernel.crashing.org> wrote: > > On Wed, Feb 07, 2018 at 03:52:27PM -0800, Mike Stump wrote: >> I dusted the pointed to patch off and check it in. Let us know how it goes. > > I wanted to test this on the prima

Re: Please accept this commit for the trunk

On Feb 5, 2018, at 8:42 AM, Douglas Mencken wrote: > > I’m about > > “ [PATCH 2/4] [Darwin,PPC] Remove uses of LR in > restore_world ” https://gcc.gnu.org/bugzilla/attachment.cgi?id=42304 > > look at bug #84113 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 for >

Re: [testsuite] Make lto.exp work with Tcl 8.4

On Feb 5, 2018, at 9:54 AM, Richard Sandiford wrote: > > "dict" was added in Tcl 8.5, but until a couple of weeks ago the > testsuite has worked with 8.4. > > This patch uses arrays instead, like we do for the caching in > target-supports.exp. It is a bit uglier

Re: [PATCH] PR52665 do not let .ident confuse assembler scan tests

On Feb 2, 2018, at 5:25 AM, Bernhard Reutner-Fischer wrote: > > Given the overwhelming silence this proposal has received, i take it > for granted that folks are thrilled and even up until now speechless > :) > -fno-ident ok for stage1? > What about -fno-file? Clever

Re: [C++ PATCH] Deprecate ARM-era for scopes

On Jan 23, 2018, at 4:18 AM, Nathan Sidwell wrote: > > As discussed (https://gcc.gnu.org/ml/gcc-patches/2018-01/msg01778.html) this > patch deprecates the ARM-era for scope. The code gives: if you use %<-fpermissive%> G++ will accept your code I think we should no longer

Re: [PATCH][GCC][Testsuite] Have dg-cmp-results reject log files.

On Jan 23, 2018, at 2:31 AM, Tamar Christina wrote: > > This patch makes dg-cmp-results.sh reject the use of log files in the > comparison. No please. We like to run that script on log files from time to time for various reasons. I'd rather fix anything that

Re: [C++] Deprecate old for-scope handling

On Jan 19, 2018, at 2:53 PM, Nathan Sidwell wrote: > what do you think about deprecating the ARM-era for-scope handling I endorse this idea. :-) 20 years is enough for anyone to update their code, right? :-) smime.p7s Description: S/MIME cryptographic signature

Re: [PATCH, rs6000] Use $ instead of . for PC

On Jan 19, 2018, at 6:06 PM, Bill Schmidt wrote: > > I'm having a lot of heartburn over this because my test machine is > experiencing disk slowdowns, so it's taking me up to 4 hours to complete > a bootstrap and regression test. Ah, the joys of crosses, no

Re: [PATCH, GCC/testsuite] Fix dump-noaddr dumpbase

On Dec 5, 2017, at 12:56 PM, Thomas Preudhomme wrote: > > Thanks, I've tested after the two commits and it works both in tree and out > of tree. It'll simplify comparing in tree results Vs out of tree for us, > thanks a lot! > > Would you consider a backport

Re: [PATCH, GCC/testsuite] Fix dump-noaddr dumpbase

On Dec 5, 2017, at 11:11 AM, Thomas Preudhomme wrote: > > On 05/12/17 17:54, Andrew Pinski wrote: >> On Tue, Dec 5, 2017 at 9:50 AM, Thomas Preudhomme >> wrote: >>> Hi, >>> >>> dump-noaddr test FAILS when $tmpdir is not the same

Re: [PATCH, GCC/testsuite] Fix dump-noaddr dumpbase

On Dec 5, 2017, at 9:54 AM, Andrew Pinski wrote: > > On Tue, Dec 5, 2017 at 9:50 AM, Thomas Preudhomme > wrote: >> Hi, >> >> dump-noaddr test FAILS when $tmpdir is not the same as the directory >> where runtest is called from. Note that this

Re: [PATCH] Fix hot/cold partitioning with -gstabs{,+} (PR debug/81307)

On Nov 27, 2017, at 5:07 PM, Jim Wilson wrote: > There is also darwin9 support that apparently no one really cares about > anymore. I'm fine with removing stabs support from the compiler.

Re: Add -std=c18 etc. option aliases

On Nov 16, 2017, at 2:24 PM, Joseph Myers wrote: > > ISO C17 won't go to ballot until December, meaning publication of the > standard won't be until 2018, leaving ambiguity as to whether people > will end up referring to the standard as C17, as it's currently known > and

Re: bitfield types

On Nov 14, 2017, at 3:21 PM, Joseph Myers <jos...@codesourcery.com> wrote: > > On Tue, 14 Nov 2017, Mike Stump wrote: >> The testsuite/gcc.c-torture/execute/pr34971.c seems wrong to me. The >> type of the expression x.b << 8 has size 8, a size 8 inte

bitfield types

The testsuite/gcc.c-torture/execute/pr34971.c seems wrong to me. The type of the expression x.b << 8 has size 8, a size 8 integral type is a 64-bit type. If the result is a 64-bit type, then it's argument (x.b) was a 64-bit type. In C++, we observed what they meant in the C language

Re: [PATCH] Fixes for PR68356, PR81210, and PR81693

On Nov 14, 2017, at 3:33 AM, Dominique d'Humières <domi...@lps.ens.fr> wrote: > >> Le 13 nov. 2017 à 18:40, Mike Stump <mikest...@comcast.net> a écrit : >> On Nov 12, 2017, at 6:58 AM, H.J. Lu <hjl.to...@gmail.com> wrote: >>> >>> On Sun, Nov

Re: [PATCH] Fixes for PR68356, PR81210, and PR81693

On Nov 12, 2017, at 6:58 AM, H.J. Lu wrote: > > On Sun, Nov 12, 2017 at 6:22 AM, Dominique d'Humières > wrote: >> The following patch fixes PR68356, PR81210, and PR81693 on darwin. >> >> --- ../_clean/gcc/testsuite/gcc.dg/torture/pr68264.c2016-01-28

Re: [PATCH] Fix pr81706 tests on darwin

On Nov 12, 2017, at 6:05 AM, Dominique d'Humières wrote: > > The following patch fixes pr81706 tests on darwin > > --- ../_clean/gcc/testsuite/gcc.target/i386/pr81706.c 2017-10-26 > 07:16:18.0 +0200 > +++ gcc/testsuite/gcc.target/i386/pr81706.c 2017-11-11

Re: [PATCH] avoid -Wstringop-truncation in Darwin bootstrap

On Nov 10, 2017, at 12:36 PM, Martin Sebor wrote: > > The warning is included in -Wall Ah, I missed that little detail the first time around. -Wall is special in that we already just sanitize the source to pass it. I assumed it was a non-wall flag someone added or wanted

Re: [PATCH] avoid -Wstringop-truncation in Darwin bootstrap

On Nov 10, 2017, at 11:55 AM, Martin Sebor wrote: > A few not incorrect but not strictly intended (according to > the function's original purpose) uses of strncpy trigger the > new -Wstringop-truncation warning because they temporarily > leave the copied string without a

Re: [PATCH, GCC/testsuite] Fix retrieval of testname

On Nov 9, 2017, at 10:00 AM, Thomas Preudhomme wrote: > > When gcc-dg-runtest is used to run a test the test is run several times > with different options. For clarity of the log, the test infrastructure > then append the options to the testname. This means that

Re: [libstdc++, patch] Fix build on APFS file system

On Oct 18, 2017, at 7:51 AM, FX wrote: > > Parallel builds of libstdc++ on APFS filesystem (with 1 ns granularity) on > macOS 10.13 often fail (failure rate for “make -j2” to “make -j8” is about > 60% from my own builds and results reported by others): >

Re: [patch] implement generic debug() functions for wide_int's

On Oct 18, 2017, at 10:08 AM, Aldy Hernandez wrote: > > It looks like the generic debug() function for wide_int's is missing. > OK for trunk? Ok.

Re: [patch] avoid printing leading 0 in widest_int hex dumps

On Oct 17, 2017, at 5:18 AM, Richard Sandiford wrote: > > Aldy Hernandez writes: >> This produces confusing dumps to say the least > That's the intended behaviour though. > 0x0 -> (1 << 32) - 1 to infinite precision >

Re: [openacc, testsuite, committed] Enable libgomp.oacc-*/declare-*.{c,f90} for non-nvidia devices

On Oct 17, 2017, at 8:34 AM, Tom de Vries wrote: > >>> OK, if full testing is ok? >> I believe this was fully intentional and the presence/absence of >> explicit dg-do run can then be used to decide if it should loop through >> options or not. > > I don't see an explicit

Re: [PATCH, testsuite] Add dg-require-stack-size

On Oct 16, 2017, at 3:16 AM, Tom de Vries wrote: > > I noticed gcc.dg/tree-ssa/ldist-27.c failing for nvptx due to a too large > stack size. > OK for trunk? Hum. There is an existing mechanism (find-grep STACK_SIZE) in the tree to handle the same issue. Did you

Re: Allow non-wi wi

> On Oct 6, 2017, at 2:35 AM, Richard Sandiford > wrote: > > Richard Biener writes: >> On Tue, Oct 3, 2017 at 8:34 PM, Richard Sandiford >> wrote: >>> This patch uses global rather than member operators

Re: [GCC][PATCH][TESTSUITE][ARM][COMMITTED] Invert check to misalign in vect_hw_misalign (PR 78421)

On Oct 6, 2017, at 5:48 AM, Tamar Christina wrote: > > I'm looking for permission to backport this patch to the gcc-7 branch to fix > the failing tests there as well. Ok.

Re: [GCC][PATCH][TESTSUITE][ARM][COMMITTED] Invert check to misalign in vect_hw_misalign (PR 78421)

On Sep 25, 2017, at 9:58 PM, Christophe Lyon wrote: > > Yes, thanks! I was missing the 'expr' part. > > Here is what I have committed (r253187), to avoid further noise in the > results. Yup, looks good. Thanks.

Re: [GCC][PATCH][TESTSUITE][ARM][COMMITTED] Invert check to misalign in vect_hw_misalign (PR 78421)

On Sep 23, 2017, at 10:52 AM, Christophe Lyon wrote: > The attached patch would apply after reverting yours. > I've applied it against r253072 (just before your patch) and the > results are visible at: >

Re: [PATCH] PR target/80556

On Sep 22, 2017, at 2:55 AM, Iain Sandoe wrote: > >> On 18 Sep 2017, at 22:08, Simon Wright wrote: >> >> On 18 Sep 2017, at 21:09, Iain Sandoe wrote: >>> > If I propose this alternative patch, should it be a new post, or

Re: [PATCH 1/2] (header usage fix) remove unused system header includes

I was hoping an RM would approve this as it seems just a hair beyond a normal darwin approval. I'm fine with this, and it does help darwin. Other ports should not care. On Sep 18, 2017, at 10:30 AM, Jack Howarth wrote: > > Pinging for the final gcc 5.5 release. >

Re: [PATCH 0/2] backport c++ header fixes to gcc-5-branch

I was hoping an RM would approve this as it seems just a hair beyond a normal darwin approval. I'm fine with this, and it does help darwin. Other ports should not care. On Sep 18, 2017, at 10:31 AM, Jack Howarth wrote: > > Pinging for the final gcc 5.5 release. >

Re: [C++ PATCH] Renames/adjustments of 1z to 17

On Sep 14, 2017, at 1:26 PM, Jakub Jelinek wrote: > > Given https://herbsutter.com/2017/09/06/c17-is-formally-approved/ > this patch makes -std=c++17 and -std=gnu++17 the documented options > --- gcc/doc/invoke.texi.jj2017-09-12 21:57:57.0 +0200 > +++

Re: [PATCH 6/13] D: Add D language support to GCC proper.

On Sep 11, 2017, at 9:34 AM, Jeff Law wrote: > > On 05/28/2017 03:15 PM, Iain Buclaw wrote: >> This patch adds D language support to GCC itself. >> >> --- >> >> >> 06-d-gcc-proper.patch >> >> >> gcc/ChangeLog >> >> * config/rs6000/rs6000.c

Re: [doc,libgomp] Updates for www.openacc.org URLs

On Sep 8, 2017, at 5:27 AM, Gerald Pfeifer wrote: > > I committed the patch below, but am wondering whether we really, > really, really need as many instances of one and the same URL in > one section of the documentation? Can we simplify this somehow? Curious that they

Re: [PATCH v2] Python testcases to check DWARF output

On Sep 4, 2017, at 2:22 AM, Pierre-Marie de Rodat wrote: > > I would like to ping for the patch I submitted at > . Thank you in > advance! I've included the dwarf people on the cc list. Seems like they may have an

Re: [TESTSUITE]Use strncpy instead of strcpy in testsuite/gcc.dg/memcmp-1.c

On Aug 30, 2017, at 8:31 AM, Renlin Li wrote: > memcpy is better than strncpy in this case. > Here is the updated patch. Ok.

Re: [PATCH] [docs] Explain how to use multiple file-name patterns in RUNTESTFLAGS

On Aug 22, 2017, at 11:53 AM, Daniel Santos wrote: > > OK, the problem is at line 4014 of gcc/Makefile.in: > > $(MAKE) TESTSUITEDIR="$(TESTSUITEDIR)" > RUNTESTFLAGS="$(RUNTESTFLAGS)" \ >check-parallel-$* \ So, this is typical of sh scripting. Most

Re: [PATCH] [docs] Explain how to use multiple file-name patterns in RUNTESTFLAGS

On Aug 22, 2017, at 10:44 AM, Daniel Santos wrote: > > OK, how's this one? Ok.

Re: Remove the frame size argument from function_prologue/epilogue

On Aug 21, 2017, at 4:12 AM, Richard Sandiford wrote: > > Later patches will add support for frame sizes that are a run-time > invariant but not a compile-time constant. I'm assuming dwarf and C++ exceptions will remain working. :-)

Re: [PATCH] [docs] Explain how to use multiple file-name patterns in RUNTESTFLAGS

On Aug 22, 2017, at 10:32 AM, Daniel Santos wrote: > >> I would suggest "escaped or quoted." >> The whole argument to RUNTESTFLAGS can be quoted in either single >> or double quotes and, AFAICT, so can the space-separated test >> names within it. > > Well,

Re: [PATCH] [docs] Explain how to use multiple file-name patterns in RUNTESTFLAGS

On Aug 22, 2017, at 8:58 AM, Martin Sebor wrote: > > On 08/21/2017 07:41 PM, Daniel Santos wrote: >> It took me a while to figure out how to do this so I figured that it should >> be >> in the docs. OK for trunk? Oh, yeah, with the correction mentioned, Ok.

Re: [PATCH] [docs] Explain how to use multiple file-name patterns in RUNTESTFLAGS

> On Aug 22, 2017, at 8:58 AM, Martin Sebor wrote: > > On 08/21/2017 07:41 PM, Daniel Santos wrote: >> It took me a while to figure out how to do this so I figured that it should >> be >> in the docs. OK for trunk? >> >> * doc/install.texi: Add more details on

Re: [PATCH] Fix building of cross compiler (PR target/81753).

On Aug 15, 2017, at 6:35 AM, Martin Liška wrote: > > Simple fix for the PR where we wrongly combine extra_objs. > Ready to install the patch? Ok. > PR target/81753 > * config.gcc: Respect previously set extra_objs in case > of darwin target.

Re: [testsuite, i386] Require -static support in gcc.dg/pie-static-[12].c (PR testsuite/81793)

On Aug 12, 2017, at 9:03 AM, Rainer Orth wrote: > > The new gcc.dg/pie-static-[12].c testcases FAIL on several systems: > > * Solaris 11.4 has PIE support, but lacks static libc, libm > > * Linux without the static libc, libm installed > > The following patch

Re: [PATCH][testsuite] Add check_effective_target_autoincdec

On Aug 9, 2017, at 5:50 AM, Richard Earnshaw (lists) wrote: > > On 09/08/17 12:37, Wilco Dijkstra wrote: >> Richard Earnshaw wrote: >>> Except that I think this would be better done as an 'effective target' >>> test; something like >>> >>> dg-require-effective-target

Re: [PATCH 0/2] Python testcases to check DWARF output

On Jul 27, 2017, at 2:07 AM, Pierre-Marie de Rodat wrote: > On 07/27/2017 09:52 AM, Richard Biener wrote: >>> I'm fine with the direction if a reviewer wants to go in that >>> direction. I wish python didn't have a built-in speed penalty, >>> that's the only downside I don't

Re: RFC [testsuite] Obey --load-average

On Aug 2, 2017, at 10:34 PM, Daniel Santos wrote: > > I'm working on a patch to modify the testsuite to obey the > --load-average value if one is passed to make. The code seems like a reasonable approach. Love to see numbers and test scenarios so that others can tell

Re: [PATCH v2 9/13] D: D2 Testsuite Dejagnu files.

On Jun 24, 2017, at 10:52 AM, Iain Buclaw wrote: > Added a few extra comments for procedures, altering dmd2dg to write > out flags converted to dejagnu in-place, instead on newlines. > > In the other testsuite patch, added new tests to accompany fixes that > have been

Re: [PATCH 0/2] Python testcases to check DWARF output

On Jul 26, 2017, at 9:00 AM, Pierre-Marie de Rodat wrote: > At the last GNU Cauldron, Richard Biener and I talked about DWARF output > testing. Except for guality tests, which are disabled on several > targets, the only way tests check the DWARF is scanning the annotated >

Re: [PATCH 12/17] Add server.h and server.c

On Jul 26, 2017, at 7:50 AM, David Malcolm wrote: > > On Wed, 2017-07-26 at 23:35 +0900, Oleg Endo wrote: >> On Mon, 2017-07-24 at 16:05 -0400, David Malcolm wrote: >>> >>> + >>> +You should have received a copy of the GNU General Public License >>> +along with GCC; see the

Re: [PATCH 1/2] simplify-rtx: The truncation of an IOR can have all bits set (PR81423)

On Jul 25, 2017, at 3:10 PM, Segher Boessenkool wrote: > > On Tue, Jul 25, 2017 at 12:30:13PM +0100, Kyrill Tkachov wrote: >> We sometimes use the __mode__ attribute to force certain sizes in C types. >> For example: typedef int ditype __attribute__ ((mode (DI))); >>

Re: Deprecate DBX/stabs?

On Jul 21, 2017, at 9:03 AM, Jim Wilson wrote: > There is also the matter of SDB_DEBUG which is still supported, and is > no longer used by anyone, as we have already deprecated all of the > COFF targets that were using it. SDB support for C++ is even worse > than the DBX

Re: Deprecate DBX/stabs?

On Jul 21, 2017, at 6:07 AM, Nathan Sidwell wrote: > > [darwin, cygwin, rx maintainers, you might have an opinion] darwin going forward is a DWARF platform, so, shouldn't be a heartache for real folks. For ancient machines, ancient compilers might be a requirement.

Re: PING: [PATCH v2 0/2] [testsuite, libgcc] PR80759 Fix FAILs on Solaris and Darwin

On Jul 17, 2017, at 9:16 AM, Daniel Santos wrote: > > https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00025.html > Mike or Iain, > Can one of you review changes for Darwin please? Ok.

Re: [PATCH][PING] Improve extraction of changed file in contrib/mklog

On Jul 17, 2017, at 12:22 AM, Yuri Gribov wrote: > > Currently mklog will fail to analyze lines like this in patches: > diff -rupN gcc/gcc/testsuite/lib/profopt.exp > gcc-compare-checks/gcc/testsuite/lib/profopt.exp > (it fails with "Error: failed to parse diff for ... and

Re: [PATCH] Print relative names in UNSUPPORTED AutoFDO tests

On Jul 9, 2017, at 12:00 PM, Yuri Gribov wrote: > > This patch fixes AutoFDO Dejagnu tests to print relative filenames > instead of absolute ones when AutoFDO is unsupported. This is to > prevent spurious differences in dg-cmp-results.sh, like this: > NA->UNSUPPORTED: >

Re: [PATCH] Ignore random output from Asan tests in dg-cmp-results

On Jul 10, 2017, at 2:21 PM, Mike Stump <mikest...@comcast.net> wrote: > > Someone with such a system will have to drill down into why. Found it, fixed in dejagnu 1.5.3, just use a newer dejagnu, 1.5.3 or later should be fine. Apparently, I should have just checked it _first

Re: [PATCH] Ignore random output from Asan tests in dg-cmp-results

On Jul 10, 2017, at 2:44 AM, Yuri Gribov wrote: > > On Mon, Jul 10, 2017 at 10:32 AM, Thomas Preudhomme > wrote: >> Hi Yuri, >> >> On 09/07/17 20:06, Yuri Gribov wrote: >>> >>> Hi, >>> >>> Currently dg-cmp-results fails to compare fails in

Re: [PATCH] Ignore random output from Asan tests in dg-cmp-results

On Jul 9, 2017, at 12:06 PM, Yuri Gribov wrote: > > Currently dg-cmp-results fails to compare fails in Asan tests because > their output includes failing process id: > NA->FAIL: c-c++-common/asan/bitfield-1.c -O0 output pattern test, > is ==18161==ERROR > FAIL->NA:

Re: [PATCH] gcc/doc: list what version each attribute was introduced in

On Jul 7, 2017, at 10:01 AM, Jeff Law wrote: > > On 07/06/2017 07:25 AM, Daniel P. Berrange wrote: >> There are several hundred named attribute keys that have been >> introduced over many GCC releases. Applications typically need >> to be compilable with multiple GCC versions,

Re: [PATCH] PR target/80556

On Jun 9, 2017, at 6:57 AM, Simon Wright wrote: > > This PR was raised because of a bootstrap failure on Darwin. > A question: I've checked for x86_64-apple-darwin*, is this OK or > should it be more restrictive? That seems ok. Ok. If anyone sees any fallout from this,

Re: [Patch testsuite]

On Jun 26, 2017, at 1:56 PM, Dominique d'Humières <domi...@lps.ens.fr> wrote: > >> Le 26 juin 2017 à 20:35, Mike Stump <mikest...@comcast.net> a écrit : >> On Jun 26, 2017, at 2:26 AM, Dominique d'Humières <domi...@lps.ens.fr> wrote: >>> >>>

Re: [Patch testsuite]

On Jun 26, 2017, at 11:35 AM, Rainer Orth <r...@cebitec.uni-bielefeld.de> wrote: > > Mike Stump <mikest...@comcast.net> writes: > >> On Jun 26, 2017, at 2:34 AM, Rainer Orth <r...@cebitec.uni-bielefeld.de> >> wrote: >>> >>

Re: [Patch testsuite]

On Jun 26, 2017, at 2:26 AM, Dominique d'Humières wrote: > > Is it OK to commit the following patch (darwin only)? Ok. As for [0-9a-f]*ing the numbers, at least 1 of test cases should retain the actual number check. I'm fine with the resting being an RE, if someone wants

Re: [Patch testsuite]

On Jun 26, 2017, at 2:34 AM, Rainer Orth wrote: > >> Is it OK to commit the following patch (darwin only)? > > this patch needs a ChangeLog entry (and preferably a description of the > problem you're fixing ;-) Actually, the CL isn't required, testsuite is

Re: [PATCH v2 9/13] D: D2 Testsuite Dejagnu files.

On Jun 24, 2017, at 10:52 AM, Iain Buclaw wrote: > > On 28 May 2017 at 23:16, Iain Buclaw wrote: >> This patch adds D language support to the GCC testsuite. >> >> As well as generating the DejaGNU options for compile and link tests, >> handles

Re: [committed] Fix -fstack-check with really big frames on aarch64

On Jun 22, 2017, at 10:21 AM, Jeff Law wrote: > > This time with the test. Just #includes 20031023-1.c with a suitable dg > directive to ensure we compile with -fstack-check. > > I won't be surprised if other targets fail this test. It's a really big > stack frame :-) The

Re: [PATCH][RFA] Fix -fstack-check with really big frames on aarch64

On Jun 22, 2017, at 8:32 AM, Jeff Law wrote: > > Sure. I'll do something with 20031023-1.c to ensure it or an equivalent > is compiled with -fstack-check. That isn't totally unexpected. I > would have also been receptive to adding -fstack-check to the torture flags. Ouch.

Re: [PATCH, GCC/contrib] Fix variant selection in dg-cmp-results.sh

On Jun 21, 2017, at 8:30 AM, Thomas Preudhomme wrote: > > Commit r249422 to dg-cmp-results.sh broke the variant selection feature > 2017-06-21 Thomas Preud'homme > > * dg-cmp-results.sh: Restore filtering on target variant. >

Re: [PATCH, contrib] Support multi-tool sum files in dg-cmp-results.sh

On Jun 20, 2017, at 8:31 AM, Thomas Preudhomme wrote: > > 2017-06-14 Thomas Preud'homme > > * dg-cmp-results.sh: Keep test result lines rather than throwing > header and summary to support sum files with multiple tools.

<    1   2   3   4   5   6   7   8   9   10   >