On Fri, Apr 18, 2014 at 08:00:45AM +0200, Marek Polacek wrote:
> On Fri, Apr 18, 2014 at 07:49:22AM +0200, Marc Glisse wrote:
> > On Fri, 18 Apr 2014, Marek Polacek wrote:
> >
> > >This patch implements a new warning that warns when controlling
> > >expression of a switch has boolean value. (Inte
Hi Jakub,
I can take that task over and will boot-strap with all languages and run the
test suite on my armv7-linux-gnueabihf system.
But that will take until next week as it is currently occupied with other tests.
Can you please review Lin's latest patch and give your OK for check-in on trunk
a
On Fri, Apr 18, 2014 at 07:49:22AM +0200, Marc Glisse wrote:
> On Fri, 18 Apr 2014, Marek Polacek wrote:
>
> >This patch implements a new warning that warns when controlling
> >expression of a switch has boolean value. (Intentionally I don't
> >warn if the controlling expression is (un)signed:1 b
On Fri, 18 Apr 2014, Marek Polacek wrote:
This patch implements a new warning that warns when controlling
expression of a switch has boolean value. (Intentionally I don't
warn if the controlling expression is (un)signed:1 bit-field.)
I guess the question is if this should be enabled by default
This patch implements a new warning that warns when controlling
expression of a switch has boolean value. (Intentionally I don't
warn if the controlling expression is (un)signed:1 bit-field.)
I guess the question is if this should be enabled by default or
deserves some new warning option. Since c
Resulting from discussion here:
http://gcc.gnu.org/ml/gcc/2014-04/msg00125.html
ChangeLog:
* g++.dg/cpp0x/nsdmi-union5.C: Change to runtime test.
Index: gcc/testsuite/g++.dg/cpp0x/nsdmi-union5.C
===
--- gcc/testsuite/g++.dg/c
Hi Bernd,
a) On which target(s) did you boot-strap your patch?
I just run it on x86, can't run it on ARM, because Android is not a
posix system, nor a System V compatible system. And my code does not
effect x86.
b) Did you run the testsuite?
Yes, but again my code does not effect x
Hi,
Here is the patch after the Jakub's review, and Jakub helps with the
coding style.
--
* asan.c (asan_emit_stack_protection):
Force the base to align to appropriate bits if STRICT_ALIGNMENT. Set
shadow_mem align to appropriate bits if STRICT_ALIGNMENT.
* cfgexpand.c
(expand_sta
Hi,
I missed a case in the vector API work for little endian. When VSX is
enabled, the vec_mergeh and vec_mergel interfaces for 4x32 vectors are
translated into xxmrghw and xxmrglw. The patterns for these were not
adjusted for little endian. This patch fixes this and adds tests for
V4SI and V4S
This patch from Peter Collingbourne avoids duplicate function
declarations in the generated libcalls.go file when building the syscall
package. Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu.
Committed to mainline.
Ian
diff -r 5009262c3e56 libgo/go/syscall/mksyscall.awk
--- a/libg
This patch from Peter Collingbourne changes libgo to use the builtin
delete function rather than the old map deletion syntax. Bootstrapped
and ran Go testsuite on x86_64-unknown-linux-gnu. Committed to
mainline.
Ian
diff -r 1e27a38c43ea libgo/go/syscall/syscall_unix.go
--- a/libgo/go/syscall/sy
This patch from Peter Collingbourne avoids an unnecessary gccgo
extension in libgo. Bootstrapped and ran Go testsuite on
x86_64-unknown-linux-gnu. Committed to mainline.
Ian
diff -r 801009f33610 libgo/go/syscall/libcall_posix.go
--- a/libgo/go/syscall/libcall_posix.go Thu Apr 17 16:01:58 2014 -
> It seems a little inconsistent, however, that *movqi_real and
> *xorqi3_real don't specify modes but *movhi_real and
> *andqi_real/*iorqi_real do (and they also accept CONST_INTs). Not that
> I'm advocating generating more warnings, but my inner OCD likes
> consistency :)
Adding the mode m
I committed the following patch as obvious to fix the PowerPC build issue that
came up with changes to machmode.h. These changes allow the compiler to build
and bootstrap. Submitted as subversion id 209498.
2014-04-17 Michael Meissner
PR target/60876
* config/rs6000/rs6000.c (
On Wed, Apr 16, 2014 at 11:35 PM, Jeff Law wrote:
>
>> I'd like to ping 2 patches:
>>
>> http://gcc.gnu.org/ml/gcc-patches/2014-01/msg00140.html
>> - Ensure GET_MODE_{SIZE,INNER,NUNITS} (const) is constant rather than
>>memory load after optimization (I'd like to keep the current
>>
>>pat
This patch from Chris Manghane changes the Go frontend to use the
backend interface for global constants. Bootstrapped and ran Go
testsuite on x86_64-unknown-linux-gnu. Committed to mainline.
Ian
2014-04-17 Chris Manghane
* go-gcc.cc (Gcc_backend::named_constant_expression): New
On 04/17/2014 08:56 AM, Eric Botcazou wrote:
> I presume that the attached kludge is sufficient to make it work?
>
>
> * fe.h (Compiler_Abort): Replace Fat_Pointer by String.
> (Error_Msg_N): Likewise.
> (Error_Msg_NE): Likewise.
> (Get_External_Name_With_Suffix): Likewise
On Tue, 15 Apr 2014, DJ Delorie wrote:
I wasn't sure what to do with that array, since it was static and
couldn't have "empty" slots in them like the arrays in tree.h. Also,
do we need to have *every* type in that list? What's the rule for
whether a type gets installed there or not? The comme
On 15/04/14 22:58, DJ Delorie wrote:
I typically leave the mode off when the operand accepts a CONST_INT as
I've had problems with patterns matching CONST_INTs otherwise, as
CONST_INT rtx's do not have a mode (or have VOIDmode).
(yes, I know gcc is supposed to accomodate that, but like I said, I
This patch to the Go frontend fixes it to not convert the function type
in a call when calling an interface method. The function type of an
interface method is not correct, since it does not include the receiver,
but the type of the method field is correct, and as such should not be
converted. Th
Hi Lin,
On Thu, 17 Apr 2014 22:29:14, Lin Zuojian wrote:
>
> Hi Bernd,
> I have my copyright mark signed and the process has completed. Now I
> am going to answer two more questions before my patch can be
> commited right?
>
> Did you copy any
> files or text written by someone else in these chang
This looks fine. LIPO has similar change too. Other directions worth
looking into:
1) To model icache effect better, weighted callee size need to be
used with profile. The weight for BB may look like: min(1,
FREQ(BB)/FREQ(ENTRY)).
2) When function splitting is turned on, are any inline heuristi
This patch from Chris Manghane marks various expression types as
immutable: numerics, constants, type info, address of, type conversion
when appropriate. Bootstrapped and ran Go testsuite on
x86_64-unknown-linux-gnu. Committed to mainline.
Ian
diff -r 194e0f47c9e5 go/expressions.cc
--- a/go/exp
On Thu, 2014-04-17 at 19:52 +0200, Jan Hubicka wrote:
[...]
> Index: doc/invoke.texi
> ===
> --- doc/invoke.texi (revision 209461)
> +++ doc/invoke.texi (working copy)
> @@ -9409,7 +9409,8 @@ before applying @option{--param inlin
On 27 Mar 17:16, Jakub Jelinek wrote:
> On Thu, Mar 27, 2014 at 08:13:00PM +0400, Ilya Verbin wrote:
> > On 27 Mar 15:02, Jakub Jelinek wrote:
> > > The tables need to be created before IPA, that way it really shouldn't
> > > matter in what order you emit them. E.g. the outlined target functions
>
On April 17, 2014 7:18:05 PM CEST, Jan Hubicka wrote:
>> On April 17, 2014 6:03:13 PM CEST, Jan Hubicka
>wrote:
>> >> > > +
>> >> > > + /* At this stage we know that majority of GGC memory is
>> >reachable.
>> >> > > + Growing the limits prevents unnecesary invocation of
>GGC.
>> >*/
>> >
Hi,
I think for 4.10 we should revisit inliner behaviour to be more LTO and LTO+FDO
ready. This is first of small patches I made to sanitize behaviour of current
bounds.
The main problem LTO brings is that we get way too many inline candidates. In
per-file
model one gets only small percentage of
Ping.
On Wed, Feb 5, 2014 at 4:31 PM, Sriraman Tallam wrote:
> Hi,
>
> I would like this patch reviewed and considered for commit when
> Stage 1 is active again.
>
> Patch Description:
>
> A C++ thunk's section name is set to be the same as the original function's
> section name for which the t
On 04/17/2014 08:35 AM, Tristan Gingold wrote:
> What about this compile-time check:
>
> package Fatptralign is
>type String_Acc is access String;
>type Integer_acc is access Integer;
>
>pragma Compile_Time_Error
> (String_Acc'Alignment = 1 * Integer_Acc'Alignment,
> "Fat poi
> On April 17, 2014 6:03:13 PM CEST, Jan Hubicka wrote:
> >> > > +
> >> > > + /* At this stage we know that majority of GGC memory is
> >reachable.
> >> > > + Growing the limits prevents unnecesary invocation of GGC.
> >*/
> >> > > + ggc_grow ();
> >> > >ggc_collect ();
> >> >
> >> >
On April 17, 2014 6:03:13 PM CEST, Jan Hubicka wrote:
>> > > +
>> > > + /* At this stage we know that majority of GGC memory is
>reachable.
>> > > + Growing the limits prevents unnecesary invocation of GGC.
>*/
>> > > + ggc_grow ();
>> > >ggc_collect ();
>> >
>> > Isn't the collect h
Hi,
GET_MODE returns VOIDmode on CONST_INT. It happens with -O0. This
patch uses counter_mode on count_exp to get mode. Tested on
Linux/x86-64 without regressions. OK for trunk and 4.9 branch?
Thanks.
H.J.
---
gcc/
2014-04-17 H.J. Lu
PR target/60868
* config/i386/i386.c
Hello!
I am not against it..
However I think there is no danger. I see no potential use of
uninitialized variable.
The use of n_unroll is guarded by n_unroll_found.
Best regards,
Daniel Marjamäki
On Thu, Apr 17, 2014 at 8:45 PM, Bernhard Reutner-Fischer
wrote:
> On 17 April 2014 16:51:23 Konstantin Serebryany
> wrote:
>
>> On Thu, Apr 17, 2014 at 6:27 PM, Bernhard Reutner-Fischer
>> wrote:
>> > On 17 April 2014 16:07, Konstantin Serebryany
>> > wrote:
>> >> Hi,
>> >>
>> >> If you are tr
Hi all,
While configuring libgfortran I'm getting this message:
"libgfortran/configure: line 25938: test: =: unary operator expected"
The script doesn't fail and continues afterwards, but I don't think it's
supposed to give that warning.
This patch makes it go away and makes it more consistent w
On 2014-04-17, 11:29 AM, Richard Sandiford wrote:
Vladimir Makarov writes:
On 2014-04-16, 3:19 PM, Tom de Vries wrote:
Vladimir,
All patches for the fuse-caller-save optimization have been ok-ed. The
only part
not approved is the MIPS-specific part.
The objection of Richard S. is not so much
On 17 April 2014 16:51:23 Konstantin Serebryany
wrote:
On Thu, Apr 17, 2014 at 6:27 PM, Bernhard Reutner-Fischer
wrote:
> On 17 April 2014 16:07, Konstantin Serebryany
> wrote:
>> Hi,
>>
>> If you are trying to modify the libsanitizer files, please read here:
>> https://code.google.com/p/add
Hi all,
While looking at the build logs I noticed a warning while building
tree-ssa-loop-ivcanon.c about a potential use of an uninitialised variable.
This patchlet fixes that warning by initialising it to 0.
Tested arm-none-eabi.
Ok for trunk?
2014-04-17 Kyrylo Tkachov
* tree-ssa
Hi,
we can fix this crash during error recovery very easily, by grouping
together the two conditions leading to skip & early return, in complete
analogy with the single-declaration case (note that we explicitly commit
to tentative parse at the beginning of the function, thus we are good).
Tes
Hello,
Unfortunately, optimization is limited only to bit-fields that have same
bit-field representative (DECL_BIT_FIELD_REPRESENTATIVE), and fields from
different classes do have different representatives.
In given example optimization would merge accesses to x and y bit-fields from
Base class,
> > > +
> > > + /* At this stage we know that majority of GGC memory is reachable.
> > > + Growing the limits prevents unnecesary invocation of GGC. */
> > > + ggc_grow ();
> > >ggc_collect ();
> >
> > Isn't the collect here pointless? I see not in ENABLE_CHECKING, but
> > shouldn't
On Wed, Apr 16, 2014 at 01:40:22PM -0400, Jason Merrill wrote:
> On 04/15/2014 03:56 PM, Marek Polacek wrote:
> >The testsuite doesn't hit this code with C++, but does hit this code
> >with C. The thing is, if we have e.g.
> >enum { A = 128 };
> >void *fn1 (void) __attribute__((assume_aligned (A))
> Ah hah.
>
> /* Make sure we can put it into a register. */
> if (STRICT_ALIGNMENT)
> TYPE_ALIGN (record_type) = MIN (BIGGEST_ALIGNMENT, 2 * POINTER_SIZE);
>
> AArch64 is not a STRICT_ALIGNMENT target, thus the mismatch.
I see. Initially this alignment promotion had been universal, bu
On 17 Apr 2014, at 16:50, Richard Henderson wrote:
> On 04/17/2014 02:00 AM, Tristan Gingold wrote:
>>
>> On 16 Apr 2014, at 17:36, Richard Henderson wrote:
>>
>>> On 04/16/2014 12:39 AM, Eric Botcazou wrote:
> The primary bit of rfc here is the hunk that applies to ada/types.h
> with
Vladimir Makarov writes:
> On 2014-04-16, 3:19 PM, Tom de Vries wrote:
>> Vladimir,
>>
>> All patches for the fuse-caller-save optimization have been ok-ed. The
>> only part
>> not approved is the MIPS-specific part.
>>
>> The objection of Richard S. is not so much the patch itself, but more the
Hi,
I checked in this preapproved patch to generate "xor reg, reg" when
optimizing for size.
H.J.
Index: ChangeLog
===
--- ChangeLog (revision 209487)
+++ ChangeLog (working copy)
@@ -1,3 +1,10 @@
+2014-04-17 H.J. Lu
+
+
On 2014-04-16, 3:19 PM, Tom de Vries wrote:
> Vladimir,
>
> All patches for the fuse-caller-save optimization have been ok-ed. The only
> part
> not approved is the MIPS-specific part.
>
> The objection of Richard S. is not so much the patch itself, but more the idea
> of the hook fn_other_hard_
On Thu, Apr 17, 2014 at 6:27 PM, Bernhard Reutner-Fischer
wrote:
> On 17 April 2014 16:07, Konstantin Serebryany
> wrote:
>> Hi,
>>
>> If you are trying to modify the libsanitizer files, please read here:
>> https://code.google.com/p/address-sanitizer/wiki/HowToContribute
>
> I read that, thanks.
On 04/17/2014 02:00 AM, Tristan Gingold wrote:
>
> On 16 Apr 2014, at 17:36, Richard Henderson wrote:
>
>> On 04/16/2014 12:39 AM, Eric Botcazou wrote:
The primary bit of rfc here is the hunk that applies to ada/types.h
with respect to Fat_Pointer. Given that the Ada type, as defined
Hi Bernd,
I have my copyright mark signed and the process has completed. Now I
am going to answer two more questions before my patch can be
commited right?
Did you copy any
files or text written by someone else in these changes?”
no
[Which files have you changed so fa
On 17 April 2014 16:07, Konstantin Serebryany
wrote:
> Hi,
>
> If you are trying to modify the libsanitizer files, please read here:
> https://code.google.com/p/address-sanitizer/wiki/HowToContribute
I read that, thanks. Patch 3/3 is for current compiler-rt git repo,
please install it there, i do
Hi,
If you are trying to modify the libsanitizer files, please read here:
https://code.google.com/p/address-sanitizer/wiki/HowToContribute
--kcc
On Thu, Apr 17, 2014 at 5:49 PM, Bernhard Reutner-Fischer
wrote:
> Conditionalize usage of dlvsym(), nanosleep(), usleep();
> Conditionalize layout of
Conditionalize usage of dlvsym(), nanosleep(), usleep();
Conditionalize layout of struct sigaction and type of it's member
sa_flags.
Conditionalize glob_t members gl_closedir, gl_readdir, gl_opendir,
gl_flags, gl_lstat, gl_stat.
Check for availability of glob.h for use with above members.
Check for
Conditionalize usage of dlvsym(), nanosleep(), usleep();
Conditionalize layout of struct sigaction and type of it's member
sa_flags.
Conditionalize glob_t members gl_closedir, gl_readdir, gl_opendir,
gl_flags, gl_lstat, gl_stat.
Check for availability of glob.h for use with above members.
Check for
libsanitizer/ChangeLog
2014-04-02 Bernhard Reutner-Fischer
* configure.ac: Check for sizeof(struct statfs64).
* configure, config.h.in: Regenerate.
* sanitizer_common/sanitizer_platform_interceptors.h
(SANITIZER_INTERCEPT_STATFS64): Make conditional on
SI
Respun. First two patches are for gcc, the last one is for upstream
LLVM.
The gcc part was bootstrapped and regtested on x86_64-unknown-linux-gnu
without regressions and bootstrapped on x86_64-unknown-linux-uclibc to
verify that the configury works as expected and that the library links
without er
and the toggle-support hookized
many thanks,
Christian
2014-04-02 Christian Bruel
* target.def (mode_switching): New hook vector.
(toggle_init, toggle_destroy, toggle_set, toggle_test):
New mode toggle hooks.
* targhooks.h (default_toggle_test): Declare.
* basic-block.h (pre_edge_
Hi,
On Thu, 17 Apr 2014, Richard Biener wrote:
> The patch below increases the number of coalescs we attempt
> to also cover unary and binary operations.
This is not usually a good idea if not mitigated by things like register
pressure measurement and using target properties to determine if it'
Hello,
He is a new version of the patch. It hookizes the mode-setting and
mode-toggling macros. Split in 2 parts.
Successfully bootstrapped/regtested on ix86 and SH4/SH4a.
I was able to do a limited build on Epiphany, if someone could give it a
try on it that would be great.
comments ? suggesti
Hi,
This fixes infinite backtrace in __cxa_end_cleanup().
Regtest was finished with no regressions on arm-linux-gnueabi(sf).
The patch posted at:
http://gcc.gnu.org/ml/gcc-patches/2014-04/msg00496.html
Thanks in advance.
Best regards,
Merzlyakov Alexey
On Wed, Apr 16, 2014 at 10:39 PM, Jeff Law wrote:
> On 03/26/14 17:44, Teresa Johnson wrote:
>>
>> Recently I discovered that the profile updates being performed by jump
>> threading were incorrect in many cases, particularly in the case where
>> the threading path contains a joiner. Some of the d
Hi All,
We implemented enhancement for if-convert phase to recognize the
simplest conditional reduction and to transform it vectorizable form,
e.g. statement
if (A[i] != 0) num+= 1; will be recognized.
A new test-case is also provided.
Bootstrapping and regression testing did not show any new
On Thu, Apr 17, 2014 at 10:53:07AM +0200, Richard Biener wrote:
> On Thu, Apr 17, 2014 at 10:37 AM, wrote:
> > From: Trevor Saunders
> >
> > Hi,
> >
> > just removing some dead code.
> >
> > bootstrapped + regtested against r209414 on x86_64-unknown-linux-gnu, ok?
>
> Ok.
Thanks for the quick
On Thu, Apr 17, 2014 at 2:21 PM, Martin Jambor wrote:
> On Wed, Apr 16, 2014 at 11:22:28AM +0200, Richard Biener wrote:
>> On Tue, 15 Apr 2014, Martin Jambor wrote:
>>
>> > Hi,
>> >
>> > back in January in
>> > http://gcc.gnu.org/ml/gcc-patches/2014-01/msg00848.html Eric pointed
>> > out a testcas
On Wed, Apr 16, 2014 at 11:22:28AM +0200, Richard Biener wrote:
> On Tue, 15 Apr 2014, Martin Jambor wrote:
>
> > Hi,
> >
> > back in January in
> > http://gcc.gnu.org/ml/gcc-patches/2014-01/msg00848.html Eric pointed
> > out a testcase where the problem was SRA not scalarizing an aggregate
> > b
On Wed, Apr 16, 2014 at 02:45:37PM -0400, DJ Delorie wrote:
> I'll approve both patches, if you agree to think about a way to solve
> this problem without module-specific configury changes for each such
> command line option. I understand the usefulness of having
> instrumentation, but the configu
--
From: Yury Gribov
Sent: Tuesday, March 25, 2014 11:57AM
To: Jakub Jelinek , Eric Botcazou
, gcc-patches@gcc.gnu.org, Hans-Peter Nilsson
, rdsandif...@googlemail.com
Subject: Re: [RFC] Do not consider volatile asms as optimization barriers #1
On
Hello,
My apologies for inconvenience.
Removed every appearance of -ftree-bitfield-merge from the patch and fixed an
issue with unions.
The rest of the patch is the same as before.
Regards,
Zoran Jovanovic
--
On Thu, 17 Apr 2014, Richard Biener wrote:
>
> The patch below increases the number of coalescs we attempt
> to also cover unary and binary operations. This improves
> initial code generation for code like
>
> int foo (int i, int j, int k, int l)
> {
> int res = i;
> res += j;
> res += k;
The patch below increases the number of coalescs we attempt
to also cover unary and binary operations. This improves
initial code generation for code like
int foo (int i, int j, int k, int l)
{
int res = i;
res += j;
res += k;
res += l;
return res;
}
from
;; res_3 = i_1(D) + j_2(D);
On Thu, 17 Apr 2014, Marc Glisse wrote:
> On Thu, 17 Apr 2014, Richard Biener wrote:
>
> > This fixes PR60849 by properly rejecting non-boolean typed
> > comparisons from valid_gimple_rhs_p so they go through the
> > gimplification paths.
>
> Could you also accept vector comparisons please?
Sur
Thanks! Sorry, missed that!
K
On Thu, Apr 17, 2014 at 2:13 PM, Jakub Jelinek wrote:
> On Wed, Jul 03, 2013 at 08:14:25AM +0200, Uros Bizjak wrote:
>> On Tue, Jul 2, 2013 at 10:32 AM, Kirill Yukhin
>> wrote:
>> > Bootstrap passing. Updated tests passing on BMI-featured HW.
>> >
>> > ChangeLog:
On Thu, 17 Apr 2014, Richard Biener wrote:
This fixes PR60849 by properly rejecting non-boolean typed
comparisons from valid_gimple_rhs_p so they go through the
gimplification paths.
Could you also accept vector comparisons please?
--
Marc Glisse
On Tue, 2014-04-15 at 14:24 -0700, Cary Coutant wrote:
> > + /* If HOST_WIDE_INT is big enough then represent the bound as
> > + a constant value. Note that we need to make sure the type
> > + is signed or unsigned. We cannot just add an unsigned
> > + constant if
On Thu, Apr 17, 2014 at 7:19 AM, Thomas Preud'homme
wrote:
>> From: Richard Biener [mailto:richard.guent...@gmail.com]
>>
>> With handling only the outermost handled-component and then only a
>> selected subset you'll catch many but not all cases. Why not simply
>> use get_inner_reference () here
On Wed, Jul 03, 2013 at 08:14:25AM +0200, Uros Bizjak wrote:
> On Tue, Jul 2, 2013 at 10:32 AM, Kirill Yukhin
> wrote:
> > Bootstrap passing. Updated tests passing on BMI-featured HW.
> >
> > ChangeLog:
> > 2013-07-02 Kirill Yukhin
> >
> > * config/i386/bmiintrin.h (_blsi_u32): New.
>
On Fri, Dec 20, 2013 at 11:45 PM, Rong Xu wrote:
> Here are the results using our internal benchmarks which are a mixed a
> multi-threaded and single-threaded programs.
> This was collected about a month ago but I did not got time to send
> due to an unexpected trip.
>
> cmpxchg gives the worst pe
On Thu, Apr 17, 2014 at 1:30 PM, Jeff Law wrote:
> On 03/18/14 04:13, bin.cheng wrote:
>>
>> Hi,
>> After control flow graph change made by
>> http://gcc.gnu.org/ml/gcc-patches/2014-02/msg01492.html, case
>> gcc.dg/tree-ssa/ssa-dom-thread-4.c is broken on logical_op_short_circuit
>> targets includ
Uros Bizjak writes:
> On Wed, Apr 16, 2014 at 1:16 PM, Rainer Orth
> wrote:
>> Now that 4.9 has branched, it's time to actually remove the obsolete
>> Solaris 9 configuration. Most of this is just legwork and falls under
>> my Solaris maintainership.
>>
>> A couple of questions, though:
>>
>> *
On Sat, Dec 7, 2013 at 12:45 AM, Cong Hou wrote:
> After further reviewing this patch, I found I don't have to change the
> code in tree-vect-stmts.c to allow further type conversion after
> widen-mult operation. Instead, I detect the following pattern in
> vect_recog_widen_mult_pattern():
>
> T1
On 17 April 2014 01:56, Luke Allardyce wrote:
>> Thanks, I was wrong about that.
>>
>> Then I think we should just bite the bullet and provide the new
>> behaviour. If we do have an abi_tag on those types in the next release
>> then we can preserve the old behaviour in the old ABI and use the
>> C+
On 16 Apr 2014, at 17:36, Richard Henderson wrote:
> On 04/16/2014 12:39 AM, Eric Botcazou wrote:
>>> The primary bit of rfc here is the hunk that applies to ada/types.h
>>> with respect to Fat_Pointer. Given that the Ada type, as defined in
>>> s-stratt.ads, does not include alignment, I can't
On Thu, Apr 17, 2014 at 10:37 AM, wrote:
> From: Trevor Saunders
>
> hi,
>
> its a useful warning, and helps catch bugs in the next two patches.
>
> bootstrap + regtest passed on x86_64-unknown-linux-gnu, ok?
Ok.
Thanks,
Richard.
> Trev
>
> 2014-03-19 Trevor Saunders
>
> * configur
On Thu, Apr 17, 2014 at 10:37 AM, wrote:
> From: Trevor Saunders
>
> Hi,
>
> simplification allowed by previous patch.
>
> bootstrap + regtest passed on x86_64-unknown-linux-gnu, ok?
Ok.
Thanks,
Richard.
> Trev
>
> 2014-03-19 Trevor Saunders
>
> * pass_manager.h (pass_manager::regi
On Thu, Apr 17, 2014 at 10:37 AM, wrote:
> From: Trevor Saunders
>
> Hi,
>
> just removing some dead code.
>
> bootstrapped + regtested against r209414 on x86_64-unknown-linux-gnu, ok?
Ok.
Thanks,
Richard.
> Trev
>
> 2014-03-19 Trevor Saunders
>
> * pass_manager.h (pass_manager::re
From: Trevor Saunders
hi,
its a useful warning, and helps catch bugs in the next two patches.
bootstrap + regtest passed on x86_64-unknown-linux-gnu, ok?
Trev
2014-03-19 Trevor Saunders
* configure.ac: Check for -Woverloaded-virtual and enable it if found.
* configure: Reg
From: Trevor Saunders
Hi,
simplification allowed by previous patch.
bootstrap + regtest passed on x86_64-unknown-linux-gnu, ok?
Trev
2014-03-19 Trevor Saunders
* pass_manager.h (pass_manager::register_dump_files_1): Remove
declaration.
* passes.c (pass_manager::register_d
From: Trevor Saunders
Hi,
just removing some dead code.
bootstrapped + regtested against r209414 on x86_64-unknown-linux-gnu, ok?
Trev
2014-03-19 Trevor Saunders
* pass_manager.h (pass_manager::register_dump_files_1): Adjust.
* passes.c (pass_manager::register_dump_files_1
This fixes PR60836 by emitting a non-proper PHI argument to the
incoming edge.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2014-04-16 Richard Biener
PR tree-optimization/60836
* tree-vect-loop.c (vect_create_epilog_for_reduction): Force
This fixes PR60849 by properly rejecting non-boolean typed
comparisons from valid_gimple_rhs_p so they go through the
gimplification paths.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2014-04-16 Richard Biener
PR middle-end/60849
* tree-ss
This fixes running into the exponential value-graph -> SLP tree
expansion by artificially limiting the overall SLP tree size.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2014-04-16 Richard Biener
PR tree-optimization/60841
* tree-vect-dat
On Thu, Apr 17, 2014 at 7:30 AM, Jeff Law wrote:
> On 03/18/14 04:13, bin.cheng wrote:
>>
>> Hi,
>> After control flow graph change made by
>> http://gcc.gnu.org/ml/gcc-patches/2014-02/msg01492.html, case
>> gcc.dg/tree-ssa/ssa-dom-thread-4.c is broken on logical_op_short_circuit
>> targets includ
On Thu, Apr 17, 2014 at 4:30 AM, Jan Hubicka wrote:
> Hi,
> the testcase shows problem where cpp implicit alias is always inline and
> symtab_remove_unreachable_nodes removes the body of aliased function before
> inlininghappens. The real problem is that cgraph_state is set too early
> and not as
On Thu, 17 Apr 2014, Jan Hubicka wrote:
> Hi,
> while compiling firefox I noticed that -fprofile-generage -flto goes to 8GB.
> It turns out that this is caused by ipa_reference no longer being disabled
> becaus in_lto_p became flag that is set later (it is not clear to me why it
> needs to be this
94 matches
Mail list logo
