The assertion should accept all constructs built by Call_to_gnu.
Tested on x86_64-suse-linux, applied on the mainline.
2015-09-14 Eric Botcazou
* gcc-interface/utils2.c (gnat_rewrite_reference) : Add
another acceptable pattern for the RHS.
--
Eric BotcazouIndex: gcc-interfa
No functional changes, tested on x86_64-suse-linux, applied on the mainline.
2015-09-14 Eric Botcazou
* gcc-interface/gigi.h (ref_filename): Delete.
(Sloc_to_locus): Add clean_column parameter defaulting to false.
(build_call_raise): Adjust comment.
(build_call
On 09/13/2015 08:24 PM, Mark Wielaard wrote:
commit 97505bd0e4ac15d86c2a302cfebc5f1a4fc2c2e8
Author: Mark Wielaard
Date: Fri Sep 11 23:54:15 2015 +0200
PR28901 -Wunused-variable ignores unused const initialised variables in C
This is ok.
Bernd
We are phasing out the GNAT encoding scheme in the debugging information so
STABS is considered obsolete for Ada.
Tested on x86_64-suse-linux, applied on the mainline.
2015-09-14 Pierre-Marie de Rodat
* gcc-interface/misc.c (gnat_post_options): Issue a warning if
generating
* shrink-wrap.c (requires_stack_frame_p): Fix formatting.
(dup_block_and_redirect): Delete function.
(can_dup_for_shrink_wrapping): New function.
(fix_fake_fallthrough_edge): New function.
(try_shrink_wrapping): Rewrite function.
(convert_to_simple_r
On 09/11/2015 11:49 PM, Nathan Sidwell wrote:
This patch implements that optimization. As the comment at the head of
the code says, we first find 'cycle-equivalent' BBs. These are ones
that we determine are in the same (set of) loops, in the closed graph.
Such equivalent BBs form the entry and
On 07/09/15 13:16, Kyrill Tkachov wrote:
Hi Gerald,
On 07/09/15 12:31, Gerald Pfeifer wrote:
On Wed, 2 Sep 2015, Kyrill Tkachov wrote:
My thinking was that when we introduce some new command-line option we
list it here and give a short description of it (new -mcpu values, for
example). Howeve
Hi,
as documented, STACK_CHECK_PROTECT is supposed to be an "estimate of the
amount of stack required to propagate an exception". It's (mainly) for Ada
and it needs to distinguish the various EH schemes, which might have different
needs. While the current setting is OK for the front-end SJLJ
On Mon, 14 Sep 2015, Kyrill Tkachov wrote:
> And here is the patch.
Thanks.
> I'll apply it in 48 hours if there's no objection.
No need to wait. ;-)
Gerald
On 09/11/2015 05:15 PM, John David Anglin wrote:
On 2015-09-11 4:15 AM, Bernd Schmidt wrote:
On 09/11/2015 01:21 AM, John David Anglin wrote:
As noted in the PR, expand_atomic_compare_and_swap can generate wrong
code when libcalls are emitted
for the sync_compare_and_swap and the result compari
On Sat, 12 Sep 2015, Eric Botcazou wrote:
> > * fold-const.c (fold_binary_loc): Move simplifying of comparisons
> > against the highest or lowest possible integer ...
> > * match.pd: ... as patterns here.
>
> This incorrectly dropped the calls to omit_one_operand_loc, resulting in the
On 09/11/2015 03:28 PM, Tom de Vries wrote:
This patch adds handling of a DEFPARAMENUM macro, which is similar to
the DEFPARAM macro, but allows the values to be named.
So the definition of param parloop-schedule becomes:
...
DEFPARAMENUM PARAM_PARLOOPS_SCHEDULE,
"parloops-schedul
On Mon, 14 Sep 2015, Richard Biener wrote:
> On Sat, 12 Sep 2015, Eric Botcazou wrote:
>
> > > * fold-const.c (fold_binary_loc): Move simplifying of comparisons
> > > against the highest or lowest possible integer ...
> > > * match.pd: ... as patterns here.
> >
> > This incorrectly dropped
> Still trying to reproduce, but I suppose you hit
The testcase fails as of r227729 on x86-64/Linux.
> /* Comparisons with the highest or lowest possible integer of
> the specified precision will have known values. */
> (simplify
> (cmp (convert?@2 @0) INTEGER_CST@1)
> (if ((INTEGRAL_T
Committed.
Bernd
Index: ChangeLog
===
--- ChangeLog (revision 227737)
+++ ChangeLog (working copy)
@@ -1,3 +1,7 @@
+2015-09-14 Bernd Schmidt
+
+ * MAINTAINERS: Update my email address.
+
2015-09-01 James Bowman
* MAINTAIN
On Fri, Sep 11, 2015 at 03:28:01PM +0200, Tom de Vries wrote:
> On 11/09/15 12:57, Jakub Jelinek wrote:
> >On Fri, Sep 11, 2015 at 12:55:00PM +0200, Tom de Vries wrote:
> >>>Hi,
> >>>
> >>>this patch adds a param parloops-schedule=<0-4>, which sets the omp
> >>>schedule
> >>>for loops paralellized
On Fri, 11 Sep 2015, Bernd Schmidt wrote:
> On 07/08/2015 04:39 PM, Richard Biener wrote:
> >
> > This introduces a :s flag to match expressions which enforces
> > the expression to have a single-use if(!) the simplified
> > expression is larger than one statement.
>
> This seems to be missing d
Michael Collison writes:
> Here is a modified patch that takes your comments into account. Breaking
> on depth == 0 with '>' does not work due to the code looking for whitespace.
What goes wrong? Just to make sure we're talking about the same thing,
I meant that in:
(match_operand:FOO> ...
Built .info and .pdf on x86_64-linux, applied.
Richard.
2015-09-14 Richard Biener
* doc/match-and-simplify.texi: Update for changed syntax
of inner ifs and the new switch expression.
Index: gcc/doc/match-and-simplify.texi
=
On 09/14/2015 10:23 AM, Eric Botcazou wrote:
as documented, STACK_CHECK_PROTECT is supposed to be an "estimate of the
amount of stack required to propagate an exception". It's (mainly) for Ada
and it needs to distinguish the various EH schemes, which might have different
needs. While the curre
> Ok, so it's folding
>
> x == 127 ? .gnat_rcheck_CE_Overflow_Check ("overflow_sum3.adb", 14);, 0 :
> (short_short_integer) x + 1
>
> <= 127
>
> where op0 (the COND_EXPR) does not have TREE_SIDE_EFFECTS set but
> its operand 1 has:
>
> (gdb) p debug_tree (op0)
> type public visited QI
>
On 11/09/15 14:19, Bill Schmidt wrote:
A secondary concern for powerpc is that REDUC_MAX_EXPR produces a scalar
that has to be broadcast back to a vector, and the best way to implement
it for us already has the max value in all positions of a vector. But
that is something we should be able to f
On Mon, 14 Sep 2015, Eric Botcazou wrote:
> > Ok, so it's folding
> >
> > x == 127 ? .gnat_rcheck_CE_Overflow_Check ("overflow_sum3.adb", 14);, 0 :
> > (short_short_integer) x + 1
> >
> > <= 127
> >
> > where op0 (the COND_EXPR) does not have TREE_SIDE_EFFECTS set but
> > its operand 1 has:
> >
Hi,
this patchlet makes it possible to get rid of useless EH cleanups generated at
-O0 in Ada for simple constructs involving VLAs:
declare
S : String (1 .. N);
begin
...
end;
by duplicating finally blocks that contain only a stack restore. Then the EH
optimization machinery (wh
On 09/10/2015 06:57 PM, Martin Sebor wrote:
>>> There is quite a bit of documentation of _FORTIFY_SOURCE that explains
>>> its effect on user code.
>>
>> I think there are only random blog articles discussing aspects of it,
>> most of them slightly incorrect or outdated.
>
> _FORTIFY_SOURCE is a
On Wed, Sep 9, 2015 at 11:07 PM, Jeff Law wrote:
> On 08/31/2015 05:30 AM, Richard Biener wrote:
>>
>> On Mon, Aug 31, 2015 at 7:49 AM, Mikhail Maltsev
>> wrote:
>>>
>>> Hi, all!
>>>
>>> This patch removes some conditional compilation from GCC. In this patch I
>>> define
>>> a macro CHECKING_P, w
Hi All,
For what it's worth I have uploaded a new patch that changes the name
from STRICT_FMIN/MAX to just FMIN/FMAX, although I realise that this
discussion has not yet been resolved. I have also added scheduling
attributes to the aarch64 instructions.
Regards,
David Sherwood.
ChangeLog:
2015-
Steve Kargl suspected that read_dir.f90 would fail on all BSDs with the
recent change. At least for DragonFly BSD, he is correct:
https://gcc.gnu.org/ml/gcc-testresults/2015-09/msg01222.html
Please consider incorporating the attached patch which sets the test for
xfail on dragonfly as well as fr
> gcc/ChangeLog:
>
> * config/mips/i6400.md (i6400_fpu_intadd, i6400_fpu_logic)
> (i6400_fpu_div, i6400_fpu_cmp, i6400_fpu_float,
> i6400_fpu_store)
> (i6400_fpu_long_pipe, i6400_fpu_logic_l, i6400_fpu_float_l)
> (i6400_fpu_mult): New cpu units.
> (i6400_msa_add
... concretely, I tested successfully the below.
Thanks,
Paolo.
Index: cp/parser.c
===
--- cp/parser.c (revision 227737)
+++ cp/parser.c (working copy)
@@ -7591,8 +7591,9 @@ cp_parser_new_expression (cp_parser*
On 09 Sep 10:20, Uros Bizjak wrote:
> On Wed, Sep 9, 2015 at 10:12 AM, Uros Bizjak wrote:
> > On Tue, Sep 8, 2015 at 5:49 PM, Ilya Enkovich
> > wrote:
> >
> > Please depend new changes to insn patterns to TARGET_STV. This way,
> > non-STV compiles will behave exactly as now.
> >
> > +;; Math-dep
On 09/14/15 04:11, Bernd Schmidt wrote:
This looks like it could potentially go into sese.c instead.
yeah, I looked at that to see if it had any goodies -- AFAICT it does
processing of already-identified SESE regions. It could certainly be abstracted
to there, if there are more general nee
On 27/08/15 15:07, Marcus Shawcroft wrote:
> On 27 July 2015 at 15:33, Ramana Radhakrishnan
> wrote:
>
>> Ramana Radhakrishnan
>>
>> PR target/63304
>> * config/aarch64/aarch64.c (aarch64_expand_mov_immediate): Handle
>> nopcrelative_literal_loads.
>> (aarch6
To make progess here I think adding new optabs is fine. So can you
split out that part and implement builtin expanders
for fmin/max instead?
Btw, FMIN/MAX_EXPR are not commutative AFAIK because of behavior for
fmax (-NaN, NaN)
vs. fmax (NaN, -NaN)?
Richard.
On Mon, Sep 14, 2015 at 12:36 PM, Dav
On Thu, Sep 10, 2015 at 9:30 AM, Sujoy Saraswati wrote:
> Hi,
> Here is a modified patch for this. The change this time is in
> fold-const.c and real.c.
>
> Bootstrap and regression tests on x86_64-linux-gnu and
> aarch64-unknown-linux-gnu passed with changes done on trunk.
>
> Is this fine ?
>
>
Hi,
The attached patch fixes PR 67061.
Tested on sh-elf trunk r227682 with
make -k check RUNTESTFLAGS="--target_board=sh-sim
\{-m2/-ml,-m2/-mb,-m2a/-mb,-m4/-ml,-m4/-mb,-m4a/-ml,-m4a/-mb}"
Committed to trunk as r227750.
Will backport to GCC 5 branch later.
Cheers,
Oleg
gcc/ChangeLog:
PR
On Mon, 2015-09-14 at 10:47 +0100, Alan Lawrence wrote:
> On 11/09/15 14:19, Bill Schmidt wrote:
> >
> > A secondary concern for powerpc is that REDUC_MAX_EXPR produces a scalar
> > that has to be broadcast back to a vector, and the best way to implement
> > it for us already has the max value in a
Hi!
This patch makes sure that when we remove all depend clauses from a
construct (e.g. because all of them refer to invalid iterations), we don't
leave ordered construct without clauses in (because that means omp ordered
threads). Furthermore, it attempts to optimize adjacent #pragma omp ordered
On 14/09/15 11:09, Jakub Jelinek wrote:
On Fri, Sep 11, 2015 at 03:28:01PM +0200, Tom de Vries wrote:
On 11/09/15 12:57, Jakub Jelinek wrote:
On Fri, Sep 11, 2015 at 12:55:00PM +0200, Tom de Vries wrote:
Hi,
this patch adds a param parloops-schedule=<0-4>, which sets the omp schedule
for loop
On 14/09/15 16:28, Tom de Vries wrote:
On 14/09/15 11:09, Jakub Jelinek wrote:
On Fri, Sep 11, 2015 at 03:28:01PM +0200, Tom de Vries wrote:
On 11/09/15 12:57, Jakub Jelinek wrote:
On Fri, Sep 11, 2015 at 12:55:00PM +0200, Tom de Vries wrote:
Hi,
this patch adds a param parloops-schedule=<0-
OK.
Jason
Hi,
The attached patch fixes an issue where a declare'd variable,
with the link clause, wasn't marked as offloadable.
Committed after regtesting on x86_64.
Thanks!
Jim
Index: libgomp/testsuite/libgomp.oacc-c-c++-common/declare-4.c
On September 14, 2015 11:23:28 AM GMT+02:00, Richard Biener
wrote:
>On Fri, 11 Sep 2015, Bernd Schmidt wrote:
>
>> On 07/08/2015 04:39 PM, Richard Biener wrote:
>> >
>> > This introduces a :s flag to match expressions which enforces
>> > the expression to have a single-use if(!) the simplified
>
On September 14, 2015 11:36:13 AM GMT+02:00, Christian Bruel
wrote:
>Hi,
>
>This patch moves the FPU flags settings and checks to the attribute
>hooks. .e.g neon must be checked in arm_option_check_internal. FPU name
>
>is emitted before each function and arm_fpu_index is Saved to be
>handled
>
On Mon, Sep 14, 2015 at 2:03 PM, Ilya Enkovich wrote:
> On 09 Sep 10:20, Uros Bizjak wrote:
>> On Wed, Sep 9, 2015 at 10:12 AM, Uros Bizjak wrote:
>> > On Tue, Sep 8, 2015 at 5:49 PM, Ilya Enkovich
>> > wrote:
>> >
>> > Please depend new changes to insn patterns to TARGET_STV. This way,
>> > no
On 14/09/15 10:52, Bernd Schmidt wrote:
I'm curious why
this would be a param rather than a -f option.
Hi Bernd,
parloops-chunk-size is also a param, so I think it would make sense to
have parloops-schedule as a param as well.
[ So, in order for parloops to generate:
#pragma omp for sche
On Mon, Sep 14, 2015 at 07:08:33AM +0900, Kaz Kojima wrote:
> Rich Felker wrote:
> > I'm pretty sure this will still apply to trunk, but I can check that
> > and add the changelog entry. Is there something I should read on the
> > form or just follow the example from my last patch where you added
On 14/09/15 17:58, Rich Felker wrote:
trunk. For the ChangeLog message, do I need to list both configure and
configure.ac or just the latter? And should configure be included in
the patch like I did, or regenerated when the patch is applied?
list both
i think it's ok to fix configure manually
On 09/12/2015 10:44 PM, David Miller wrote:
> From: Eric Botcazou
> Date: Sat, 12 Sep 2015 16:04:09 +0200
>
>>> Richard, Eric, any objections?
>>
>> Do we really need to promote to 64-bit if TARGET_ARCH64? Most 32-bit
>> instructions are still available. Otherwise this looks good to me.
>
> N
Hello!
tree-parloops pass names loop functions as $loopfn. These names are
later renamed for NO_DOLLAR_IN_LABEL targets to _loopfn.
alpha-linux-gnu is not in this group, so it fails
FAIL: gcc.dg/gomp/notify-new-function-3.c scan-tree-dump-times
ompexpssa "Added new ssa gimple function foo._lo
On Mon, Sep 14, 2015 at 06:06:02PM +0100, Szabolcs Nagy wrote:
> On 14/09/15 17:58, Rich Felker wrote:
> >trunk. For the ChangeLog message, do I need to list both configure and
> >configure.ac or just the latter? And should configure be included in
> >the patch like I did, or regenerated when the p
It occurred to me that we weren't warning about this with -Wabi and a
lower -fabi-version. This patch fixes that.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit e924f74640ecd18240fb514f99b0d5b5ceeeffb7
Author: Jason Merrill
Date: Wed Sep 2 16:32:15 2015 -0400
PR c++/44282
Ping. (Rerevert with 5 lines extra paranoia in scalarizable_type_p).
Thanks, Alan
On 08/09/15 13:43, Martin Jambor wrote:
Hi,
On Mon, Sep 07, 2015 at 02:15:45PM +0100, Alan Lawrence wrote:
In-Reply-To: <55e0697d.2010...@arm.com>
On 28/08/15 16:08, Alan Lawrence wrote:
Alan Lawrence wrote:
On September 14, 2015 1:39:28 PM GMT+02:00, Christian Bruel
wrote:
>This patch splits the neon_builtins initialization into 2 internals
>functions. One for NEON and one for CRYPTO, each one guarded by its own
>
>predicate. arm_init_neon_builtins is now global to be called from
>arm_valid_target
On 09/10/2015 10:28 PM, David Malcolm wrote:
Attached is a work-in-progress patch kit implementing these ideas.
I posting it now to get feedback: some parts of it may be ready to
commit, but other parts are definitely *not* ready yet.
It's hard to provide meaningful review under these condition
The attached testcase triggered an ICE because the builtin expansion
code passed the output of expand_normal directly to the SET_FP[SC]R
generator, without forcing it into a register first.
Tested on aarch64-linux-gnu. OK to install?
Thanks,
Richard
gcc/
* config/aarch64/aarch64-builtin
This patch by Chris Manghane changes the Go frontend to ignore the
result context when determining the type of constant expressions.
This fixes https://golang.org/issue/11566 . Bootstrapped and ran Go
testsuite on x86_64-unknown-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERG
On 09/14/2015 01:45 AM, Manuel López-Ibáñez wrote:
The flag diagnostic_context::some_warnings_are_errors controls whether
to give the message "all warnings being treated as errors". However, when
warnings are buffered and then discarded, this flag is not reset. It turns
out we do not need this fl
On 09/14/2015 07:54 PM, Richard Sandiford wrote:
This patch splits optabs up as follows:
- optabs-query.[hc]: IL-independent functions for querying what a target
can do natively.
- optabs-tree.[hc]: tree and gimple query functions (an extension of
optabs-query.[hc]).
- opt
On 08/09/2015 22:47, François Dumont wrote:
> On 07/09/2015 13:03, Jonathan Wakely wrote:
>> On 05/09/15 22:53 +0200, François Dumont wrote:
>>>I remember Paolo saying once that we were not guarantiing any abi
>>> compatibility for debug mode. I haven't found any section for
>>> unversioned sym
Hi
Here is what I had in mind when talking about moving debug checks to
the lightweight debug checks.
Sometimes the checks have been simply moved resulting in a simpler
debug vector implementation (front, back...). Sometimes I copy the
checks in a simpler form and kept the debug one too t
From: Richard Henderson
Date: Mon, 14 Sep 2015 10:20:00 -0700
> There's a possibility of benefit though -- br and movr only work with DImode.
> You may want to examine the generated code to decide one way or another.
>
> It's possible that the extra comparison instructions don't really matter
>
working on another task, I found the idiom used in lower_oacc_loop_enter_exit
rather confusing. I've applied this to use two different loops, clearly going
in different directions, rather than a single loop and an internal mechanism to
make one of the instances go backwards.
nathan
2015-09-14
On 09/14/2015 12:36 AM, Sebastian Huber wrote:
Ping.
On 04/09/15 08:26, Sebastian Huber wrote:
Index: htdocs/gcc-6/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v
retrieving revision 1.25
diff -u -r1.25 chan
On 09/14/2015 04:11 AM, Richard Biener wrote:
On Wed, Sep 9, 2015 at 11:07 PM, Jeff Law wrote:
On 08/31/2015 05:30 AM, Richard Biener wrote:
On Mon, Aug 31, 2015 at 7:49 AM, Mikhail Maltsev
wrote:
Hi, all!
This patch removes some conditional compilation from GCC. In this patch I
define
a
On 09/13/2015 05:45 PM, Manuel López-Ibáñez wrote:
The flag diagnostic_context::some_warnings_are_errors controls whether
to give the message "all warnings being treated as errors". However, when
warnings are buffered and then discarded, this flag is not reset. It turns
out we do not need this fl
On 09/09/2015 04:33 PM, Mark Wielaard wrote:
On Thu, 2015-09-10 at 00:03 +0200, Jakub Jelinek wrote:
On Wed, Sep 09, 2015 at 04:01:07PM -0600, Jeff Law wrote:
* gcc.dg/nonnull-4.c: New test.
* g++.dg/warn/nonnull3.C: Likewise.
If the tests are the same, perhaps stick just one
On 09/10/2015 02:28 PM, David Malcolm wrote:
location_get_source_line takes an expanded_location, but the column
is irrelevant; it just needs a filename and line number.
This change is used by, but independent of, the new implementation of
diagnostic_show_locus later in the kit, so am breaking t
> -Original Message-
> From: Richard Henderson [mailto:r...@redhat.com]
> Sent: Wednesday, September 09, 2015 7:46 PM
> To: Jason Merrill; Moore, Catherine; gcc-patches@gcc.gnu.org
> Cc: Matthew Fortune; Ian Lance Taylor
> Subject: Re: [RFA] Compact EH Patch
>
> On 09/09/2015 01:35 PM, J
On 09/10/2015 02:28 PM, David Malcolm wrote:
This patch adds an easy way to write tests for expected multiline
output. For example we can test carets and underlines for
a particular diagnostic with:
/* { dg-begin-multiline-output "" }
typedef struct _GMutex GMutex;
^~~
On 09/11/2015 07:55 AM, Michael Matz wrote:
Hi,
On Thu, 10 Sep 2015, David Malcolm wrote:
Does anyone know why this was "carefully packed" and to what extent
this matters? I'm adding an extra 8 bytes to it (or 4 if we eliminate
the existing location_t). As far as I can see, these are
short-l
On 09/09/2015 05:09 PM, Paolo Carlini wrote:
> +@item -Wsubobject-linkage @r{(C++ and Objective-C++ only)}
> +@opindex Wsubobject-linkage
> +@opindex Wno-subobject-linkage
> +Warn if a class type has a base or a field whose type uses the anonymous
> +namespace or depends on a type with no linkage.
On 09/10/2015 02:28 PM, David Malcolm wrote:
The function "diagnostic_show_locus" gains new functionality in the
next patch, so this preliminary patch breaks it out into a new source
file, diagnostic-show-locus.c, along with a couple of related functions.
gcc/ChangeLog:
* Makefile.in (OB
On 09/14/2015 11:43 AM, Bernd Schmidt wrote:
It's hard to provide meaningful review under these conditions. My advice
would be to resubmit the things that are ready now and can stand on
their own so that we can get them out of the way first. Also, gather
memory/time information before posting the
On September 14, 2015 4:30:23 PM GMT+02:00, Christian Bruel
wrote:
>Finally, the final part of the patch set does the attribute target
>parsing and checking, redefines the preprocessor macros and implements
>the inlining rules.
>
>testcases and documentation included.
@@ -29501,6 +29532,8 @@
On 14/09/15 20:27 +0200, François Dumont wrote:
Hi
Here is what I had in mind when talking about moving debug checks to
the lightweight debug checks.
Ah yes, I hadn't thought about removing reundant checks from the
__gnu_debug containers, but that makes sense.
Sometimes the checks have
On September 14, 2015 12:47:23 PM GMT+02:00, Christian Bruel
wrote:
>This patch defines and uses accessors for the current fpu type fields,
>based on switchable arm_fpu_index rather than defuncted arm_fpu_desc.
* config/arm/arm.c (arm_fpu_desc): Remove.
(all_fpus): Make global.
Passing void * to avail_expr_hash was an artifact of the old htab
interface. Since we're no longer using that interface and call the
hashing routine directly, we can just pass in the right type and avoid
the annoying casting.
This simplifies class-ifying the available expression stack and r
Hello,
I'd like to initiate discussion on vectorization of loops which boundaries are
not
aligned to VF. Main target for this optimization right now is x86's AVX-512,
which
features per-element embedded masking for all instructions.
The main goal for this mail is to agree on overall design of the
On Mon, 14 Sep 2015, Richard Biener wrote:
> To make progess here I think adding new optabs is fine. So can you
> split out that part and implement builtin expanders
> for fmin/max instead?
>
> Btw, FMIN/MAX_EXPR are not commutative AFAIK because of behavior for
> fmax (-NaN, NaN)
> vs. fmax (Na
On Mon, 14 Sep 2015, Richard Biener wrote:
> I'll leave the correctness part of the patch to Joseph who knows FP
> arithmetic better than me,
> implementation-wise this is ok if you fix the REAL_CST sharing issue.
Changing fold_abs_const is wrong - abs of sNaN is sNaN, no exceptions
raised. Cha
On September 14, 2015 9:32:54 PM GMT+02:00, Jeff Law wrote:
>On 09/10/2015 02:28 PM, David Malcolm wrote:
>>
>> multiline.exp is used by prune.exp; hence we need to load it before
>> prune.exp via *load_gcc_lib* for the testsuites of the various
>> non-"gcc" support libraries (e.g. boehm-gc).
>?!
Hi Florian,
On 09/14/2015 09:41 PM, Florian Weimer wrote:
This warning is
+enabled by default.
Maybe add a sentence why this is bad? I can only guess, but I suspect
the reason is this: Such types are necessarily specific to a single
translation unit because any definition in another translati
On 09/14/2015 02:38 PM, Bernhard Reutner-Fischer wrote:
On September 14, 2015 9:32:54 PM GMT+02:00, Jeff Law
wrote:
On 09/10/2015 02:28 PM, David Malcolm wrote:
multiline.exp is used by prune.exp; hence we need to load it
before prune.exp via *load_gcc_lib* for the testsuites of the
various
On 09/08/2015 05:17 AM, Kai Tietz wrote:
Hi,
This patch is the first part of obsoleting 'shorten_compare' function
for folding.
It adjusts the uses of 'shorten_compare' to ignore folding returned by
it, and adds
missing pattterns to match.pd to allow full bootstrap of C/C++ without
regressions.
I've committed this patch, which replaces IFN_GOACC_FORK and IFN_GOACC_JOIN with
a single IFN_UNIQUE function. This makes the fork & join handling slightly more
tricky, but reduces the invasion into the rest of the compiler -- the unique
predicate function only need check a single value and is
2015-09-14 Rich Felker
* gcc/configure.ac: Change target pattern for sh TLS support
test from "sh[34]-*-*" to "sh[123456789lbe]*-*-*".
* gcc/configure: Regenerate.
diff --git a/gcc/configure b/gcc/configure
index 846c996..6fb11a7 100755
--- a/gcc/configure
+++ b/gcc/con
Rich Felker wrote:
> 2015-09-14 Rich Felker
>
> * gcc/configure.ac: Change target pattern for sh TLS support
> test from "sh[34]-*-*" to "sh[123456789lbe]*-*-*".
> * gcc/configure: Regenerate.
The patch is OK. I've committed it with removing gcc/ from
the file names in gcc/
On Fri, Sep 11, 2015 at 03:40:53PM +0100, Jiong Wang wrote:
> >> A quick check shows > 30% more functions shrink-wrapped during
> >> bootstrapping by a the following command:
> >>
> >> cd $TOP_BUILD ; find . -name "*.pro_and_epilogue" | xargs grep
> >> "Perform.*shrink" | wc -l
> >
> > Wow, that
On Mon, 2015-09-14 at 13:42 -0600, Jeff Law wrote:
> On 09/14/2015 11:43 AM, Bernd Schmidt wrote:
> > It's hard to provide meaningful review under these conditions. My advice
> > would be to resubmit the things that are ready now and can stand on
> > their own so that we can get them out of the way
On 09/14/2015 06:17 PM, Paolo Carlini wrote:
Hi Florian,
On 09/14/2015 09:41 PM, Florian Weimer wrote:
This warning is
+enabled by default.
Maybe add a sentence why this is bad? I can only guess, but I suspect
the reason is this: Such types are necessarily specific to a single
translation un
+void foo(void *bar) __attribute__((nonnull(1)));
+
+void foo(void *bar) { if (!bar) abort(); } /* { dg-warning "null" "argument ‘bar’
compared to NULL" } */
This looks like a very useful enhancement. Since the change is limited
to build_binary_op in the two front ends I wonder if the warning a
Apparently arm64 GNU/Linux does not provide ustat, and the linker
warns about it when using glibc. This patch to libgo avoids providing
syscall.Ustat on arm64 GNU/Linux, since it will apparently never work.
Since I was touching Makefile.am I rebuilt with automake 1.11.6, the
new GCC standard.
Bo
On Mon, Sep 7, 2015 at 8:22 AM, Jonathan Wakely wrote:
> And we could get rid of the _Empty type, because std::bitset<0> is an
> empty type anyway, so if we made _S_cache_size()==0 when _UseCache is
> false then in the current code we could just unconditionally use:
>
> using _CacheT = std::bitse
On Wed, Sep 2, 2015 at 8:32 PM, Richard Biener
wrote:
> On Wed, Sep 2, 2015 at 5:50 AM, Bin Cheng wrote:
>> Hi,
>> When calling get_shiftadd_cost, the mult_op is stripped at caller places.
>> We should look into unnecessary conversion in op1 before checking equality,
>> otherwise it computes wron
Just realized that I missed the updated patch before. Here it is...
Thanks,
bin
On Tue, Sep 8, 2015 at 6:07 PM, Bin.Cheng wrote:
> On Tue, Sep 8, 2015 at 6:06 PM, Bin.Cheng wrote:
>> On Wed, Sep 2, 2015 at 10:12 PM, Richard Biener
>> wrote:
>>> On Wed, Sep 2, 2015 at 5:26 AM, Bin Cheng wrote
Ping.
On Thu, Aug 27, 2015 at 5:41 PM, Bin Cheng wrote:
> Hi,
> This is a rework for
> https://gcc.gnu.org/ml/gcc-patches/2015-07/msg02335.html, with review
> comments addressed. For now, SCEV may compute iv base in the form of
> "(signed T)((unsigned T)base + step))". This complicates other
>
Would anyone like me to spend some more time on this and perhaps clear up some
of the TODO items?
(Unlike some of you, I'm retired. I have time for this.)
Louis
== == == == == == Forwarded message == == == == == ==
>From : Louis Krupp
To : "gcc-patches","fortran"
Date : Wed, 09 Sep 2015 00:2
This was the most glaring case, and would result in LRA crashing
if this code snippet was actually hit on big-endian, since
simplify_gen_subreg() will return NULL in such a case and then
we try to blindly emit a move to 'subreg'.
There is code in match_reload which seems to have a similar problem
99 matches
Mail list logo
