Re: Fix libgcc for FreeBSD 10

On 11/13/2011 04:18 PM, Gerald Pfeifer wrote: The snippet below was written when a new major release of FreeBSD would happen every couple of years, not as frequently as recently the case. FreeBSD 1.x and 2.x, and a.out support, have been obsolete for what must be a decade or so, yet the regular

Re: [Patch testsuite/darwin] fix PR testsuite/51059

Iain, > This probably qualifies as obvious - but having discussed some of the > background with Mike .. > .. there are other ways of solving the problem - although probably rather > heavy-weight for this problem. > > .. So, I'll let him have the say... > > OK for trunk? > Iain > > testsuite: > >

Re: Revert "PowerPC shrink-wrap support 3 of 3"

On 11/11/11 20:13, Hans-Peter Nilsson wrote: > AFAICT, your patch has got sufficiently testing now (on three > targets to boot) to be considered safe to check in. Or is > something amiss? > > (If it's the unchecked code quality you mentioned, that can be > just as well dealt with having the tree

Re: [Patch,Fortran] PR39427/37829 - implement F2003's constructors

Dear Tobias, I'll take a look this afternoon. Cheers Paul On Mon, Nov 14, 2011 at 10:45 AM, Tobias Burnus wrote: > I would like to *ping*. > > Additionally, I attached an updated patch as the tree-walking patch is now > in. The updated patch is also available at > https://userpage.physik.fu-be

[v3] Remove constexpr from frexp, modf, remquo

Hi, Daniel noticed that in we have functions marked constexpr which aren't really viable anyway due to the pointer parameter. Seems basically harmless given our way to deal with these matters, but I agree can be misleading. Tested x86_64-linux, committed. Paolo. /// 201

Re: [Patch testsuite/darwin] fix PR testsuite/51059

Hi Rainer, On 14 Nov 2011, at 09:50, Rainer Orth wrote: +/* { dg-options "-O2 -fprofile-arcs -ftest-coverage - flat_namespace - undefined suppress" { target *-*-darwin* } } */ /* { dg-require-weak "" } */ I'd prefer if you'd use the new dg-additional-options instead of duplicating the compl

[PATCH, PR51005] Fix slow down of compilation of 20001226-1.c by -ftree-tail-merge

Richard, This patch fixes the slow down in the compilation of 20001226-1.c caused by -ftree-tail-merge. -ftree-tree-tail-merge removes half of the 16000 basic blocks, but increases compilation time with a factor 2.4 from 34 seconds to 80 seconds (not counting the further increase of 46 seconds by

CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

> From: Bernd Schmidt > Date: Mon, 14 Nov 2011 10:51:56 +0100 > On 11/11/11 20:13, Hans-Peter Nilsson wrote: > > AFAICT, your patch has got sufficiently testing now (on three > > targets to boot) to be considered safe to check in. Or is > > something amiss? > > > > (If it's the unchecked code q

Re: vector garbaged collected while still in use

... probably here. Though I'd also approve a patch that simply removes the ggc_collect call (and the nested parameter). Honza - you probably added the ggc_collect - what's the reason to do it in this lowlevel place? The ggc_collect was always here. Before unit-at-a-time we used to run into

Re: vector garbaged collected while still in use

> Here is the revised patch. Bootstrap and regression tested on linux/x86-64. > > Honza, can you comment on the implication of this change? Well, as I explained in previous email, this was traditinal place where frontends collect garbage while parsing, so you would need to verify that all the exis

Re: CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

> > Someone with approval rights: pretty please? Can I add my +1 "pretty please" as well here :) ? According to #c3 this fixes arm-linux-gnueabi cross-builds for C++ as well and potentially allows this to bootstrap again. I have kicked off a bootstrap and test run on arm-linux-gnueabi . cheers Ra

Re: CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

Ramana Radhakrishnan writes: >> Someone with approval rights: pretty please? > > Can I add my +1 "pretty please" as well here :) ? According to #c3 > this fixes arm-linux-gnueabi cross-builds for C++ as well and > potentially allows this to bootstrap again. I have kicked off a > bootstrap and tes

[patch committed]: Fix recent obvious typo in gcov.c

Hi, this fixes bootstrap failure for Windows targets due recent change in gcov.c. 2011-11-14 Kai Tietz * gcov.c (generate_results): Add missing semicolon and correct indent. Committed at revision 181353. Regards, Kai Index: gcov.c ===

Re: [google] ThreadSanitizer instrumentation pass (issue 5303083)

Ok for google/main after compiler bootstrap and regression test (without ftsan), and some large tests with tsan turned on (as many as you can but at your discretion). David On Sun, Nov 13, 2011 at 11:59 PM, wrote: > On 2011/11/11 00:00:35, davidxl wrote: >> >> Have you run through SPEC, and SPE

[pph] Add flag -fpph-include-tree (issue5376093)

This patch is an enhanced variant of -H. It prints more information about the included files. I'm using it as input to a tool to automatically generate PPH mappings for large TUs. I don't think this will survive for long, but it is useful for now. Tested on x86_64. Committed to branch. Dieg

Re: [PATCH] Account for devirtualization opportunities in inliner

Hi, the patch is OK. Thanks! Honza

Re: Memset/memcpy patch

On Mon, Nov 14, 2011 at 9:03 AM, Jan Hubicka wrote: > Hi, > this is hopefully final variant of patch. The epilogue code was broken in some > scenarios for memset, but should work safely now.  I also fixed the tables for > core/buldozer/amdfam10 chips. > > But before it can be comitted, we need to

[PATCH] postreload: Invalidate reg_state info at barrier/volatile insns

Hi, a problem in postreload causes a miscompilation of libgomp on s390x. insn 1: r1 = r1 + r2 insn 2: r3 = r1 insn 3: unspec_volatile insn 4: use r1 With the patch from http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49452 the regstate information is resetted at the unspec_volatile instead of invali

Fix emutls bootstrap issues

Hi, emutls is creating variables late that confuses varpool since varpool_finalize_decl is supposed to be used only before cgraph construction. This patch fixes the problem by introducing varpool_add_new_variable that works same as cgraph_add_new_function (i.e. allows middle-end/back-end to create

Re: Memset/memcpy patch

> On Mon, Nov 14, 2011 at 9:03 AM, Jan Hubicka wrote: > > Hi, > > this is hopefully final variant of patch. The epilogue code was broken in > > some > > scenarios for memset, but should work safely now.  I also fixed the tables > > for > > core/buldozer/amdfam10 chips. > > > > But before it can

Re: CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

On 11/14/2011 04:10 AM, Hans-Peter Nilsson wrote: > Looks like all we need is a positive review of > and a > ChangeLog entry to unbreak three or more targets. > > Someone with approval rights: pretty please? That patch is ok. r~

Re: PR c++/30195

Looks good; I fixed a few whitespace and formatting issues and checked in the patch. Thanks a lot! Jason

Re: [PATCH 1/4] arm: Install __sync libfuncs for Linux.

On 11 November 2011 23:32, Richard Henderson wrote: > Cc: Richard Earnshaw > Cc: Ramana Radhakrishnan > --- >  gcc/config/arm/arm.c |    4 >  1 files changed, 4 insertions(+), 0 deletions(-) > > diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c > index 6ef6f62..abf8ce1 100644 > --- a

PATCH: Check ia32 instead of ilp32

Hi, ilp32 includes both x32 and ia32. -march=i486 only applies to ia32. I checked in this patch to check ia32 instead of ilp32. H.J. --- Index: ChangeLog === --- ChangeLog (revision 181359) +++ ChangeLog (working copy) @@ -1,3

Re: [PATCH 1/4] arm: Install __sync libfuncs for Linux.

On 11/14/2011 08:08 AM, David Gilbert wrote: > There is unfortunately no guarantee that your kernel has support for the 64bit > cases, since this was only recently added - and the libgcc code checks > and aborts if linked in. > > (As far as I can tell there is approximately one potential user of 6

Re: [PATCH 1/4] arm: Install __sync libfuncs for Linux.

> > There is unfortunately no guarantee that your kernel has support for the 64bit > cases, since this was only recently added - and the libgcc code checks > and aborts if linked in. I don't see how this patch will change status-quo. Richard: I've not been able to test the patch yet given that tr

[PATCH, i386]: Vectorize (int) {floor,ceil,round}{,f} with SSE4.1+

Hello! Currently, gcc vectorizes {floor,ceil,round}{,f}, but not i.e. (int) floor [and other rounding functions] due to conversion of (int) floor -> ifloor that inhibits vectorization. Attached patch introduces new expanders that handle rounding+conversions with expansion to round{pd,ps}+cvttpd2{

Re: [PATCH, testsuite]: Do not run simulate-thread on powerpc*-*-darwin*

On Nov 13, 2011, at 1:32 PM, Iain Sandoe wrote: > we have a problem on powerpc-darwin9 > OK for trunk? Ok, please. Include a comment line just before staying why.

Re: [PATCH 1/4] arm: Install __sync libfuncs for Linux.

On 11/14/2011 01:18 PM, Richard Henderson wrote: On 11/14/2011 08:08 AM, David Gilbert wrote: Andrew, what's the state of discussion on the atomics library? While I understand that vendors want to be able to replace that library, and thus we want to settle on a standard ABI, I think *not* provi

Couple of fixes to GRAPHITE-OpenCL

Hi guys, These are couple of patches for Graphite-OpenCL. First patch fixes lack of MINUS_EXPR processing in OpenCL kernel code generation. The second one fixed VEC related issue, which caused ISE on some tests from NPB (NASA parallel benchmark). ChangeLogs: [1] * graphite-opencl-code

Re: gcov patch, multiple paths

This breaks the mingw64 build with S_ISLNK being unresolved. Since windows doesn't know anything about symbolic links, could something like this help? diff --git a/gcc/config/i386/xm-mingw32.h b/gcc/config/i386/xm-mingw32.h index e0dd3f3..34663ac 100644 --- a/gcc/config/i386/xm-mingw32.h +++ b/gc

Re: gcov patch, multiple paths

On 11/14/11 19:51, Alen Skondro wrote: This breaks the mingw64 build with S_ISLNK being unresolved. Since windows doesn't know anything about symbolic links, could something like this help? thanks, Joseph also pointed this out to me. I have a slightly different patch in testing (posix specif

Re: [Patch]: PR49868: Named address space support for AVR, #4

Denis Chertykov wrote: > Let's wait for > http://gcc.gnu.org/ml/gcc-patches/2011-10/msg01874.html As that patch is now upstream, here the updated version. Difference to the prior implementation of AS1 is: o If no LPMX instruction is available and more than 2 bytes have to be loaded, a libgcc

[PATCH, testsuite]: Cleanup rounding *-vec.c test

Hello! 2011-11-14 Uros Bizjak * gcc.target/i386/avx-recip-vec.c: New test. * gcc.target/i386/avx-lrintf-vec.c: Ditto. * gcc.target/i386/avx-lrint-vec.c: Ditto. * gcc.target/i386/avx-ceilf-vec.c: Include sse4_1-ceilf-vec.c. * gcc.target/i386/avx-ceil-vec.

Re: [Patch] Take 2: Move Objective-C runtime flags to modern options system.

V2 is simpler, than http://gcc.gnu.org/ml/gcc-patches/2011-11/msg01335.html because (using the approach suggested by Joseph) we can initialize flag_next_runtime early enough to avoid having to deal with any other flags. [I'll still get rid of the flag_objc_sjlj_exceptions flag in a follow

Re: Memset/memcpy patch

2011/11/14 Jan Hubicka : >> On Mon, Nov 14, 2011 at 9:03 AM, Jan Hubicka wrote: >> > Hi, >> > this is hopefully final variant of patch. The epilogue code was broken in >> > some >> > scenarios for memset, but should work safely now.  I also fixed the tables >> > for >> > core/buldozer/amdfam10 c

Re: Memset/memcpy patch

On 14 Nov 2011, at 20:36, H.J. Lu wrote: 2011/11/14 Jan Hubicka : On Mon, Nov 14, 2011 at 9:03 AM, Jan Hubicka wrote: Hi, this is hopefully final variant of patch. The epilogue code was broken in some scenarios for memset, but should work safely now. I also fixed the tables for core/bu

Re: [PATCH, PR51005] Fix slow down of compilation of 20001226-1.c by -ftree-tail-merge

On Mon, Nov 14, 2011 at 2:02 PM, Tom de Vries wrote: > Richard, > > This patch fixes the slow down in the compilation of 20001226-1.c caused by > -ftree-tail-merge. > > -ftree-tree-tail-merge removes half of the 16000 basic blocks, but increases > compilation time with a factor 2.4 from 34 seconds

Re: Memset/memcpy patch

On Mon, Nov 14, 2011 at 12:40 PM, Iain Sandoe wrote: > > On 14 Nov 2011, at 20:36, H.J. Lu wrote: > >> 2011/11/14 Jan Hubicka : On Mon, Nov 14, 2011 at 9:03 AM, Jan Hubicka wrote: > > Hi, > this is hopefully final variant of patch. The epilogue code was broken > in some

Re: Memset/memcpy patch

Hi, 2011-11-14 Zolotukhin Michael Jan Hubicka >>> >>> Zolotukhin Michael works for Intel and has copyright assignment with FSF. Looks like we have a bootstrap issue, thus sorry if may message may appear stupid nitpicking: why Zolotukhin Michael instead of Mi

Re: [PATCH, PR51005] Fix slow down of compilation of 20001226-1.c by -ftree-tail-merge

From: Richard Guenther Date: Mon, 14 Nov 2011 21:43:30 +0100 > On Mon, Nov 14, 2011 at 2:02 PM, Tom de Vries wrote: >> This patch fixes the slow down in the compilation of 20001226-1.c caused by >> -ftree-tail-merge. ... >> ok for trunk? > > Ok. Tom, thanks for working on this. And Richard,

Re: [PATCH 3/3] rs6000: Rewrite sync patterns for atomic; expand early.

Richard, * rs6000: Rewrite sync patterns for atomic; expand early. Okay. Please go ahead and apply your patch with the conservative implementation of memory model for CONSUME while I investigate further. Thanks, David

Re: Memset/memcpy patch

On 14 Nov 2011, at 20:44, H.J. Lu wrote: On Mon, Nov 14, 2011 at 12:40 PM, Iain Sandoe wrote: On 14 Nov 2011, at 20:36, H.J. Lu wrote: 2011/11/14 Jan Hubicka : On Mon, Nov 14, 2011 at 9:03 AM, Jan Hubicka wrote: Hi, this is hopefully final variant of patch. The epilogue code was b

[patch] trans-mem: trivial: add cleanup-tree-dump in testcase, fix typo in comment.

Committed as obvious. commit df0a9fa2a7975b945b72b90bbcc8862d87fe2bad Author: Torvald Riegel Date: Mon Nov 14 14:34:30 2011 +0100 Trivial: add cleanup-tree-dump in testcase, fix typo in comment. gcc/testsuite: * g++.dg/tm/template-1.C: Add cleanup-tree-dump. Fix typo i

Re: [Patch] Take 2: Move Objective-C runtime flags to modern options system.

On Nov 14, 2011, at 12:30 PM, Iain Sandoe wrote: > V2 is simpler, than :-) > OK for trunk? Ok.

gcov, fix S_ISLNK

I've committed this to fix windows and other non-modern posix systems. nathan 2011-11-14 Nathan Sidwell * gcov.c (canonicalize_name): Protect use of S_ISLNK. Index: gcov.c === --- gcov.c (revision 181347) +++ gcov.c

Re: [PATCH 0/3] Conversion to __atomic builtins

On Sat, Nov 12, 2011 at 1:46 AM, Richard Henderson wrote: > There are a couple of instances in which the paper doesn't cover the > handling of memory_model_consume, and I made a best guess.  These > are indicated by /* ??? */ markers.  I would be obliged if someone > could verify what's supposed

Re: CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

On Mon, Nov 14, 2011 at 07:48:03AM -1000, Richard Henderson wrote: > On 11/14/2011 04:10 AM, Hans-Peter Nilsson wrote: > > Looks like all we need is a positive review of > > and a > > ChangeLog entry to unbreak three or more targets. > > >

coverage, propagate visibility

This patch propagates visibility information in the same way that weakness is for externally visible coverage objects. I don't know whether this will fix the reported firefox build failure -- can you try? Even if it doesn't, I'm pretty sure it's an improvement, but I'll leave it for comment be

Go patch committed: Use some of 6g runtime.c

This patch to the Go library uses some of the runtime.c file from the 6g compiler. This is to make it easier to merge changes to the scheduler. There are no functional changes with this patch. Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu. Committed to mainline. Ian diff -r 43a

Re: coverage, propagate visibility

On 2011.11.14 at 21:59 +, Nathan Sidwell wrote: > This patch propagates visibility information in the same way that weakness is > for externally visible coverage objects. I don't know whether this will fix > the > reported firefox build failure -- can you try? The patch doesn't help unfor

[patch] Require parentheses when parsing transaction expressions.

This patch fixes parsing of transaction expressions, so that two txn expressions that are part of a single expression do not get treated as nested txns anymore, but become two separate ones (see test case). This was approved off-line by Richard Henderson for the trans-mem branch and posted before N

Re: [patch] Require parentheses when parsing transaction expressions.

On 11/14/2011 12:41 PM, Torvald Riegel wrote: > Require parentheses when parsing transaction expressions. > > gcc/ > * c-parser.c (c_parser_transaction_expression): Require parentheses > when parsing transaction expressions. > > gcc/cp/ > * parser.c (cp_p

Re: Memset/memcpy patch

> bootstrap completed on i686-darwin9, so I've applied the following as > requested, Thank you and my apologizes for the breakage! Honza > Iain > > gcc: > > 2011-11-14 Jan Hubicka > > * config/i386/i386.c (core cost model): Correct pasto. > > ndex: gcc/config/i386/i386.c > =

Re: CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

> From: Richard Henderson > Date: Mon, 14 Nov 2011 18:48:03 +0100 > On 11/14/2011 04:10 AM, Hans-Peter Nilsson wrote: > > Looks like all we need is a positive review of > > and a > > ChangeLog entry to unbreak three or more targets. > > >

[PATCH] Fix PCH on MIPS

Since Linux 2.6.36, both the heap and mmap are randomized on MIPS like other architectures. This breaks PCH because currently TRY_EMPTY_VM_SPACE is not defined for MIPS. This patch fixes the issue and allows largefile test to pass now. OK? Bootstraped and tested on mips64-linux-gnu. Thanks, Andre

Re: [PATCH] Fix PCH on MIPS

On Mon, Nov 14, 2011 at 3:41 PM, Andrew Pinski wrote: > Since Linux 2.6.36, both the heap and mmap are randomized on MIPS like > other architectures. This breaks PCH because currently > TRY_EMPTY_VM_SPACE is not defined for MIPS. > This patch fixes the issue and allows largefile test to pass now.

Re: CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

> From: Alan Modra > Date: Mon, 14 Nov 2011 22:56:48 +0100 > I haven't really looked into what Bernd's fix does. I know this one > fixes what I broke.. Hm... Oh well, I'm trusting RTH and Bernd that it fixed a real issue. Thanks for looking (and a belated thanks to RTH for the review). brgds,

Re: Memset/memcpy patch

On Mon, Nov 14, 2011 at 9:03 AM, Jan Hubicka wrote: > Hi, > this is hopefully final variant of patch. The epilogue code was broken in some > scenarios for memset, but should work safely now.  I also fixed the tables for > core/buldozer/amdfam10 chips. > > But before it can be comitted, we need to

Re: CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

On 11/14/2011 11:56 AM, Alan Modra wrote: > On Mon, Nov 14, 2011 at 07:48:03AM -1000, Richard Henderson wrote: >> On 11/14/2011 04:10 AM, Hans-Peter Nilsson wrote: >>> Looks like all we need is a positive review of >>> and a >>> ChangeLog en

Re: [PATCH 0/3] Conversion to __atomic builtins

On 11/14/2011 11:46 AM, David Edelsohn wrote: > On Sat, Nov 12, 2011 at 1:46 AM, Richard Henderson wrote: > >> There are a couple of instances in which the paper doesn't cover the >> handling of memory_model_consume, and I made a best guess. These >> are indicated by /* ??? */ markers. I would

Re: CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

On 11/15/11 01:43, Richard Henderson wrote: > On 11/14/2011 11:56 AM, Alan Modra wrote: >> * function.c (thread_prologue_and_epilogue_insns): Guard >> emitting return with single_succ_p test. > > Hmm. This looks plausible too. > > Bernd's patch made sure that cfglayout didn't do some

Re: CFG review needed for fix of "PowerPC shrink-wrap support 3 of 3"

From: Bernd Schmidt Date: Tue, 15 Nov 2011 01:54:34 +0100 > On 11/15/11 01:43, Richard Henderson wrote: >> On 11/14/2011 11:56 AM, Alan Modra wrote: >>> * function.c (thread_prologue_and_epilogue_insns): Guard >>> emitting return with single_succ_p test. >> >> Hmm. This looks plausible

[PATCH, debug] Emit basic block markers in .debug_line section

With this patch DW_LNS_set_basic_block opcodes are emitted in the .debug_line section marking the instructions that indicate the beginning of a basic block as specified by the dwarf standards 2,3 and 4. Tested on x86_64-linux also against gdb's 7.3.1 testsuite. r gcc/Changelog: 2011-11-14 Rob

Re: [Patch]: PR49868: Named address space support for AVR, #4

2011/11/15 Georg-Johann Lay : > Denis Chertykov wrote: > >> Let's wait for >> http://gcc.gnu.org/ml/gcc-patches/2011-10/msg01874.html > > As that patch is now upstream, here the updated version. > > Difference to the prior implementation of AS1 is: > > o If no LPMX instruction is available and more

RFA: disable -fdelete-null-pointer-checks for Java

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/07/11 09:56, Paolo Bonzini wrote: I'm not sure if GCC will currently delete the "if" statement in > > try { x = x.getSomething(); } catch (NullPointerException npe) { } > > if (x) ... > > but even if it doesn't, the Java front-end should prob

[wwwdocs] POWER7 announcement in News section

I figured I'd make the POWER7 donation to the GCC Compile Farm a news item. Hint to everyone else: donate, and I'll be happy to add an entry as well. :-) Installed. Gerald Index: index.html === RCS file: /cvs/gcc/wwwdocs/htdocs/ind

Minor contrib.texi update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK for trunk? * doc/contrib.texi: Add entry for David Binderman. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOwgKRAAoJEBRtltQi2kC7ZKgIALIpCIUG

Re: coverage, propagate visibility

On 11/14/11 22:33, Markus Trippelsdorf wrote: On 2011.11.14 at 21:59 +, Nathan Sidwell wrote: This patch propagates visibility information in the same way that weakness is for externally visible coverage objects. I don't know whether this will fix the reported firefox build failure -- can y

Re: [PATCH 0/3] Predication support for selective scheduler

Hello, On 26.10.2011 21:11, Alexander Monakov wrote: Hello, This patch series implements predication support for the selective scheduler. It is implemented as a transformation similar to speculative execution, but simpler in some aspects (e.g. does not require recovery code). On ia64, combinin

Re: [PATCH 1/3] Transformation replay mechanism

Hello, On 26.10.2011 21:26, Alexander Monakov wrote: (Note, this is a prerequisite for predication support but also is an improvement on its own. This patch can be installed separately.) ... diff --git a/gcc/sel-sched.c b/gcc/sel-sched.c index f11faca..91fb0fe 100644 --- a/gcc/sel-sched.c

Re: [CRIS] Hookize FUNCTION_VALUE_REGNO_P

> From: Anatoly Sokolov > Date: Wed, 9 Nov 2011 22:42:53 +0100 > Regression tested on cris-axis-elf. > > OK to install? > > * config/cris/cris.c (cris_function_value_regno_p): Make static. > (TARGET_FUNCTION_VALUE_REGNO_P): Define. > * config/cris/cris.h (FUNCTION_VA

Re: coverage, propagate visibility

On 2011.11.15 at 07:09 +, Nathan Sidwell wrote: > On 11/14/11 22:33, Markus Trippelsdorf wrote: > > On 2011.11.14 at 21:59 +, Nathan Sidwell wrote: > >> This patch propagates visibility information in the same way that weakness > >> is > >> for externally visible coverage objects. I don't