[PATCH] glibc/sysdeps/microblaze/bits/atomic.h: Avoid include recursion to cause compiling break

The related definitions are in 'atomic.h', which also need include 'lowlevellock.h', which also need the related functions in 'atomic.h'. The related configuration: ../glibc/configure --prefix /upstream/release/ \ --target=microblaze-linux-gnu --with-headers=/upstream/release/kernel \

Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'

On 09/21/2014 02:24 PM, Chen Gang wrote: > > After check the details, I guess, we need: > > - Cross compile and install glibc with raw microblaze cross-compiler, > After fix a compiling break bug for microblaze glibc, I succeed building microblaze glibc with microblaze raw cross compiler, with

Re: [PATCH] Make all gcc.dg/guality/const-volatile.c subtests PASS under LTO.

On September 21, 2014 12:06:24 AM CEST, Mark Wielaard wrote: >Some subtests were reported as UNSUPPORTED when running under LTO. >That was just because the relevant variables were optimized out. >Mark those variables as used. Now const-volatile reports 192 PASS. OK. Ideally with early debug we c

Re: [PATCH] remove duplicated lines in gcc/fortran/resolve.c

> AFAICT the lines 11200-11222 in gcc/fortran/resolve.c are a copy of > the lines 11176-11198. The duplicates were introduced by revision 126468, an unrelated patch, after the original commit of the code as 126466. It looks like a svn/patch mishap. > The following patch removes the duplicated >

Re: Speedup int_bit_from_pos

On September 20, 2014 6:07:52 PM CEST, Jan Hubicka wrote: >> On 09/19/14 22:04, Jan Hubicka wrote: >> >Hi, >> >int_bit_position is used by ipa-devirt's type walking code. It is >currently a bottleneck >> >since I introduced speculation into contextes (I plan to solve this >by changing the >> >way

Re: [PATCH, libffi, alpha]: Use FFI_ASSERT in ffi_closure_osf_inner

On Sat, Sep 20, 2014 at 12:04 PM, Anthony Green wrote: > > [replying to an ancient post here..] > > Uros Bizjak writes: > >> Hello! >> >> Attached patch fixes libgo reflect test failure with libffi closures. >> The gccgo compiler started to use FFI closures recently; the compiler >> passes ffi_ty

Re: [PATCH, i386, Pointer Bounds Checker 33/x] MPX ABI

On Fri, Sep 19, 2014 at 9:55 AM, Ilya Enkovich wrote: > Here is an updated version of this patch. > > Thanks, > Ilya > -- > 2014-09-19 Ilya Enkovich > > * config/i386/i386.c (ix86_option_override_internal): Do not > support x32 with MPX. > is not available. > (i

Re: [GOOGLE] Fix LIPO COMDAT fixup and gcov-tool interactions

On 09/13/14 00:31, Teresa Johnson wrote: This patch addresses issues when running gcov-tool after performing COMDAT fixup during dyn-ipa. Functions that were previously all zero counts are marked, and the counts are discarded when being read in by gcov-tool before recalculating module groups and

Re: [Patch sh] Fixup use of constraints in define_split

On Fri, 2014-09-19 at 13:59 +0100, James Greenhalgh wrote: > Hi, > > After https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01615.html we error > on the use of constraints in define_splits, define_expands and > define_peephole2s. These are never looked at by the compiler, and so > have no reason to b

Re: Speedup int_bit_from_pos

> > Please omit static from inline functions. Yep, I suppose we want to drop static in all inlines? I can make patch for that. > > Also one notable difference with your patches is that the fits hwi is now not > tested on the result but on the result input which, multiplied by 8, might > not fi

[PATCH, i386]: Properly generate clobbered regs in ms->sysv function call

Hello! While reviewing MPX patches, I noticed that gcc generates clobbers in the ms->sysv function call as part of the call insn pattern. The documentation recommends to generate clobbers inside the expr_list, and this is what the patch implements. The patch further removes now unneeded specializ

Re: [PATCH, i386, Pointer Bounds Checker 33/x] MPX ABI

On Sun, Sep 21, 2014 at 2:34 PM, Uros Bizjak wrote: > On Fri, Sep 19, 2014 at 9:55 AM, Ilya Enkovich wrote: > >> Here is an updated version of this patch. >> >> Thanks, >> Ilya >> -- >> 2014-09-19 Ilya Enkovich >> >> * config/i386/i386.c (ix86_option_override_internal): Do not >>

Re: [PATCH, i386, Pointer Bounds Checker 34/x] Vararg functions support

Hello! > This patch introduces initialization of incoming bounds for vararg function > on i386 target. > > Bootstrapped and tested on linux-x86_64. > > Thanks, > Ilya > -- > gcc/ > > 2014-06-11 Ilya Enkovich > > * config/i386/i386.c (ix86_setup_incoming_varargs): New. > (ix86_v

Re: [PATCH 1/9] rs6000: Change how we model the carry bit

On Sat, Sep 20, 2014 at 2:23 PM, Segher Boessenkool wrote: > Make the carry bit non-allocatable (i.e., of class NO_REGS). It will > only ever be assigned to explicitly by machine patterns. Let it have > mode SI or DI (if compiling for 64-bit), even though it only ever > contains 0 or 1, so that

Re: [PATCH 2/9] rs6000: Handle rtx cost of NE

On Sat, Sep 20, 2014 at 2:23 PM, Segher Boessenkool wrote: > Currently NE isn't handled at all. Handle it the same as EQ, LTU, GTU. > > > 2014-09-20 Segher Boessenkool > > * config/rs6000/rs6000.c (rs6000_rtx_costs) : New. Okay. Thanks, David

Re: [PATCH 3/9] rs6000: Clean up one_cmpl2

On Sat, Sep 20, 2014 at 2:23 PM, Segher Boessenkool wrote: > Just the usual tidying. Also use the "not" extended mnemonic instead > of the "nor" that translates to. > > > 2014-09-20 Segher Boessenkool > > * config/rs6000/rs6000.md (*one_cmpl2): Generate "not" insn. > (two anony

Re: [PATCH 5/9] rs6000: Clean up bool3

On Sat, Sep 20, 2014 at 2:23 PM, Segher Boessenkool wrote: > Use a new code iterator to handle IOR, XOR. Also, we can now fold > the AND patterns together with the boolean_or_operator patterns. > > > 2014-09-20 Segher Boessenkool > > * config/rs6000/rs6000.md (iorxor): New code_iterato

Re: [PATCH 4/9] rs6000: Clean up neg2

On Sat, Sep 20, 2014 at 2:23 PM, Segher Boessenkool wrote: > > 2014-09-20 Segher Boessenkool > > * config/rs6000/rs6000.md (*neg2_internal): Delete. > (two anonymous define_insn and two define_split): Delete. > (*neg2, *neg2_dot, *neg2_dot2): New. Okay. Thanks, David

Re: [PATCH 6/9] rs6000: Clean up sub3

On Sat, Sep 20, 2014 at 2:23 PM, Segher Boessenkool wrote: > The instruction patterns are now called subf, with the corresponding > operand order, to be less confusing. I tried using the "sub" extended > mnemonics instead but that only made things way, way worse. > > Do not allow an integer as se

Re: [PATCH 7/9] rs6000: Clean up ctz, ffs, popcount, parity

On Sat, Sep 20, 2014 at 2:23 PM, Segher Boessenkool wrote: > > 2014-09-20 Segher Boessenkool > > * config/rs6000/rs6000.md (ctz2, ffs2, popcount2, > popcntb2, popcntd2, parity2, parity2_cmpb): > Tidy. Okay. Thanks, David

Re: [PATCH 8/9] rs6000: Clean up sra[wd]

On Sat, Sep 20, 2014 at 2:23 PM, Segher Boessenkool wrote: > > 2014-09-20 Segher Boessenkool > > * config/rs6000/rs6000.md (ashr3, *ashr3, *ashrsi3_64, > *ashr3_dot, *ashr3_dot2): Clobber CA_REGNO. > (floatdisf2_internal2): Ditto. > (ashrdi3_no_power): Ditto. Fi

Re: [PATCH 9/9] rs6000: Clean up sra[wd]i;addze

On Sat, Sep 20, 2014 at 2:23 PM, Segher Boessenkool wrote: > Also change type "compare" to "two" for the dot forms. > > > 2014-09-20 Segher Boessenkool > > * config/rs6000/rs6000.md (div3): Fix comment. Use a different > insn for divides by integer powers of two. > (div

Re: [GOOGLE] Fix LIPO COMDAT fixup and gcov-tool interactions

On Sun, Sep 21, 2014 at 5:48 AM, Nathan Sidwell wrote: > On 09/13/14 00:31, Teresa Johnson wrote: >> >> This patch addresses issues when running gcov-tool after performing >> COMDAT fixup during dyn-ipa. Functions that were previously all zero >> counts are marked, and the counts are discarded whe

Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'

On 09/20/14 23:24, Chen Gang wrote: And it seems, we also need 'LinkScr.ld' for ldscript, could you share it to me, thanks. set_board_info ldscript "-T/home/eager/Xilinx/dg/microblaze_0/LinkScr.ld" Hi Chen -- The DejaGNU configuration I provided is for a bare-metal environment. If you are

Re: [Patch, AArch64] Enable Address sanitizer and UB sanitizer

On 17 September 2014 12:48, Marcus Shawcroft wrote: > On 9 September 2014 13:08, Christophe Lyon wrote: >> On 9 September 2014 12:03, wrote: >>> >>> On Sep 9, 2014, at 2:50 AM, Marcus Shawcroft wrote: +static unsigned HOST_WIDE_INT +aarch64_asan_shadow_offset (void) >

Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'

On 09/21/14 03:46, Chen Gang wrote: Excuse me, I want to consult one thing: I installed raw microblaze cross compiler, binutils and glibc into one directory (/upstream/release), and try to build a "Hello world" C program for microblaze under x86_64 host. I guess it is OK, but I am not quite sure

Re: [patch] libstdc++/29988 Rb_Tree reuse allocated nodes

On 30/07/14 23:39 +0200, François Dumont wrote: On 16/06/2014 22:23, François Dumont wrote: Hi Here is another proposal taking into account your remarks except the one below. In fact I had no problem with lambda, I just needed to store them in a variable, lambda do not need to be made mu

Profile mode maintenance patch

Hi Here is the promise major patch for the profile mode. Here are the most important modifications. Now instance of profiling structs are kept as pointers in the containers themselves. It has an impact on the container ABI but it greatly enhance performances as we do not need to move

Re: [Bug libstdc++/62313] Data race in debug iterators

On 10/09/14 22:55 +0200, François Dumont wrote: Hi Here is a proposal to fix this data race issue. I finally generalized bitset approach to fix it by inheriting from the normal iterator first and then the _Safe_iterator_base type. None of the libstdc++ iterator types are final so it is

Re: [RFA 2/2]: --enable-explicit-exception-frame-registration compatibility option

> From: Jeff Law > Date: Fri, 19 Sep 2014 08:29:16 +0200 > On 09/12/14 11:51, Hans-Peter Nilsson wrote: > > Ping! > >> libgcc: > >>* crtstuff.c [EH_FRAME_SECTION_NAME && !USE_PT_GNU_EH_FRAME]: > >>Sanity-check USE_EH_FRAME_REGISTR

RE: [PATCH, ira] Ignore some conflict cost

> -Original Message- > From: Marek Polacek [mailto:pola...@redhat.com] > Sent: Wednesday, September 17, 2014 5:29 PM > To: Zhenqiang Chen > Cc: gcc-patches@gcc.gnu.org > Subject: Re: [PATCH, ira] Ignore some conflict cost > > On Wed, Sep 17, 2014 at 05:18:27PM +0800, Zhenqiang Chen wrote:

Move dwarf2 frame tables to read-only section for AIX

Hi, The following patch moves dwarf2 exception frame tables to read-only memory so they can be properly shared by multiple processes on AIX. There are two main mechanisms to register frame tables: - EH_FRAME_SECTION_NAME puts the frames in a specially named section, which are then registered by c

Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'

On 9/22/14 2:03, Michael Eager wrote: > On 09/20/14 23:24, Chen Gang wrote: >> And it seems, we also need 'LinkScr.ld' for ldscript, could you share it >> to me, thanks. >> >>set_board_info ldscript "-T/home/eager/Xilinx/dg/microblaze_0/LinkScr.ld" > > Hi Chen -- > > The DejaGNU configurati

Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'

On 9/22/14 2:09, Michael Eager wrote: > On 09/21/14 03:46, Chen Gang wrote: >> Excuse me, I want to consult one thing: I installed raw microblaze cross >> compiler, binutils and glibc into one directory (/upstream/release), and >> try to build a "Hello world" C program for microblaze under x86_64 h

Re: [PATCH, Pointer Bounds Checker 23/x] Function split

2014-09-19 23:45 GMT+04:00 Jeff Law : > On 09/16/14 03:09, Ilya Enkovich wrote: >>> >>> >>> I must be misunderstanding something then. I fundamentally don't see how >>> the return bounds are any different here than the return value. If we >>> have >>> exposed the bounds in the IL, then aren't the