Re: [hsa, testsuite] Suppress hsa warnings in libgomp tests

On Mar 1, 2016, at 10:47 AM, Jakub Jelinek wrote: > What is the difference betwee the $flags and $default-extra-cflags > arguments to dg-runtest? You seem to stick -Wno-hsa into the former, > which to me looks like it will be mentioned as part of the test > names (e.g. when

Re: [hsa, testsuite] Suppress hsa warnings in compiler gomp tests

On Mar 1, 2016, at 10:40 AM, Martin Jambor wrote: > as Jakub requested in another thread, this patch deals with HSA > "excess errors" in the gomp compiler testsuite by passing -Wno-hsa to > all of them. > OK for trunk? Ok.

Re: [testsuite] Invoke gdb with -batch to avoid prompts

On Mar 1, 2016, at 6:20 AM, Rainer Orth wrote: > When switching from gdb 7.10 to the newly released gdb 7.11 on Solaris, > all simulate-thread tests started to timeout Ok. If a domain expert prefers a different strategy, I’m fine with anything better as well.

Re: [hsa merge 08/10] HSAIL BRIG description header file

On Feb 26, 2016, at 10:58 AM, Martin Jambor wrote: > I have asked HSA foundation Thanks. > The license is going to be: > > The MIT License (MIT) Wonderful.

Re: [PATCH] libffi testsuite: Use split to ensure valid tcl list

On Feb 25, 2016, at 11:10 AM, Thomas Schwinge wrote: > +set lines [libffi_target_compile $src /dev/null assembly “"] Does this work on a dos box, or windows or other random non-posix systems?

Re: [Patch, testsuite] Require int32 target support in sso tests

On Feb 22, 2016, at 11:52 PM, Senthil Kumar Selvaraj wrote: > > Yes that works Ok. Committed revision 233621. Scream if anything goes wrong. Thanks for testing.

Re: [Patch, testsuite] Require int32 target support in sso tests

On Feb 5, 2016, at 1:03 AM, Eric Botcazou wrote: > You probably need to tweak the regexps again to make it accept the ^M. So, it turned out to the the last line of the file and prune. I’ve fixed it by merely adding an extra line to the end, so that the regexps work as

Re: [Patch, testsuite] Require int32 target support in sso tests

On Feb 22, 2016, at 12:41 AM, Senthil Kumar Selvaraj wrote: > Could someone commit it for me please? I don't have commit access. Could you test out: Index: sso.exp === --- sso.exp (revision

Re: [PATCH][RFC][Offloading] Fix PR68463

On Feb 19, 2016, at 6:53 AM, Jakub Jelinek wrote: > Looking at this, I think I have no problem with crtoffloadbegin.o being > included in all -fopenmp/-fopenacc linked programs/shared libraries, :-) I have a problem with just the normal init path in most executables. It adds

Re: [RFC, PR68580] Handle pthread_create error in tsan testsuite

On Feb 15, 2016, at 3:29 AM, Bernd Edlinger wrote: > And independently of that I am looking at using llvm's test.h framework > instead > of gcc's test_barrier.h for gcc-7 soon. Here’s to hoping that we don’t back slide on:

Re: TR29124 C++ Special Maths - Make pull functions into global namespace.

On Feb 12, 2016, at 1:01 PM, Jonathan Wakely wrote: > OK, thanks. t double checked the log file: -D__STDCPP_WANT_MATH_SPEC_FUNCS__ -DMAX_ITERATIONS=5 which I neglected to do the first time. With that check looking good as well, I checked it in, thanks.

Re: TR29124 C++ Special Maths - Make pull functions into global namespace.

On Feb 12, 2016, at 10:07 AM, Jonathan Wakely <jwak...@redhat.com> wrote: > On 12/02/16 09:52 -0800, Mike Stump wrote: >> On Feb 11, 2016, at 3:57 AM, Jonathan Wakely <jwak...@redhat.com> wrote: >>> On 10/02/16 22:36 -0800, Mike Stump wrote: >>>>

Re: TR29124 C++ Special Maths - Make pull functions into global namespace.

I’m seeing: /home/mrs/work1/gcc/libstdc++-v3/testsuite/special_functions/18_riemann_zeta/check_value.cc: In function 'void test(const testcase_riemann_zeta (&)[Num], Tp)': /home/mrs/work1/gcc/libstdc++-v3/testsuite/special_functions/18_riemann_zeta/check_value.cc:285:15: error: 'riemann_zeta'

testsuite fix

I’m running the pretty printer test cases on a target with status wrappers, and that system works by printing the return code on that output. It is dependent upon the last line being terminated by “\n”, as the code that looks for the return code requires the return code at the start of a line.

Re: [PATCH] Make C++ use the enum mode attribute

On Feb 6, 2016, at 2:37 PM, Trevor Saunders wrote: > it is allowed if you do something like > > enum X : int; > > but it seems really pointless to support setting the size of something > when the language gives you a standard way to do that. Yes, it is, as long as you

Re: [PATCH] Make C++ use the enum mode attribute

On Feb 6, 2016, at 12:36 PM, Bernd Edlinger wrote: > If that patch is not appropriate for stage 4 Without looking at the patch, fixes to abi incompatibilities I think are important. Would be nice to fix them. [ ok, I peeked at the patch ] Wow, nice, short and

Re: [Patch, testsuite] Require int32 target support in sso tests

On Feb 4, 2016, at 5:46 AM, Senthil Kumar Selvaraj wrote: > When running the regression testsuite for the AVR target, I noticed a > bunch of sso tests failing > If this patch is ok, could someone commit please? The patch is Ok. I don’t recall a target

Re: [PATCH] fix #69251 - [6 Regression] ICE in unify_array_domain on a flexible array member

On Feb 4, 2016, at 10:23 AM, Martin Sebor wrote: > Yes, I sure did! (But no, it wasn't obvious to me. I recently > upgraded this machine and did it differently than I normally do, > so things are, well, different than I expected. FWIW, it would > be nice to mention this as

Re: [PATCH] fix #69251 - [6 Regression] ICE in unify_array_domain on a flexible array member

On Feb 4, 2016, at 7:32 AM, Martin Sebor wrote: > FWIW, I keep having trouble with the repository. > $ svn switch --relocate svn://gcc.gnu.org/svn/gcc > svn+ssh://mse...@gcc.gnu.org/svn/gcc > svn: E170013: Unable to connect to a repository at URL >

Re: [Patch, MIPS] Fix PR target/68273, passing args in wrong regs

On Feb 3, 2016, at 2:30 PM, Steve Ellcey wrote: > Here is a new patch for PR target/68273. So this doesn’t fix aarch64, c6x, epiphany, ia64, iq2000, rs6000, rx, sparc, tilegx, tilepro or xtensa. :-( That’s one of the problems by having each port copy and paste swaths of

random struct-layout-1 link failures caused by timeouts

I added dg-timeout-factor support to compat.exp, so that one can use it in struct-layout-1.exp test cases. To use it, one can do something like: diff --git a/gcc/testsuite/gcc.dg/compat/struct-layout-1_generate.c b/gcc/testsuite/gcc.dg/compat/struct-layout-1_generate.c index 80c7355..bc34f2a

Re: [PATCH] [wwwdocs] Add common C++ issues to /gcc-6/porting_to.html

On Feb 3, 2016, at 2:03 PM, Jonathan Wakely wrote: > Yes, there are *dozens* of packages that fail to build due to "return > false;" in a function that returns a pointer of some kind. Wow, curious. Anyway, that removes my objection.

Re: [PATCH] [graphite] document that isl-0.16 is supported

On Feb 2, 2016, at 10:29 PM, Sebastian Huber wrote: > If it is so basic to choose the latest release or the one on the system, then > why uses the contrib/download_prerequisites ancient versions, e.g. the six > year old GMP 4.3.2? Because no one has seen

Re: [PATCH] [wwwdocs] Add common C++ issues to /gcc-6/porting_to.html

On Feb 3, 2016, at 9:13 AM, David Malcolm wrote: >> +pointer constants, so other constants such as false and >> +(1 - 1) cannot be used where a null pointer is desired. So, I’d leave this out entirely. The subject is porting, not the fine detail pedanticism only a language

Re: [PATCH] [graphite] document that isl-0.16 is supported

On Feb 2, 2016, at 2:23 AM, Sebastian Huber wrote: > It would be good to have a recommended version as well (similar for cloog, > gmp, mpc and mpfr). If you present me three versions which one should I > choose as a naive user? The latest release, or the

Re: [Patch,microblaze]: Better register allocation to minimize the spill and fetch.

On Jan 29, 2016, at 2:31 AM, Ajit Kumar Agarwal wrote: > > This patch improves the allocation of registers in the given function. Is it just me, or, would it be even better to change the abi and make MB_ABI_ASM_TEMP_REGNUM be allocated by the register allocator?

Re: [PATCH] [graphite] document that isl-0.16 is supported

On Jan 29, 2016, at 8:10 AM, Sebastian Pop wrote: > diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi > index 062f42c..3df7974 100644 > --- a/gcc/doc/install.texi > +++ b/gcc/doc/install.texi > @@ -383,7 +383,7 @@ installed but it is not in your default library search >

Re: new port: vn8

On Jan 27, 2016, at 7:12 PM, Bernhard Reutner-Fischer <rep.dot@gmail.com> wrote: > On January 27, 2016 8:47:15 PM GMT+01:00, Mike Stump <mikest...@comcast.net> > wrote: >> On Jan 26, 2016, at 10:33 PM, Nguyễn Sinh Ngọc >> <ngoc.nguyens...@icdrec.edu.vn>

Re: new port: vn8

On Jan 26, 2016, at 10:33 PM, Nguyễn Sinh Ngọc wrote: > I wonder that what paper is? > Is it an introduction about new feature in our target? I was not able to make any sense of these two question. Likely a language barrier. If you can find a way to rephrase

Re: [PATCH, testsuite] Fix g++.dg/pr67989.C test failure when running with -march or -mcpu

On Jan 26, 2016, at 10:35 PM, Thomas Preud'homme wrote: > On Monday, January 18, 2016 11:33:47 AM Thomas Preud'homme wrote: >> On Wednesday, January 13, 2016 06:39:20 PM Bernd Schmidt wrote: >>> On 01/12/2016 08:55 AM, Thomas Preud'homme wrote: On Monday,

Re: [PATCH, testsuite]: Disable some tests in gcc.dg/torture/pr68264.c for older glibcs

On Jan 27, 2016, at 12:58 AM, Uros Bizjak wrote: > 2016-01-27 Uros Bizjak > >* gcc.dg/torture/pr68264.c: Disable log1p test for glibc < 2.22 >and expm1 test for glibc < 2.11. > > Tested on x86_64-linux-gnu, CentOS 5.11 and Fedora 23. > > OK for

Re: new port: vn8

On Jan 27, 2016, at 7:36 PM, Sandra Loosemore wrote: > Where is the patch under discussion here? I can't find it in the archives. It was 500+K after compression. The port didn’t seem terribly large to me.

Re: [PATCH] Fix up wi::lrshift (PR c++/69399)

On Jan 26, 2016, at 10:21 AM, Jakub Jelinek wrote > The question is, shall we do what wi::lshift does and have the fast path > only for the constant shifts, as the untested patch below does, or shall we > check shift dynamically (thus use > shift < HOST_BITS_PER_WIDE_INT >

Re: [C++ PATCH] Handle error_mark_node in cp_fold (alt; PR c++/68357)

On Jan 26, 2016, at 8:39 AM, Jakub Jelinek wrote: > On Tue, Jan 26, 2016 at 02:56:24PM +0100, Jakub Jelinek wrote: >> Another alternative would be to make sure tree folders don't introduce >> error_mark_node (if it wasn't there already), but instead fold the call say >> to

Re: [PATCH] Fix up wi::lrshift (PR c++/69399)

On Jan 26, 2016, at 12:45 PM, Richard Biener wrote: > The original reasoning was to inline only the fast path if it is known at > compile time and otherwise have a call. Exactly to avoid bloating callers > with inlined conditionals. That’s part of it. And

Re: [PATCH] Fix up wi::lrshift (PR c++/69399)

On Jan 26, 2016, at 1:26 PM, Jakub Jelinek wrote: > will do cc1plus size comparison afterwards. We know the dynamic check is larger. You can’t tell the advantage of speed from size. Better would be to time compiling any random large translation unit. Nice to see that only

new port: vn8

I don’t see the point of libgcc/config/vn8/test.patch. I suspect either you need to apply it to your diffs before you send them out, or remove the file a junk from the diff set. I saw: inflating: libgcc/config/vn8/lib1funcs-fixed.S inflating: libgcc/config/vn8/lib1funcs-fixed.S.old

Re: gomp_target_fini

On Jan 22, 2016, at 2:16 AM, Jakub Jelinek wrote: > On Thu, Jan 21, 2016 at 04:24:46PM +0100, Bernd Schmidt wrote: >> Thomas, I've mentioned this issue before - there is sometimes just too much >> irrelevant stuff to wade through in your patch submissions, and it >> discourages

Re: [PATCH, AArch64] Fix for PR67896 (C++ FE cannot distinguish __Poly{8,16,64,128}_t types)

On Jan 25, 2016, at 4:15 AM, James Greenhalgh wrote: P.S.: I haven't signed the copyright assignment to the FSF. The change is really small but I can do the paperwork if required. > > I can't commit it on your behalf until we've heard back regarding whether >

Re: [PATCH 1/5] s390: Use proper read-only data section for literals.

On Jan 20, 2016, at 10:56 PM, Marcin Kościelnicki wrote: >> This is ok if bootstrap and regression tests are clean. Thanks! > The bootstrap and regression tests are indeed clean for this patch and #2. I > don't have commit access to gcc repo, how do I get this pushed? Just

Re: [PATCH] Detangle gcc/configure for Darwin

On Jan 21, 2016, at 6:50 AM, David Edelsohn wrote: > A gcc/configure stanza to test for PowerPC mfcrf support became > tangled with Darwin test for .machine directive. This patch detangles > and separates the two tests. > > I don't have a Darwin system to test. > > *

Re: [PATCH] libitm: Disable testing transaction-safe exceptions on Darwin and AIX.

On Jan 21, 2016, at 10:15 AM, Torvald Riegel <trie...@redhat.com> wrote: > On Thu, 2016-01-21 at 10:06 -0800, Mike Stump wrote: >> On Jan 21, 2016, at 9:29 AM, Dominique d'Humières <domi...@lps.ens.fr> wrote: >>> // { dg-do run { target { ! { *-*-darwin* powerpc-ibm

Re: [PATCH v2] libstdc++: Make certain exceptions transaction_safe.

On Jan 21, 2016, at 9:29 AM, Dominique d'Humières wrote: > // { dg-do run { target { ! { *-*-darwin* powerpc-ibm-aix* } } } } A comment to hint that this has something to do with weak undefined would be nice.

Re: [doc] GCC manual copy-editing

On Jan 19, 2016, at 12:52 PM, Sandra Loosemore wrote: > I've checked in this patch to address some copy-editing issues I glanced around at it, looks nice, thanks.

Re: [wwwdocs] gcc-6/changes.html: diagnostics, Levenshtein, -Wmisleading-indentation, jit (v2)

On Jan 19, 2016, at 11:05 AM, Manuel López-Ibáñez wrote: > > Am I the only one who doesn't see the colors at > https://gcc.gnu.org/gcc-6/changes.html#c-family nor > https://gcc.gnu.org/gcc-5/changes.html#fortran ? Yes. The darkslategrey of the headings is very close to

Re: [C++] Add -fnull-this-pointer

On Jan 19, 2016, at 6:41 AM, Jakub Jelinek wrote: > But then perhaps it will be better incentive for the projects to fix their > cruft. With a specialized option they will keep broken code forever. Flags are forever.

Re: [POST A NEW PORT]

On Jan 19, 2016, at 7:50 PM, Nguyễn Sinh Ngọc wrote: > How can I post it into gcc-patches for everyone reviewing? Just send an email with it. If too large for a single email, you can compress it. If still too large, you can drop it on a server and just post a

Re: [PATCH] PR testsuite/69181: ensure expected multiline outputs is cleared per-test (v2)

On Jan 18, 2016, at 8:14 AM, David Malcolm wrote: > I assumed that these differences were unintentional, so the patch > consolidates things to make the cleanup identical between (A) and (B). I also think this is the right path forward.

Re: [PATCH] sanitize paths used in regular expression

On Jan 15, 2016, at 2:47 AM, David Malcolm wrote: > FWIW, I do something similar in multiline.exp's _build_multiline_regex, > which attempts to have a complete list of metacharacters (though I > believe some of these are not valid for POSIX filenames); Only ‘\’ and ‘\0’ are

Re: [hsa merge 08/10] HSAIL BRIG description header file

On Jan 15, 2016, at 2:37 AM, Jakub Jelinek wrote: > HSA Foundation grants express permission to any current Founder, Promoter, > Supporter Contributor, Academic or Associate member of HSA Foundation to > copy and redistribute UNMODIFIED versions of this specification So, this

Re: [PATCH v2] sanitize paths used in regular expression

On Jan 15, 2016, at 10:40 AM, Zachary T Welch wrote: > Does this version look better? Ok. > I am not sure if this the right place to put the new helper, so let me know > if there is a better spot for it. So, someone that wants to rehome the helper is free to do that.

Re: [PATCH] sanitize paths used in regular expression

On Jan 14, 2016, at 4:54 PM, Zachary T Welch wrote: > This patch fixes a small problem when running 'make check' from a path > that includes "++". When such paths get used as a regular expression, > that sequence would cause a runtime error. That is prevented here by >

Re: [PATCH, testsuite] Stabilize test result output of dump-noaddr

On Jan 12, 2016, at 12:48 AM, Thomas Preud'homme wrote: > This patch solve this problem by replacing the static pass number in the > output by a star, allowing for a stable output while retaining easy copy/ > pasting in shell. > Is this ok for stage3? Ok.

Re: [PATCH : RL78] Disable interrupts during hardware multiplication routines

On Jan 11, 2016, at 11:20 PM, Kaushik M Phatak wrote: > Kindly review the updated patch and let me know if it is OK. My review comment is still outstanding.

Re: [PATCH] c/68966 - atomic_fetch_* on atomic_bool not diagnosed

On Jan 6, 2016, at 3:38 PM, Martin Sebor wrote: >>> gcc/testsuite/ChangeLog: >>> 2016-01-04 Martin Sebor >>> >>> PR c/68966 >>> * gcc.dg/atomic-fetch-bool.c: New test. >>> * gcc.dg/sync-fetch-bool.c: Same. >> >> So the tradition is to repeat

Re: [CilkPlus] fix issues when cilk_spawn is used with nontrivial expressions

On Jan 6, 2016, at 12:11 PM, Ryan Burn wrote: > I could additionally check that the language is c++ before checking > those flags, Please, no. Objective-C++ isn’t C++ and the string that names the language won’t strcmp with the name of the C++ language.

Re: cilkplus fails without pthreads for me

On Jan 4, 2016, at 9:09 AM, Nathan Sidwell <nat...@acm.org> wrote: > On 01/04/16 10:06, Bernd Schmidt wrote: >> On 01/01/2016 07:13 PM, Mike Stump wrote: >>> cilkplus fails without pthreads for me: >>> >>> xg++: error: unrecognized command line option '-

Re: cilkplus fails without pthreads for me

On Jan 4, 2016, at 7:22 AM, Nathan Sidwell <nat...@acm.org> wrote: > On 01/01/16 13:13, Mike Stump wrote: >> cilkplus fails without pthreads for me: >> >> xg++: error: unrecognized command line option '-pthread' >> compiler exited with status 1 >> output i

guilty test suite fix

So, I’d like for the guality people to chime in. I only kick in, if they fail to do so for any reason. :-) Either, the stuff downstream _must_ arrange for newline ended content, or this code has to do it, if they don’t. My take, I think they are signing up for newline terminated content:

Re: [patch] [java] bump libgcj soname

On Jan 3, 2016, at 9:34 AM, Matthias Klose wrote: > On 03.01.2016 17:23, Andrew Haley wrote: >> On 03/01/16 15:52, Matthias Klose wrote: >>> No, libgcj versions up to 4.9.3 didn't change the value for releases taken >>> from >>> the same branch. All of 4.9.0, 4.9.1, 4.9.2, 4.9.3

cilkplus fails without pthreads for me

cilkplus fails without pthreads for me: xg++: error: unrecognized command line option '-pthread' compiler exited with status 1 output is: xg++: error: unrecognized command line option '-pthread' FAIL: c-c++-common/attr-simd-3.c -std=gnu++14 PR68158 (test for errors, line 5) I suspect pthreads

Re: [PATCH] v3 of diagnostic_show_locus and rich_location (was Re: [PATCH 2/5] Reimplement diagnostic_show_locus, introducing rich_location classes (v2))

On Sep 25, 2015, at 1:11 PM, David Malcolm wrote: > +layout::layout (diagnostic_context * context, >> +const diagnostic_info *diagnostic) >> >> [...] >> >> + if (loc_range->m_finish.file != m_exploc.file) >> +continue; >> + if

Re: [PATCH] Fix PR66848 by enforcing 16-bit alignment on darwin

On Dec 22, 2015, at 9:08 AM, Jack Howarth wrote: > This bug doesn't exist in the more recent boehm-gc 7.2 or > later releases. Until the exact change from 6.6 to 7.2 that suppresses > this bug is identified or FSF gcc's boehm-gc is rebased on the 7.2 > version or later,

Re: [Patch testsuite] Skip gcc.dg/ifcvt-4.c for targets on which it may not work

On Dec 22, 2015, at 3:24 AM, Richard Earnshaw (lists) wrote: > >> In theory what I want to be able to do is build all the listed targets >> and run a single test on them so that we can build these skip/xfail >> lists much easier. >> >> I've done it a few times by hand

Re: [PATCH 4/4] Un-XFAIL ssa-dom-cse-2.c for most platforms

On Dec 22, 2015, at 8:00 AM, Alan Lawrence wrote: > On 21/12/15 15:33, Bill Schmidt wrote: >>> >>> Not on a stage1 compiler - check_p8vector_hw_available itself requires being >>> able to run executables - I'll check on gcc112. However, both look like >>> they're >>>

Re: [PATCH, rs6000] Fix PR target/68872, make -mcpu=powerpc64le pass correct assembler option

On Dec 22, 2015, at 9:13 AM, Peter Bergner wrote: > PR target/68772 No, this is wrong. Compare to 68872 in the subject line. > * config/rs6000/rs6000.h (ASM_CPU_SPEC): For -mcpu=powerpc64le, > pass %(asm_cpu_power8)/-mpwr8. > *

Re: [build] Only support -gstabs on Mac OS X if assember supports it (PR target/67973)

On Dec 16, 2015, at 11:29 PM, Rainer Orth wrote: > Here's what I came up with. Tested with the appropriate runtest > invocations both in a tree with the Xcode 7/LLVM as without stabs > support, where the tests come out UNSUPPORTED, and another one with the > Xcode

Re: [build] Only support -gstabs on Mac OS X if assember supports it (PR target/67973)

On Dec 15, 2015, at 5:35 AM, Rainer Orth wrote: > Right: I'm effectively keeping just the first configure test for .stabs > support in the assembler to enable or disable > DBX_DEBUG/DBX_DEBUGGING_INFO. I'll post it later since … > ... testing revealed another

Re: fix scheduling antideps

On Dec 11, 2015, at 1:22 AM, Eric Botcazou wrote: >> This patch allows a target to increase the cost of anti-deps to better >> reflect the actual cost on the machine. > > But it can already do it via the TARGET_SCHED_ADJUST_COST hook, can't it? The undocumented

Re: fix scheduling antideps

On Dec 11, 2015, at 6:09 AM, Jeff Law wrote: > On 12/11/2015 02:22 AM, Eric Botcazou wrote: >>> This patch allows a target to increase the cost of anti-deps to better >>> reflect the actual cost on the machine. >> >> But it can already do it via the TARGET_SCHED_ADJUST_COST

Re: [PATCH 2/2] obsolete openbsd 2.0 and 3.X

On Dec 14, 2015, at 7:55 PM, tbsaunde+...@tbsaunde.org wrote: > * config.gcc: Makr openbsd 2.0 and 3.X as obsolete. English: Mark...

Re: [PATCH 1/2] mark *-knetbsd-* as obsolete

On Dec 14, 2015, at 7:55 PM, tbsaunde+...@tbsaunde.org wrote: > * config.gcc: mark knetbsd targets as obsolete. English: Mark...

Re: [build] Only support -gstabs on Mac OS X if assember supports it (PR target/67973)

On Dec 14, 2015, at 2:40 AM, Rainer Orth wrote: > As described in PR PR target/67973, newer assemblers on Mac OS X, which > are based on LLVM instead of gas, don't support .stab* directives any > longer. The following patch detects this situation and tries to fall

fix scheduling antideps

This patch allows a target to increase the cost of anti-deps to better reflect the actual cost on the machine. This gets me get 5% more performance on an important inner loop by exposing the actual cost of long dep chains that have lots of anti-deps in them. Be scheduling the longer chain

Re: [PATCH] Fix warnings from including fdl.texi into gnat-style.texi

On Dec 8, 2015, at 10:10 AM, Gerald Pfeifer wrote: > On Tue, 8 Dec 2015, Tom de Vries wrote: Can you approve the fdl part? >>> Let's assume I can. Okay. >> was the 'Okay' above: >> - a figure of speech (as I read it), or >> - an actual approval (conditional on the adding

Re: [PATCH] enable loop fusion on isl-15

On Dec 4, 2015, at 5:13 AM, Alan Lawrence wrote: > On 05/11/15 21:43, Sebastian Pop wrote: >>* graphite-optimize-isl.c (optimize_isl): Call >>isl_options_set_schedule_maximize_band_depth. >> >>* gcc.dg/graphite/fuse-1.c: New. >>*

fix formatting

I checked this in to fix a formatting issue. != binds more tightly than &&. Index: lra-constraints.c === --- lra-constraints.c (revision 230982) +++ lra-constraints.c (working copy) @@ -2556,8 +2556,8 @@ process_alt_operands

Re: [PATCH 01/15] Selftest framework (unittests v4)

On Nov 25, 2015, at 2:55 AM, Bernd Schmidt wrote: >> That would be the ideal - though do we require randomization > What do you hope to gain with randomization? Please, no randomization.

Re: [PATCH] Fix PR objc/68438 (uninitialized source ranges)

On Nov 23, 2015, at 3:13 AM, Joseph Myers wrote: > On Sun, 22 Nov 2015, David Malcolm wrote: > >> Is there (or could there be) a precanned dg- directive to ask if ObjC is >> available? > > I don't think so. Normal practice is that each language's tests are in >

Re: [PATCH] g++.dg/init/vbase1.C and g++.dg/cpp/ucn-1.C

On Nov 16, 2015, at 6:02 AM, Renlin Li wrote: > On 14/11/15 00:33, David Edelsohn wrote: >> No RISC architecture can store directly to MEM, so the expected RTL in >> g++.dg/init/vbase1.C is wrong. I am adding XFAIL for PowerPC. This >> probably should be disabled for ARM and

Re: [PATCH 01/15] Selftest framework (unittests v4)

On Nov 19, 2015, at 10:08 AM, David Malcolm wrote: > gcc_assert terminates the process and no further testing is done, > whereas the approach the kit tries to run as much of the testsuite as > possible, and then fail if any errors occurred. Running as much as possible is

Re: [PATCH] g++.dg/cpp1y/pr58708.C wchar_t size

On Nov 17, 2015, at 8:50 AM, David Edelsohn wrote: > > Thanks for the pointer. How about the following? Ok. sizeof (*wfoo) or sizeof (wchar_t) or some such might be even more portable. > > Thanks, David > > > Index: pr58708.C >

Re: Add null identifiers to genmatch

On Nov 16, 2015, at 1:52 PM, Richard Sandiford wrote: > > Yeah. Kenny was adamant that for wide-int we should have an UNSIGNED/SIGNED Yeah, you can blame me. I think (, UNSIGNED) conveys more than (,true) or (,false). The sad part is, this has always been true. >

Re: [PATCH 00/16] Unit tests framework (v3)

On Nov 16, 2015, at 3:12 PM, Jeff Law wrote: > So I'd tend to want them either at the end of the file with a single #if > CHECKING_P or as a separate foo-tests file. Hum… I kinda don’t want the main files mucked up with tests. I think I’d rather have #if CHECKING_P #include

Re: [PATCH] g++.dg/init/vbase1.C and g++.dg/cpp/ucn-1.C

On Nov 13, 2015, at 4:33 PM, David Edelsohn wrote: > No RISC architecture can store directly to MEM, so the expected RTL in > g++.dg/init/vbase1.C is wrong. I am adding XFAIL for PowerPC. So, completely non-portable test cases aren’t particularly nice. vbase1.C fails for me

tm_p.h for bb-reorder.c?

My port needs the below patch. I think this was reduced by someone on a port that didn’t use some features (TARGET_SHORT_BRANCH_CHEAPER) of tm.h. So, the question is, is this the preferred way to do this? I don’t want to hookize TARGET_SHORT_BRANCH_CHEAPER, which is the other fix. If yes,

libiberty TAGS

I applied this one as obvious. * Makefile.in (etags tags TAGS): Use && instead of ;. Index: Makefile.in === --- Makefile.in (revision 230269) +++ Makefile.in (working copy) @@ -409,7 +409,7 @@ stamp-noasandir: .PHONY: all

Re: [PATCH] Simple optimization for MASK_STORE.

On Nov 10, 2015, at 6:56 AM, Ilya Enkovich wrote: > 2015-11-10 17:46 GMT+03:00 Richard Biener : >> On Tue, Nov 10, 2015 at 1:48 PM, Ilya Enkovich >> wrote: >>> 2015-11-10 15:33 GMT+03:00 Richard Biener

Re: [PATCH 1/2] Fix invalid left shift of negative value.

On Nov 10, 2015, at 3:13 AM, Dominik Vogt wrote: > On Tue, Nov 10, 2015 at 12:11:23PM +0100, Dominik Vogt wrote: >> The following series of patches fixes all occurences of >> left-shifting negative constants in C code which is undefined by >> the C standard. The patches

Re: [PATCH 10/12] always define EH_RETURN_HANDLER_RTX

On Nov 9, 2015, at 11:46 AM, Jeff Law wrote: On 11/09/2015 12:38 PM, Bernd Schmidt wrote: >> We might want to think about making a policy decision to try waiving >> some of the testing requirements for target macro -> hook conversions. >> Maybe try only a "build to cc1"

Re: [ping] Fix PR debug/66728

On Nov 6, 2015, at 5:06 AM, Richard Biener wrote: >> If there are no substantial reasons to not check it in now, I’d like to >> proceed and get it checked in. People can refine it further in tree if they >> want. Any objections? > > Ok with a changelog entry and

Re: [PATCH][AArch64] PR target/68129: Define TARGET_SUPPORTS_WIDE_INT

On Nov 9, 2015, at 3:32 AM, Kyrill Tkachov wrote: > The aarch64 port does not define TARGET_SUPPORTS_WIDE_INT. > Ok for trunk and GCC 5? :-) I’d endorse it, but, best left to the target folks.

Re: [PATCH c/c++] use explicit locations for some warnings in c-pragma.c

On Nov 4, 2015, at 1:02 PM, Manuel López-Ibáñez wrote: > 24:missing

Re: [PATCH c/c++] use explicit locations for some warnings in c-pragma.c

On Nov 4, 2015, at 1:02 PM, Manuel López-Ibáñez <lopeziba...@gmail.com> wrote: > On 4 November 2015 at 09:45, Mike Stump <m...@mrs.kithrup.com> wrote: >> in the top of the tree. This is bad as the same line appears in a PASS: and >> an XFAIL:. Each test cas

Re: [ping] Fix PR debug/66728

On Nov 5, 2015, at 4:32 AM, Richard Biener wrote: > No idea on location lists but maybe this means we should just use the > maximum supported integer mode for CONST_WIDE_INTs? Ah, yeah, that sounds like a fine idea. Below is that version. I snuck in one more

Re: [ping] Fix PR debug/66728

On Nov 4, 2015, at 12:50 PM, Richard Sandiford <richard.sandif...@arm.com> wrote: > Mike Stump <mikest...@comcast.net> writes: >> Index: dwarf2out.c >> === >> --- dwarf2out.c (revision 229720)

Re: [ping] Fix PR debug/66728

On Nov 4, 2015, at 4:15 AM, Richard Biener wrote: > I wonder if we'll manage to to get mode_for_size return BLKmode > in case of an original mode that was not of a size multiple of > HOST_BITS_PER_WIDE_INT (and that's host dependent even…). > We probably should use

Re: [ping] Fix PR debug/66728

On Nov 4, 2015, at 1:43 AM, Richard Biener wrote: > I think you should limit the effect of this patch to the dwarf2out use > as the above doesn't make sense to me. Since dwarf is so special, and since other clients already do something sort of like this anyway, it

Re: [PATCH c/c++] use explicit locations for some warnings in c-pragma.c

On Sep 20, 2015, at 2:40 PM, Manuel López-Ibáñez wrote: > On 20 September 2015 at 22:32, Christophe Lyon > wrote: >> On 25 May 2015 at 22:16, Manuel López-Ibáñez wrote: >>> On 25 May 2015 at 21:56, Marek Polacek

Re: [ping] Fix PR debug/66728

On Nov 3, 2015, at 12:46 AM, Richard Sandiford wrote: > This isn't just an argument about the DWARF standard though. It's an > argument about GCC internals. Presumably these hypothetical BLKmode > types would need to support addition, I don’t recall seeing that as a

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