On Sep 1, 2014, at 6:34 PM, Ed Smith-Rowland <3dw...@verizon.net> wrote:
> (I sort of wonder why this wasn't added to the actual preprocessor 20 years
> ago.)
:-)
So can you hack the system at template expansion time yet? :-)
std::shell<“/bin/sh -c …”> maybe?
On Tue, Sep 2, 2014 at 11:28 AM, Jeff Law wrote:
> On 09/01/14 13:15, Segher Boessenkool wrote:
>>
>> On Mon, Sep 01, 2014 at 10:41:43AM -0600, Jeff Law wrote:
>>>
>>> On 08/31/14 06:18, Segher Boessenkool wrote:
On Fri, Aug 29, 2014 at 11:58:37PM -0600, Jeff Law wrote:
>
> One c
On Tue, Sep 2, 2014 at 11:40 AM, Jeff Law wrote:
> On 08/31/14 22:18, Bin.Cheng wrote:
>>>
>>>
>>> Note that i0..i4 need not be consecutive insns, so you'd have to walk the
>>> chain from the location with the death note to the proposed death note
>>> site.
>>> If between those locations there's a
On 08/31/14 22:18, Bin.Cheng wrote:
Note that i0..i4 need not be consecutive insns, so you'd have to walk the
chain from the location with the death note to the proposed death note site.
If between those locations there's another set of the same pseudo, then drop
the note. Since this may be an
On 09/01/14 11:50, Segher Boessenkool wrote:
Another question is why is r84 set twice in the first place?
Various transformations can set that kind of situation up.
Sure -- but also lazy expanders can reuse a register instead of doing
gen_reg_rtx. Which is why I asked :-)
Which comes back t
On 09/01/14 13:15, Segher Boessenkool wrote:
On Mon, Sep 01, 2014 at 10:41:43AM -0600, Jeff Law wrote:
On 08/31/14 06:18, Segher Boessenkool wrote:
On Fri, Aug 29, 2014 at 11:58:37PM -0600, Jeff Law wrote:
One could argue that this mess is a result of trying to optimize a reg
that is set more
From: Andi Kleen
The Linux kernel dynamically patches in __fentry__ calls in and
out at runtime. This allows using function tracing for debugging
in production kernels without (significant) performance penalty.
For this it needs a table pointing to each __fentry__ call.
The way it is currently
On Monday 01 September 2014 21:58:47 Ed Smith-Rowland wrote:
> The Fourth installment, testing and other oddments will be sent tomorrow.
>
> The implementation of __has_cpp_attribute is underway and will come in a
> few days as a Fifth installment (modulo bugs this should be all).
> I have it work
On Tue, Sep 2, 2014 at 1:50 AM, Segher Boessenkool
wrote:
> On Mon, Sep 01, 2014 at 10:39:10AM -0600, Jeff Law wrote:
>> On 09/01/14 05:38, Segher Boessenkool wrote:
>> >On Mon, Sep 01, 2014 at 11:36:07AM +0800, Bin.Cheng wrote:
>> >>>In the testcase (and comment in the proposed patch), why is com
The Fourth installment, testing and other oddments will be sent tomorrow.
The implementation of __has_cpp_attribute is underway and will come in a
few days as a Fifth installment (modulo bugs this should be all).
I have it working in C++.
I feel though that it would be welcome as it is in clang
From: Trevor Saunders
Hi,
There are still some issues to make this work really nicely, but this part is
probably good enough its worth reviewing.
For one thing you can't use ggc hash_map or set in front ends with some types
or gengtype will decide to put the overloads of the marking routines it
Greetings,
I am finally getting back to my SD-6 C++ features test work.
This adds feature macros to various libstdc++ components.
The new version of SD-6 cleans up the shared_mutex noise.
Some libraries that were moved to different tSen are still given macros as they
are in the SD-6 draft.
Bo
Greetings,
I am finally getting back to my SD-6 C++ features test work.
This second part adds a __has_include function-like macro that will
return true if a header exists. I also added a __has_include_next
function-like macro as an extension. Clang has this extension.
These macros just wrap t
Greetings,
I am finally getting back to my SD-6 C++ features test work.
This first part adds a __has_include__ built-in that will return true if
a header exists.
I also added __has_include_next__ as an extension. Clang has this
extension.
Both these built-ins will be wrapped in function type
On Mon, Sep 1, 2014 at 3:49 PM, Segher Boessenkool
wrote:
> Mostly like zero_extend, with two twists. First, this patch allows to set
> "dot" on insn type "exts". Now we are almost ready to remove insn type
> "compare".
>
> Second, this makes lwa_operand reject memory if avoiding Cell microcode.
On Mon, Sep 1, 2014 at 3:49 PM, Segher Boessenkool
wrote:
> Don't group the insns based on extended size; use source size instead.
> Use the "andi." insn rather than "rldicl." and friends if possible.
> The instructions guarded by TARGET_LFIWZX do not need that guard: the
> constraints already gua
On Mon, Sep 1, 2014 at 3:49 PM, Segher Boessenkool
wrote:
> This is a little more complex. The highpart muls generate a "truncate
> lshiftrt" pattern that is not canonical when widening to two registers,
> so this doesn't optimise well with combine. This patch changes it to use
> the canonical s
On Mon, Sep 1, 2014 at 3:49 PM, Segher Boessenkool
wrote:
> Nothing noteworthy in this patch, sorry.
>
> Tested as usual (powerpc64-linux, -m64,-m32,-m32/-mpowerpc64), no
> regressions. Is this okay to apply?
>
>
> Segher
>
>
> 2014-09-01 Segher Boessenkool
>
> gcc/
> * config/rs6000/r
On Monday 18 August 2014 14:32:04 Thiago Macieira wrote:
> Hello
>
> The SD-6 [1] document keeps a list of built-in #defines that allow
> application and library writers know when certain language and library
> features have been implemented by the compiler. They are optional, since a
> compliant
Hi,
The attached patch fixes PR 62312. It's actually obvious. Tested with
'make all-gcc' and checking that the added test case fails without the
patch and passes with the patch.
Committed to trunk as r214804 and to 4.9 as r214805.
Cheers,
Oleg
gcc/ChangeLog:
PR target/62312
* c
On Mon, 25 Aug 2014, DJ Delorie wrote:
> + for (i = 0; i < NUM_INT_N_ENTS; i ++)
> +if (int_n_enabled_p[i])
> + {
> + char buf[35+20+20];
> +
> + /* These are used to configure the C++ library. */
> +
> + if (!flag_iso || int_n_data[i].bitsize == POINTER_SIZE)
> + {
>
From: Andi Kleen
[This was an old patch of mine that has been posted before,
but never made it in]
This adds a new C/C++ option to force
__attribute__((no_instrument_function)) on every function compiled.
This is useful together with LTO. You may want to have the whole
program compiled with -pg
Mostly like zero_extend, with two twists. First, this patch allows to set
"dot" on insn type "exts". Now we are almost ready to remove insn type
"compare".
Second, this makes lwa_operand reject memory if avoiding Cell microcode.
That way we can easily merge the various extendsidi2 patterns (two
Don't group the insns based on extended size; use source size instead.
Use the "andi." insn rather than "rldicl." and friends if possible.
The instructions guarded by TARGET_LFIWZX do not need that guard: the
constraints already guarantee the (correct!) condition.
Tested as usual; no regressions.
This is a little more complex. The highpart muls generate a "truncate
lshiftrt" pattern that is not canonical when widening to two registers,
so this doesn't optimise well with combine. This patch changes it to use
the canonical subreg patterns instead, which means we need separate patterns
for L
Nothing noteworthy in this patch, sorry.
Tested as usual (powerpc64-linux, -m64,-m32,-m32/-mpowerpc64), no
regressions. Is this okay to apply?
Segher
2014-09-01 Segher Boessenkool
gcc/
* config/rs6000/rs6000.md (mulsi3, *mulsi3_internal1,
*mulsi3_internal2, and two splitte
On Mon, Sep 01, 2014 at 10:41:43AM -0600, Jeff Law wrote:
> On 08/31/14 06:18, Segher Boessenkool wrote:
> >On Fri, Aug 29, 2014 at 11:58:37PM -0600, Jeff Law wrote:
> >>One could argue that this mess is a result of trying to optimize a reg
> >>that is set more than once.Though I guess that mig
On Mon, Sep 01, 2014 at 10:39:10AM -0600, Jeff Law wrote:
> On 09/01/14 05:38, Segher Boessenkool wrote:
> >On Mon, Sep 01, 2014 at 11:36:07AM +0800, Bin.Cheng wrote:
> >>>In the testcase (and comment in the proposed patch), why is combine
> >>>combining four insns at all? That means it rejected c
On 08/31/14 06:18, Segher Boessenkool wrote:
On Fri, Aug 29, 2014 at 11:58:37PM -0600, Jeff Law wrote:
One could argue that this mess is a result of trying to optimize a reg
that is set more than once.Though I guess that might be a bit of a
big hammer.
It works fine in other cases, and is
On 09/01/14 05:38, Segher Boessenkool wrote:
On Mon, Sep 01, 2014 at 11:36:07AM +0800, Bin.Cheng wrote:
In the testcase (and comment in the proposed patch), why is combine
combining four insns at all? That means it rejected combining just the
first three. Why did it do that?
It is explicitly
Vladmir Makarov wrote:
> * config/s390/s390.h (IRA_COVER_CLASSES,
> IRA_HARD_REGNO_ADD_COST_MULTIPLIER(regno)): Define.
In debugging PR 53854 I noticed a strange behavior in IRA costs
that seems to trace back to the very first definition of the
IRA_HARD_REGNO_ADD_COST_MULTIPLIER on s3
Tom de Vries wrote:
> * ira-costs.c (ira_tune_allocno_costs): Use
> ALLOCNO_CROSSED_CALLS_CLOBBERED_REGS to adjust costs.
In debugging PR 53864 on s390x-linux, I ran into a weird change in behavior
that occurs when the following part of this patch was checked in:
> - if (ir
Hi Joseph:
Thanks for your review, I've reverted the part of gsyslimits.h,
here is updated patch and ChangeLog :)
bootstrap ok for x86_64
2014-09-01 Kito Cheng
except.h: Fix header guard.
addresses.h: Add missing header guard.
cfghooks.h: Likewise.
collect-utils.h: Likewise.
From: Andi Kleen
Only give a warning when gcc-ar/nm/ranlib cannot find the plugin.
In this case do not pass a plugin argument to the wrapped program.
This should make it work on non linker plugin systems, so
that the build system can use it unconditionally.
gcc/:
2014-09-01 Andi Kleen
On Mon, Sep 01, 2014 at 01:34:17PM +0200, Richard Biener wrote:
> On Sun, Aug 31, 2014 at 4:51 PM, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > To use gcc-{ar,ranlib} for boot strap we need to add a -B option
> > to the tool. Since ar has weird and unusual argument conventions
> > implement the
On Mon, Sep 01, 2014 at 07:55:52PM +0400, Marat Zakirov wrote:
> >>I have a fix for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61875.
> >>This situation occurs when somebody decides to build GCC with
> >>-fexeptions and -frtti which are forbidden for libsanitizer. They get
> >>strange error (see
On Mon, 1 Sep 2014, Kito Cheng wrote:
> gsyslimits.h: Likewise.
This is incorrect. This is a very special header file, installed as part
of the implementation of ; it certainly can't use any
user-namespace identifiers, and it's probably not safe for it to have
header guards at all.
--
J
On 08/26/2014 12:47 PM, Marat Zakirov wrote:
On 08/18/2014 07:37 PM, Marat Zakirov wrote:
Hi there!
I have a fix for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61875.
This situation occurs when somebody decides to build GCC with
-fexeptions and -frtti which are forbidden for libsanitizer.
On Sat, 30 Aug 2014, David Edelsohn wrote:
> > 2014-08-30 Maciej W. Rozycki
> >
> > * gcc.dg/tree-ssa/loop-19.c: Exclude classic FPU Power targets.
> >
> > Maciej
> >
> > gcc-test-power-loop-19.diff
> > Index: gcc-fsf-trunk-quilt/gcc/testsuite/gcc.dg/tree-ssa/loop-19.c
> > ===
Support for .preinit_array/.init_array/.fini_array has been available in
glibc since version 2.4.
[gcc]
2014-08-27 Tulio Magno Quites Machado Filho
* acinclude.m4: Automatically detect if glibc supports
.preinit_array/.init_array/.fini_array on cross compilers.
* config
Hello,
This patch is necessary for proper operation of a piece
of the Ada Makefile fragment which tests the value of $(CROSS).
@ substitutions aren't performed for the language specific
Makefile fragments so using @CROSS directly isn't an option
there.
We have been using this for years and multi
> -ffat-lto-objects is automatically active for hosts not supporting the
> linker plugin. Is gcc-ar$(exeext) unconditionally built and found
> on such hosts? Will gcc-ar work without finding a linker plugin
> on such hosts?
Currently it errors out. I suppose that could be turned into a warning
On Mon, 1 Sep 2014, Mike Stump wrote:
> > Executing on host: powerpc-linux-gnu-gcc arm_cortex_m25641.c
> > -fno-diagnostics-show-caret -fdiagnostics-color=never -mthumb -S -o
> > arm_cortex_m25641.s(timeout = 300)
>
> > OK to apply?
>
> Ok.
Applied, thanks.
Maciej
> Please mention the PR in the ChangeLog entry and add some testcases
> (can be gcc.target/i386/, but we should have it tested).
> Does this change anything on say register short sil __asm ("sil"); in 32-bit
> mode (when it IMHO should be rejected too?)?
>
Do we support "sil" at all? In i386.h i se
On Wed, Aug 27, 2014 at 03:29:40PM -0600, Jeff Law wrote:
> OK once you add a ChangeLog entry.
Thanks. Erm, yes. Committed with this ChangeLog:
2014-09-01 Segher Boessenkool
* genemit.c: Include dumpfile.h.
(gen_split): Print name of splitter function to dump file.
Segher
Hi,
This fixes an issue with the mode used for register save slots on the
stack where e500 processor support is enabled along non-e500 multilibs.
In that case the HARD_REGNO_CALLER_SAVE_MODE macro definition from
gcc/config/rs6000/e500.h overrides one in gcc/config/rs6000/rs6000.h even
for n
On Tue, Aug 26, 2014 at 10:04:36AM +0200, Richard Biener wrote:
> > Should I backport this to 4.9/4.8 after a while?
>
> Yes please.
Done.
Marek
On Tue, Aug 19, 2014 at 01:50:41PM +0200, Marek Polacek wrote:
> Sure, especially in the cgraph code... I'll wait until next week or
> so, thanks.
I've backported to 4.8/4.9 now.
Marek
On Wed, Aug 27, 2014 at 05:59:17PM +, Joseph S. Myers wrote:
> On Mon, 25 Aug 2014, Marek Polacek wrote:
>
> > PR62024 reports that we can't use __atomic_always_lock_free in
> > a static assert, as the FEs say it's not a constant expression. Yet the
> > docs say that the result of __atomic_al
The following patch tries to work towards fixing PR62291 by moving
NEW_SETS/AVAIL_OUT adding strictly to insert_into_preds_of_block
and the value / expression we wanted to insert. If doing that for
other unrelated expressions this may cause fake partial
redundancies to be detected and dead code w
Hi,
I think that in order to implement the resolution we simply have to
remove the check. Tested x86_64-linux.
Thanks,
Paolo.
//
/cp
2014-09-01 Paolo Carlini
DR 1405
PR c++/58102
* semantics.c (cxx_eval_outermost_constant_expr): Do not check
On Mon, Sep 01, 2014 at 03:28:42PM +0200, Steven Bosscher wrote:
> On Mon, Sep 1, 2014 at 3:23 PM, Marek Polacek wrote:
>
> > diff --git gcc/fortran/interface.c gcc/fortran/interface.c
> > index b210d18..68d8545 100644
> > --- gcc/fortran/interface.c
> > +++ gcc/fortran/interface.c
> > @@ -2014,7
The following avoids the usually 1-element size vectors during
constraint generation to be allocated on the heap.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2014-09-01 Richard Biener
* tree-ssa-struct-aliases.c (find_func_aliases_for_builtin_call):
This removes redundant "folding" code from reference phi-translation
and it avoids allocating the "translated" operands vector if it is
identical to the original one.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2014-09-01 Richard Biener
* tree-ssa
On Mon, Sep 1, 2014 at 3:23 PM, Marek Polacek wrote:
> diff --git gcc/fortran/interface.c gcc/fortran/interface.c
> index b210d18..68d8545 100644
> --- gcc/fortran/interface.c
> +++ gcc/fortran/interface.c
> @@ -2014,7 +2014,7 @@ compare_parameter (gfc_symbol *formal, gfc_expr *actual,
>if (fo
These two issues are the last ones blocking moving -Wlogical-not-parentheses
to -Wall. I tried to fix them, but my attempts failed, so I opened
PR62270. I hope we could for now go with the following; it only quiets
the warning, but otherwise does not change the code. Hopefully someone
familiar w
On Sep 1, 2014, at 2:45 PM, Nathan Sidwell wrote:
>> OK to commit ?
>
> Yes, thanks
Done. Thanks for your super prompt feedback.
Olivier
The dg conversion of gcc.c-torture/execute (thanks alot for tackling
this, by the way) broke gcc.c-torture/execute/20010129-1.c on 32-bit
x86:
FAIL: gcc.c-torture/execute/20010129-1.c -O0 (test for excess errors)
WARNING: gcc.c-torture/execute/20010129-1.c -O0 compilation failed to
produce
On 09/01/14 08:34, Olivier Hainque wrote:
We have been using a variant of this for years in our gcc 4.7
based compiler series, checked that the patch works fine with
gcc-4.9 and that it applies as-is on the current mainline.
OK to commit ?
Yes, thanks
--
Nathan Sidwell
Hello,
VxWorks environments all provide a few environment variables
that help locate components such as header files or libraries.
WIND_BASE typically designates an installation root and the
regular VxWorks ports leverage this with:
gcc/confg/vxworks.h:
#define VXWORKS_ADDITIONAL_CPP_SPEC
On Sun, Aug 31, 2014 at 4:51 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> Change the bootstrap-lto config file to use slim (non fat) LTO..
> Speeds up the LTO bootstrap by ~18% on a 4 core system.
>
> This requires using gcc-ar/ranlib in post stage 1 builds, so these
> are passed to all sub build
On Mon, Sep 01, 2014 at 11:36:07AM +0800, Bin.Cheng wrote:
> > In the testcase (and comment in the proposed patch), why is combine
> > combining four insns at all? That means it rejected combining just the
> > first three. Why did it do that?
> It is explicitly reject by below code in can_combine
On Sun, Aug 31, 2014 at 4:51 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> To use gcc-{ar,ranlib} for boot strap we need to add a -B option
> to the tool. Since ar has weird and unusual argument conventions
> implement the code by hand instead of using any libraries.
>
> v2: Fix typo
> v3: Improve
The following patch avoids doing tail-merging work when not in PRE.
It also avoids dumping the shared_lookup_references vector and
avoids reallocating when visiting calls. It also hides APIs
of SCCVN that are not used outside.
I'd like to get rid of the tail-merging - SCCVN interaction for
GCC 5
On Mon, Sep 01, 2014 at 02:43:14PM +0400, Ilya Tocar wrote:
> Hi, this patch adds checks for registers availability, when
> alternative/numeric name is used.
> Bootstraps/passes make-check on x86-64.
> Ok for trunk?
>
> ChangeLog:
>
> gcc/
>
> 2014-09-01 Ilya Tocar
>
> * varasm.c (deco
On Fri, Aug 29, 2014 at 10:40:57AM -0700, Richard Henderson wrote:
> On 08/06/2014 03:05 AM, Varvara Rainchik wrote:
> > * libgomp.h (gomp_thread): For non TLS case create thread data.
> > * team.c (create_non_tls_thread_data): New function.
> >
> >
> > ---
> > diff --git a/libgom
Hi, this patch adds checks for registers availability, when
alternative/numeric name is used.
Bootstraps/passes make-check on x86-64.
Ok for trunk?
ChangeLog:
gcc/
2014-09-01 Ilya Tocar
* varasm.c (decode_reg_name_and_count): Check availability for
registers from ADDITIONAL_R
I've checked several tests, I see that for all tests failure occurs in
function gomp_icv (). E.g.:
icv-2:
#0 gomp_icv (write=true) at ../../../libgomp/libgomp.h:494
#1 omp_set_num_threads (n=6) at ../../../libgomp/env.c:1282
#2 0x00404014 in tf ()
#3 0x0040d063 in start_thread
> >
> >AVX512 added new 16 xmm registers (xmm16-xmm31).
> >Those registers require evex encoding.
> >Only 512-bit wide versions of instructions have evex encoding with
> >avx512f, but all versions have it with avx512vl.
> >Most instructions have same macroized pattern for 128/256/512 vector
> >leng
On 09/01/2014 11:03 AM, Jakub Jelinek wrote:
On Thu, Aug 14, 2014 at 05:59:56PM +0200, Bernd Schmidt wrote:
On 08/14/2014 05:50 PM, Jakub Jelinek wrote:
I hope the scheduler doesn't attempt to swap sp += 24 with flags setter
because of the sp += 16 vs. flags setter dependency and sp += 24 vs. s
On Sat, 30 Aug 2014, Kito Cheng wrote:
> Hi Richard:
>
> >> >> -fno-builtin is seem not only for the c family front-end, but also
> >> >> used in LTO now, so move it to common.opt and change it to `Common`.
> >> >
> >> > Please leave it in c-family and just add LTO to the set of supported
> >> >
Ping.
-Maxim
Original Message
Subject:[PATCH] Fix environment variables restoring in GCC testsuite.
Date: Fri, 22 Aug 2014 14:39:16 +0400
From: Maxim Ostapenko
To: GCC Patches
CC: Yury Gribov , Slava Garbuzov
Hi,
When testing, I've noticed, that Asan-bo
Hello,
I have not received any comments on the patch yet.
Eric, do you have any thoughts?
Best Regards,
Daniel Hellstrom
Software Section Head
Aeroflex Gaisler AB
Aeroflex Microelectronic Solutions – HiRel
Kungsgatan 12
SE-411 19 Gothenburg, Sweden
Phone: +46 31 7758657
dan...@gaisler.com
www.
On Thu, Aug 14, 2014 at 05:59:56PM +0200, Bernd Schmidt wrote:
> On 08/14/2014 05:50 PM, Jakub Jelinek wrote:
> >I hope the scheduler doesn't attempt to swap sp += 24 with flags setter
> >because of the sp += 16 vs. flags setter dependency and sp += 24 vs. sp +=
> >16 dependency, but I feel kind of
On Mon, Sep 1, 2014 at 10:47 AM, Jakub Jelinek wrote:
> On Wed, Aug 27, 2014 at 12:25:14PM +0200, Uros Bizjak wrote:
>> Something like following (untested) patch that also fixes the testcase
>> perhaps?
>>
>> -- cut here--
>> Index: cfgexpand.c
>> =
On 9/1/14 16:41, Jakub Jelinek wrote:
> On Thu, Aug 28, 2014 at 06:43:02AM +0800, Chen Gang wrote:
>> 'max_len' is the maximized length of 'name', so for writing '\0' to
>> "name[max_len]", it is out of string's border, need use "max_len - 1"
>> instead of.
>
> Depends on how the function's API
On Wed, Aug 27, 2014 at 12:25:14PM +0200, Uros Bizjak wrote:
> Something like following (untested) patch that also fixes the testcase
> perhaps?
>
> -- cut here--
> Index: cfgexpand.c
> ===
> --- cfgexpand.c (revision 214445)
> +++ c
On Aug 30, 2014, at 8:36 AM, Jeff Law wrote:
>> * Makefile.in (FLAGS_TO_PASS): Propagate INSTALL, INSTALL_DATA,
>> INSTALL_SCRIPT and INSTALL_PROGRAM as well.
> OK.
Checked-in, Thanks :)
On Thu, Aug 28, 2014 at 06:43:02AM +0800, Chen Gang wrote:
> 'max_len' is the maximized length of 'name', so for writing '\0' to
> "name[max_len]", it is out of string's border, need use "max_len - 1"
> instead of.
Depends on how the function's API is defined.
And, at least in GCC sources that fun
On Fri, Aug 29, 2014 at 02:51:57PM +0800, Thomas Preud'homme wrote:
> 2014-08-29 Thomas Preud'homme
>
> * tree-ssa-math-opts.c (struct symbolic_number): Clarify comment about
> the size of byte markers.
> (do_shift_rotate): Fix confusion between host, target and marker byte
>
On 09/01/2014 11:29 AM, Jakub Jelinek wrote:
On Mon, Sep 01, 2014 at 11:19:07AM +0400, Maxim Ostapenko wrote:
libiberty/ChangeLog:
2014-09-01 Max Ostapenko
* testsuite/Makefile.in(LIBCFLAGS): Add LDFLAGS.
Space before (.
Ugh, sorry.
# Flags to pass down to makes which are bu
On Fri, Aug 29, 2014 at 02:36:17PM +, Zamyatin, Igor wrote:
> Hi!
>
> The patch is another attempt to enable Cilk_for (see eg
> https://www.cilkplus.org/sites/default/files/open_specifications/Intel_Cilk_plus_lang_spec_1.2.htm)
> in the GCC compiler.
>
> Bootstrapped and regtested on x86_64
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
> ow...@gcc.gnu.org] On Behalf Of Jeff Law
> Sent: Saturday, August 30, 2014 4:54 AM
> To: Zhenqiang Chen; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH, ira] Miss checks in split_live_ranges_for_shrink_wrap
>
On Mon, Sep 01, 2014 at 11:19:07AM +0400, Maxim Ostapenko wrote:
> libiberty/ChangeLog:
>
> 2014-09-01 Max Ostapenko
>
> * testsuite/Makefile.in(LIBCFLAGS): Add LDFLAGS.
Space before (.
> # Flags to pass down to makes which are built with the target environment.
> # The double $ decr
On Mon, Sep 01, 2014 at 11:22:12AM +0400, Yury Gribov wrote:
> BTW regarding ChangeLog: should I mention both bugs (they are
> duplicates) or just one of them?
You can mention both if you want (on separate lines), or just the
one the other has been DUPed to.
> commit e3324d8d3528f0cb1a56e784f0887
---
From: Yury Gribov
Sent: Friday, August 22, 2014 12:47PM
To: GCC Patches
Cc: Jakub Jelinek, Marek Polacek, t...@alumni.duke.edu, sabrina...@gmail.com
Subject: [PATCH] Fix Asan ICEs on unexpected types (PR62140, PR61897)
On 08/22/2014 12:47 PM, Yury
On 08/25/2014 07:21 PM, Bernhard Reutner-Fischer wrote:
On 25 August 2014 16:23:54 CEST, Yury Gribov wrote:
On 08/25/2014 11:04 AM, Maxim Ostapenko wrote:
This patch adds necessary flags to provide a linkage of these tests
in
bootstrap-asan case.
I think you'll want to modify Makefile.def
87 matches
Mail list logo
