It started failing after the following commit: 32e90dc6a0cda45 ("PR
rtl-optimization/61047").
The change that made xtensa backend go ICE looks completely unrelated,
and indeed, the issue is caused by the side effect of
compute_frame_size() function call hidden in the
INITIAL_ELIMINATION_OFFSET mac
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Spanish team of translators. The file is available at:
http://translationproject.org/latest/gcc/es.po
(This file, 'gcc-6.2.0.es.po', has just
Attached is an updated patch that works around the problem with
the definition of the NOTE_DATA macro discussed below. I've
raised bug 78174 for it and temporarily worked around it in
the patch. I'll see if I can come up with a patch to fix the
macro the "right way" but would prefer to do that s
On Oct 31, 2016, at 7:19 PM, Michael Meissner
wrote:
>
> One question is how many of the billions and billions (ok, 1,345) of the
> rs6000
> built-ins would be improved by expanding them in gimple time rather than rtl?
>
Hundreds and hundreds of them. All of the basic operators, many of the m
> On Oct 31, 2016, at 7:09 PM, Jakub Jelinek wrote:
>
> On Mon, Oct 31, 2016 at 05:28:42PM -0500, Bill Schmidt wrote:
>> The PowerPC back end loses performance on vector intrinsics, because
>> currently
>> all of them are treated as calls throughout the middle-end phases and only
>> expanded wh
On Mon, Oct 31, 2016 at 06:49:20PM -0500, Bill Schmidt wrote:
> >
> > On Oct 31, 2016, at 5:28 PM, Bill Schmidt
> > wrote:
> >
> > The other way would be to require a specific option on the command line
> > to use the new dispatch mechanism. When the option is present, we would
> > prede
On Mon, Oct 31, 2016 at 05:28:42PM -0500, Bill Schmidt wrote:
> The PowerPC back end loses performance on vector intrinsics, because currently
> all of them are treated as calls throughout the middle-end phases and only
> expanded when they reach RTL. Our version of altivec.h currently defines the
>
> On Oct 31, 2016, at 5:28 PM, Bill Schmidt wrote:
>
> The other way would be to require a specific option on the command line
> to use the new dispatch mechanism. When the option is present, we would
> predefine a macro such as __PPC_FAST_VECTOR__, which would then gate the
> usage i
On Mon, Oct 31, 2016 at 06:04:47PM -0500, Segher Boessenkool wrote:
> On Mon, Oct 31, 2016 at 05:25:56PM -0400, Michael Meissner wrote:
> > +(define_insn "vsx_xvcvsxwdp_df"
> > + [(set (match_operand:DF 0 "vsx_register_operand" "=ws")
> > + (unspec:DF [(match_operand:V4SI 1 "vsx_register_operand
On Mon, Oct 31, 2016 at 05:25:56PM -0400, Michael Meissner wrote:
> +(define_insn "vsx_xvcvsxwdp_df"
> + [(set (match_operand:DF 0 "vsx_register_operand" "=ws")
> + (unspec:DF [(match_operand:V4SI 1 "vsx_register_operand" "wa")]
> +UNSPEC_VSX_CVSXWDP))]
> + "VECTOR_UNIT_VSX_P
Hi,
The PowerPC back end loses performance on vector intrinsics, because currently
all of them are treated as calls throughout the middle-end phases and only
expanded when they reach RTL. Our version of altivec.h currently defines the
public names of overloaded functions (like vec_add) to be #def
Hi!
Some automatic VAR_DECLs don't get DECL_RTL set - e.g. if its SSA_NAMEs
expand to multiple rtls, then there is not a single one that can be used.
Using DECL_RTL on such VAR_DECLs ICEs.
I've tried to just return 0 in nonoverlapping_memrefs_p if either
DECL_RTL_SET_P (expr{x,y}) wasn't true, bu
This patch adds an optimization that I noticed towards the end of working on my
previous patch to allow SImode into vector registers.
This patch adds optimization when you are extracting an element using a 32-bit
integer with constant element number, and then converting the value to double.
While
On Mon, Oct 31, 2016 at 3:33 PM, Jakub Jelinek wrote:
> On Mon, Oct 31, 2016 at 02:42:15PM -0400, Jason Merrill wrote:
>> On 10/20/2016 02:52 PM, Jakub Jelinek wrote:
>> >@@ -8476,7 +8498,16 @@ size_of_die (dw_die_ref die)
>> > size += DWARF_OFFSET_SIZE;
>> > break;
>> > case
The attached patch does a little change in
combine.c:combine_simplify_rtx() to prevent a "simplification"
where the rtl code gets more complex in reality. The complete
description of the change can be found in the commit comment in
the attached patch.
The patch reduces the number of patterns in t
On 10/21/2016 04:30 AM, Jiong Wang wrote:
All DW_OP_* of the expression are grouped together inside the PARALLEL,
and those operations which don't have RTL mapping are wrapped by
UNSPEC. The parsing algorithm is simply something like:
foreach elem inside PARALLEL
if (UNSPEC)
{
On Mon, Oct 31, 2016 at 3:38 PM, Jakub Jelinek wrote:
> On Mon, Oct 31, 2016 at 03:33:22PM -0400, Jason Merrill wrote:
>> OK.
>
> This patch needs the incremental
> http://gcc.gnu.org/ml/gcc-patches/2016-10/msg02440.html
> patch (now successfully bootstrapped/regtested on x86_64-linux and
> i686-l
On Mon, Oct 31, 2016 at 03:33:22PM -0400, Jason Merrill wrote:
> OK.
This patch needs the incremental
http://gcc.gnu.org/ml/gcc-patches/2016-10/msg02440.html
patch (now successfully bootstrapped/regtested on x86_64-linux and
i686-linux). Is that one ok too?
I think it would be better to commit th
On Mon, Oct 31, 2016 at 02:42:15PM -0400, Jason Merrill wrote:
> On 10/20/2016 02:52 PM, Jakub Jelinek wrote:
> >@@ -8476,7 +8498,16 @@ size_of_die (dw_die_ref die)
> > size += DWARF_OFFSET_SIZE;
> > break;
> > case dw_val_class_range_list:
> >- size += DWARF_OFFSET_S
OK.
OK.
On 10/31/2016 02:38 PM, Jakub Jelinek wrote:
On Mon, Oct 31, 2016 at 11:25:26AM -0400, Jason Merrill wrote:
On 10/19/2016 07:30 PM, Jakub Jelinek wrote:
This patch adds support for DWARF5 .debug_line{,_str} section format,
though only if !DWARF2_ASM_LINE_DEBUG_INFO, because otherwise
.debug_lin
On 10/20/2016 02:52 PM, Jakub Jelinek wrote:
@@ -8476,7 +8498,16 @@ size_of_die (dw_die_ref die)
size += DWARF_OFFSET_SIZE;
break;
case dw_val_class_range_list:
- size += DWARF_OFFSET_SIZE;
+ if (dwarf_split_debug_info
+ && dwarf_version
On Mon, Oct 31, 2016 at 11:25:26AM -0400, Jason Merrill wrote:
> On 10/19/2016 07:30 PM, Jakub Jelinek wrote:
> >This patch adds support for DWARF5 .debug_line{,_str} section format,
> >though only if !DWARF2_ASM_LINE_DEBUG_INFO, because otherwise
> >.debug_line is emitted by the assembler. For th
This patch cleans up all code related to the frame pointer. On AArch64 we
emit a frame chain even in cases where the frame pointer is not required.
So make this explicit by introducing a boolean emit_frame_chain in
aarch64_frame record.
When the frame pointer is enabled but not strictly required
I've created a new branch ira-select for work on experimental
algorithm of calculations of pseudo register classes.
The current algorithm in IRA (file ira-costs.c) was adopted from old
regclass.c. It has a big disadvantage which is in ignoring a fact
that operands should be in the same alternati
On 31/10/16 17:15, Segher Boessenkool wrote:
If maybe_record_trace_start fails because the CFI is inconsistent on two
paths into a block it currently just ICEs. This changes it to also dump
the CFI on those two paths in the dump file; debugging it without that
information is hopeless.
Tested o
I think this is obvious, the following code in combine.c which intends
to fallthrough some switch cases is not marked with 'gcc_fallthrough'
as it should be, thus producing warnings during compilation.
---
Fritz Reese
2016-10-31 Fritz Reese
gcc/combine.c (simplify_compare_const): Mar
If maybe_record_trace_start fails because the CFI is inconsistent on two
paths into a block it currently just ICEs. This changes it to also dump
the CFI on those two paths in the dump file; debugging it without that
information is hopeless.
Tested on powerpc64-linux {-m32,-m64}. Is this okay for
On 10/31/2016 01:04 PM, Jakub Jelinek wrote:
On Mon, Oct 31, 2016 at 12:58:23PM -0400, Jason Merrill wrote:
On 10/14/2016 03:41 PM, Jakub Jelinek wrote:
Another set of GNU extensions that were accepted into DWARF5, so we should
emit them even for -gstrict-dwarf -gdwarf-5, and for -gdwarf-5 shou
On Mon, Oct 31, 2016 at 12:58:23PM -0400, Jason Merrill wrote:
> On 10/14/2016 03:41 PM, Jakub Jelinek wrote:
> >Another set of GNU extensions that were accepted into DWARF5, so we should
> >emit them even for -gstrict-dwarf -gdwarf-5, and for -gdwarf-5 should use
> >the accepted standard opcodes i
OK.
On 10/14/2016 03:41 PM, Jakub Jelinek wrote:
Another set of GNU extensions that were accepted into DWARF5, so we should
emit them even for -gstrict-dwarf -gdwarf-5, and for -gdwarf-5 should use
the accepted standard opcodes instead of the corresponding GNU ones.
Hmm, I wonder if we also want to
All the different cases in output_loc_list could use brief comments.
Let's keep loc_list_idx, output_loclists_offsets, and
assign_location_list_indexes together in the file.
OK with those changes.
Jason
On 10/31/2016 09:45 AM, Andreas Schwab wrote:
> On Okt 31 2016, Vineet Gupta wrote:
>
>> This silences tons of -Wformat= warnings when building ARC Linux kernel
>> with gcc 6.x (and restores the ARC gcc 4.8.x behaviour) which had
>> similar fix.
>>
>> gcc/
>> 2016-10-28 Vineet Gupta
>>
>>
This silences tons of -Wformat= warnings when building ARC Linux kernel
with gcc 6.x (and restores the ARC gcc 4.8.x behaviour) which had
similar fix.
gcc/
2016-10-28 Vineet Gupta
* config/arc/arc.h (SIZE_TYPE): define as unsigned int.
* (PTRDIFF_TYPE): define as int.
Signed-of
OK, thanks.
On Mon, Oct 31, 2016 at 12:13 PM, Ville Voutilainen
wrote:
> On 31 October 2016 at 15:31, Jason Merrill wrote:
>> Good idea. You might put the reuse in a separate function in order to
>> hide it from the optimizer.
>
>
> Ok, new patch, tested on Linux-x64, ok for trunk?
>
> 2016-10-
On Mon, Oct 31, 2016 at 12:44 PM, Jakub Jelinek wrote:
> On Mon, Oct 31, 2016 at 10:15:11AM -0400, Jason Merrill wrote:
>> On 10/17/2016 05:39 PM, Jakub Jelinek wrote:
>> >(dwarf_version >= 5 ? 128 : 64)
>>
>> Please make this a macro. OK with that change.
>
> DWARF_LARGEST_DATA_FORM_BITS ? Or d
On Okt 31 2016, Vineet Gupta wrote:
> This silences tons of -Wformat= warnings when building ARC Linux kernel
> with gcc 6.x (and restores the ARC gcc 4.8.x behaviour) which had
> similar fix.
>
> gcc/
> 2016-10-28 Vineet Gupta
>
> * config/arc/arc.h (SIZE_TYPE): define as unsigned int.
On Mon, Oct 31, 2016 at 10:13:16AM -0400, Jason Merrill wrote:
> OK.
This patch is on top of the
- DWARF5 http://gcc.gnu.org/ml/gcc-patches/2016-10/msg01202.html
- DW_OP_{implicit_pointer,entry_value,{const,regva
On 10/31/2016 06:39 AM, Tobias Burnus wrote:
Martin Sebor wrote:
Attached is an updated patch that adds checks for excessive sizes
and bounds (those in excess of SIZE_MAX / 2), and also enables
the same checking for strcat and strncat). This version also
fixes an issue with the interpretation o
On Mon, Oct 31, 2016 at 10:15:11AM -0400, Jason Merrill wrote:
> On 10/17/2016 05:39 PM, Jakub Jelinek wrote:
> >(dwarf_version >= 5 ? 128 : 64)
>
> Please make this a macro. OK with that change.
DWARF_LARGEST_DATA_FORM_BITS ? Or do you have better name?
Jakub
This silences tons of -Wformat= warnings when building ARC Linux kernel
with gcc 6.x (and restores the ARC gcc 4.8.x behaviour) which had
similar fix.
gcc/
2016-10-28 Vineet Gupta
* config/arc/arc.h (SIZE_TYPE): define as unsigned int.
* (PTRDIFF_TYPE): define as int.
Signed-of
On October 31, 2016 4:50:08 PM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>As the testcase shows, while reassociation of vector multiplication
>has been enabled, the eliminate_using_constants optimization
>isn't enabled for integral vectors (only for floating point vectors),
>so e.g. if we have more
On 31 October 2016 at 15:31, Jason Merrill wrote:
> Good idea. You might put the reuse in a separate function in order to
> hide it from the optimizer.
Ok, new patch, tested on Linux-x64, ok for trunk?
2016-10-31 Ville Voutilainen
Add tests for a const member and a reference member for
Hi!
As the testcase shows, while reassociation of vector multiplication
has been enabled, the eliminate_using_constants optimization
isn't enabled for integral vectors (only for floating point vectors),
so e.g. if we have more than one { ~0, ~0, ... } vectors in there
coming from NEGATE_EXPRs, we
Hi Andrew,
Please find the updated patch.
What is new:
- The .def files are having a comment block on how to add new lines.
- The arc_seen_option is not used.
- The arc_cpu* variables are not used.
Please let me know if I miss something,
Claudiu
gcc/
2016-05-09 Claudiu Zissulescu
*
Hi!
On Mon, Oct 24, 2016 at 04:20:25PM +0200, Jakub Jelinek wrote:
> While writing a testcase for __builtin_launder, I've noticed we don't parse
> __builtin_shuffle or __builtin_addressof properly (as well as do error
> recovery e.g. for typeid in constant expression etc.).
>
> The problem is tha
wg21.link/p0136 significantly changes the specification of C++11
inheriting constructors so that they become an implementation detail
rather than a language-level construct; instead, overload resolution
and such are done on the constructor from the base, and the artificial
constructor in the derive
On Mon, Oct 31, 2016 at 04:09:48PM +0100, Steven Bosscher wrote:
> On Sun, Oct 30, 2016 at 8:10 PM, Segher Boessenkool wrote:
> > This patch solves this problem by simply running the
> > duplicate_computed_gotos
> > pass again, as long as it does any work. The patch looks much bigger than
> > it
On 10/19/2016 07:30 PM, Jakub Jelinek wrote:
This patch adds support for DWARF5 .debug_line{,_str} section format,
though only if !DWARF2_ASM_LINE_DEBUG_INFO, because otherwise
.debug_line is emitted by the assembler. For that we'll need some
coordination with gas, dunno if we want a new as dire
On Sun, Oct 30, 2016 at 8:10 PM, Segher Boessenkool wrote:
> This patch solves this problem by simply running the duplicate_computed_gotos
> pass again, as long as it does any work. The patch looks much bigger than
> it is, because I factored out two routines to simplify the control flow.
It's ma
On 10/31/2016 08:04 AM, Jeff Law wrote:
On 10/28/2016 03:30 PM, Michael Eager wrote:
On 10/28/2016 11:14 AM, Waldemar Brodkorb wrote:
Hi,
uClibc-ng can be used for Microblaze architecture.
It is regulary tested with qemu-system-microblaze in little and
big endian mode.
2016-10-28 Waldemar Br
On Sat, 2016-10-29 at 12:10 -0500, Segher Boessenkool wrote:
Hi Carl,
>
> On Fri, Oct 28, 2016 at 08:11:11AM -0700, Carl E. Love wrote:
> > Manuel López-Ibáñez
> > Martin v. Löwis
> > H.J. Lu
> > +Carl Love
> > Christophe Lyon
>
On 10/28/2016 03:30 PM, Michael Eager wrote:
On 10/28/2016 11:14 AM, Waldemar Brodkorb wrote:
Hi,
uClibc-ng can be used for Microblaze architecture.
It is regulary tested with qemu-system-microblaze in little and
big endian mode.
2016-10-28 Waldemar Brodkorb
gcc/
* config
On 10/31/2016 12:11 PM, Richard Biener wrote:
> On Mon, Oct 31, 2016 at 11:18 AM, Richard Sandiford
> wrote:
>> Richard Biener writes:
>>> On Mon, Oct 31, 2016 at 10:58 AM, Richard Sandiford
>>> wrote:
Richard Biener writes:
> On Mon, Oct 31, 2016 at 10:10 AM, Martin Liška wrote:
Attached patch builds on previous libgcc patch and implements
TARGET_EXPAND_DIVMOD_LIBFUNC target hook.
The same approach can also be used on other targets without hardware
divmod insn.
Patch also fixes several gcc.dg/divmod-?.c testsuite failures for
x86_64 multilibs.
2016-10-31 Uros Bizjak
This function will be used in a follow-up patch to implement
TARGET_EXPAND_DIVMOD_LIBFUNC for x86 targets. Other targets can call
this function, so IMO it should be part of a generic library.
2016-10-31 Uros Bizjak
* Makefile.in (LIB2_DIVMOD_FUNCS): Add _divmoddi4.
* libgcc2.c (__divmo
On Mon, Oct 31, 2016 at 10:25 AM, Jakub Jelinek wrote:
> On Mon, Oct 31, 2016 at 09:52:28AM -0400, Jason Merrill wrote:
>> On 10/14/2016 01:33 PM, Jakub Jelinek wrote:
>> >This also uses the infrastructure of the langhook patch I've sent earlier.
>> >It emits (if not strict dwarf) DW_AT_inline on
On 10/17/2016 05:45 PM, Jakub Jelinek wrote:
+/* First abbrev_id that can be optimized based on usage. */
+static unsigned int abbrev_opt_start;
+
+/* Vector of usage counts during build_abbrev_table. Indexed by
+ abbrev_id - abbrev_opt_start. */
+static vec abbrev_usage_count;
+
+/* Vector
Hi,
gcc.dg/lto/pr60449_0.c fails to link for the avr target because it
doesn't have an implementation for gettimeofday. This patch therefore
skips the test for avr.
Committed to trunk as obvious.
Regards
Senthil
gcc/testsuite/ChangeLog
2016-10-31 Senthil Kumar Selvaraj
* g
On 31/10/16 13:42, Richard Earnshaw (lists) wrote:
On 31/10/16 11:54, Kyrill Tkachov wrote:
On 24/10/16 17:15, Andrew Pinski wrote:
On Mon, Oct 24, 2016 at 7:27 AM, Kyrill Tkachov
wrote:
Hi all,
When storing a 64-bit immediate that has equal bottom and top halves we
currently
synthesize the
On Mon, Oct 31, 2016 at 09:52:28AM -0400, Jason Merrill wrote:
> On 10/14/2016 01:33 PM, Jakub Jelinek wrote:
> >This also uses the infrastructure of the langhook patch I've sent earlier.
> >It emits (if not strict dwarf) DW_AT_inline on explicit or implicit inline
> >variables, and also tweaks dwa
I am testing the following to fix another latent PTA bug uncovered
by pointer comparsion folding.
Bootstrap and regtest running on x86_64-unknown-linux-gnu.
Richard.
2016-10-31 Richard Biener
PR tree-optimization/78047
* tree-ssa-structalias.c (push_fields_onto_fieldstack):
On 10/17/2016 05:39 PM, Jakub Jelinek wrote:
(dwarf_version >= 5 ? 128 : 64)
Please make this a macro. OK with that change.
Jason
OK.
Jason
On 10/24/2016 03:09 PM, Jakub Jelinek wrote:
On Mon, Oct 24, 2016 at 02:34:04PM -0400, Jason Merrill wrote:
On Mon, Oct 24, 2016 at 10:29 AM, Jakub Jelinek wrote:
This is another addition in DWARF5. The patch emits these attributes
only for DW_TAG_subprogram for non-static ref-qualified membe
OK.
On 10/14/2016 01:33 PM, Jakub Jelinek wrote:
This also uses the infrastructure of the langhook patch I've sent earlier.
It emits (if not strict dwarf) DW_AT_inline on explicit or implicit inline
variables, and also tweaks dwarf2out so that for inline static data members
we consider in-class decla
On 31/10/16 11:54, Kyrill Tkachov wrote:
>
> On 24/10/16 17:15, Andrew Pinski wrote:
>> On Mon, Oct 24, 2016 at 7:27 AM, Kyrill Tkachov
>> wrote:
>>> Hi all,
>>>
>>> When storing a 64-bit immediate that has equal bottom and top halves we
>>> currently
>>> synthesize the repeating 32-bit pattern t
On 10/28/2016 01:13 PM, tbsaunde+...@tbsaunde.org wrote:
From: Trevor Saunders
HI,
This series changes various variables type from rtx to rtx_insn * so that the
remaining patches in this series
http://gcc.gnu.org/ml/gcc-patches/2016-10/msg01353.html can be applied.
patches bootstrapped and re
OK.
On Sun, Oct 30, 2016 at 2:53 PM, Ville Voutilainen
wrote:
> So, how about adding these? They should give us regression tests
> that make sure launder does the right in in case some optimizations
> attempt to reuse const/reference members.
Good idea. You might put the reuse in a separate function
OK.
Jason
On 2016.10.31 at 13:46 +0100, Richard Biener wrote:
>
> This is an updated patch for PR78035 which is about optimizing
> address comparisons using points-to info vs. directly looking
> at two addr-exprs. I've given up trying to dissect a predicate
> more useful than decl_binds_to_current_def_p fr
This fixes leftovers in /tmp from -Werror=suggest-final-types.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2016-10-31 Richard Biener
PR lto/78129
* lto.c (do_whole_program_analysis): Bail out after errors
from WPA analysis.
Index:
This is an updated patch for PR78035 which is about optimizing
address comparisons using points-to info vs. directly looking
at two addr-exprs. I've given up trying to dissect a predicate
more useful than decl_binds_to_current_def_p from
symtab_node::equal_address_to and thus I'm going with the f
OK.
On Sun, Oct 30, 2016 at 3:53 PM, Mark Wielaard wrote:
> On Tue, Oct 25, 2016 at 01:57:09AM +0200, Mark Wielaard wrote:
>> I think the only thing "blocking" the patch from going in is that
>> nobody made a decission on how the actual warning option should be
>> named. I think the suggestion fo
Martin Sebor wrote:
> Attached is an updated patch that adds checks for excessive sizes
> and bounds (those in excess of SIZE_MAX / 2), and also enables
> the same checking for strcat and strncat). This version also
> fixes an issue with the interpretation of anti-ranges in the
> first patch. The
On Sat, Oct 29, 2016 at 1:09 PM, Jakub Jelinek wrote:
> On Sat, Oct 29, 2016 at 12:41:43PM -0400, Jason Merrill wrote:
>> On Sat, Oct 29, 2016 at 12:09 PM, Jakub Jelinek wrote:
>> > Apparently the driver reorders the options, -std=* options come before
>> > all -f* options, so both of the followi
On 10/31/2016 11:07 AM, Rainer Orth wrote:
> Hi Martin,
>
>> Using priority {cd}tors on a target that does not support that can cause
>> failures (see the PR).
>> Apart from that, I decided to use priority 100 for both gcov_init and
>> gcov_exit functions as
>> the reserved range includes priority
Ping.
Thanks,
Kyrill
On 24/10/16 12:30, Kyrill Tkachov wrote:
Ping.
https://gcc.gnu.org/ml/gcc-patches/2016-10/msg00839.html
Thanks,
Kyrill
On 12/10/16 11:23, Kyrill Tkachov wrote:
Hi all,
I'm looking at the aarch64 prologue and epilogue generation code and I noticed
many of the helper
fun
Ping.
Thanks,
Kyrill
On 24/10/16 14:12, Kyrill Tkachov wrote:
On 24/10/16 12:29, Kyrill Tkachov wrote:
Ping.
https://gcc.gnu.org/ml/gcc-patches/2016-10/msg01321.html
I just noticed my original ChangeLog entry was truncated.
It is
2016-10-04 Kyrylo Tkachov
PR target/77822
* conf
On 24/10/16 17:15, Andrew Pinski wrote:
On Mon, Oct 24, 2016 at 7:27 AM, Kyrill Tkachov
wrote:
Hi all,
When storing a 64-bit immediate that has equal bottom and top halves we
currently
synthesize the repeating 32-bit pattern twice and perform a single X-store.
With this patch we synthesize th
On Sun, Oct 23, 2016 at 03:37:22PM -0700, Andrew Pinski wrote:
> On Tue, Nov 17, 2015 at 2:10 PM, Andrew Pinski wrote:
> >
> > The way the current code was written assumes all cores have an unique part
> > num which is not true. What they have is an unique pair of implementer and
> > part num. T
On Mon, Oct 31, 2016 at 11:18 AM, Richard Sandiford
wrote:
> Richard Biener writes:
>> On Mon, Oct 31, 2016 at 10:58 AM, Richard Sandiford
>> wrote:
>>> Richard Biener writes:
On Mon, Oct 31, 2016 at 10:10 AM, Martin Liška wrote:
> On 10/31/2016 01:12 AM, Richard Sandiford wrote:
Richard Biener writes:
> On Mon, Oct 31, 2016 at 10:58 AM, Richard Sandiford
> wrote:
>> Richard Biener writes:
>>> On Mon, Oct 31, 2016 at 10:10 AM, Martin Liška wrote:
On 10/31/2016 01:12 AM, Richard Sandiford wrote:
> Richard Biener writes:
>> On Thu, Oct 27, 2016 at 5:06 PM, M
On Mon, Oct 31, 2016 at 10:58 AM, Richard Sandiford
wrote:
> Richard Biener writes:
>> On Mon, Oct 31, 2016 at 10:10 AM, Martin Liška wrote:
>>> On 10/31/2016 01:12 AM, Richard Sandiford wrote:
Richard Biener writes:
> On Thu, Oct 27, 2016 at 5:06 PM, Martin Liška wrote:
>> On 10/
Hi Martin,
> Using priority {cd}tors on a target that does not support that can cause
> failures (see the PR).
> Apart from that, I decided to use priority 100 for both gcov_init and
> gcov_exit functions as
> the reserved range includes priority 100. Moreover, I enhanced test-cases
> we have.
ju
Yeah, In the test it's reasonable, just used one extra register.
I'm currently running some benchmarks to make sure those are OK too.
Regards,
Tamar
From: Bin.Cheng
Sent: Friday, October 28, 2016 12:38:28 PM
To: Tamar Christina
Cc: Pat Haugen; Maxim Kuvy
Richard Biener writes:
> On Mon, Oct 31, 2016 at 10:10 AM, Martin Liška wrote:
>> On 10/31/2016 01:12 AM, Richard Sandiford wrote:
>>> Richard Biener writes:
On Thu, Oct 27, 2016 at 5:06 PM, Martin Liška wrote:
> On 10/27/2016 03:35 PM, Richard Biener wrote:
>> On Thu, Oct 27, 2016
When a symbol cannot be demangled in ada_demangle a new demangled VEC
will be allocated without deleting the demangled VEC already in use.
Running testsuite/test-demangle under valgrind will show the leak for
this entry in testsuite/demangle-expected:
# Elaborated flag (not demangled)
--f
On Fri, Oct 28, 2016 at 4:06 PM, Will Schmidt wrote:
> On Fri, 2016-10-28 at 08:31 -0500, Will Schmidt wrote:
>> On Fri, 2016-10-28 at 10:38 +0200, Richard Biener wrote:
>> > On Thu, Oct 27, 2016 at 5:37 PM, Will Schmidt
>> > wrote:
>> > > Hi,
>> > >
>> > > Per PR72747, A statement such as "v =
On Mon, Oct 31, 2016 at 10:10 AM, Martin Liška wrote:
> On 10/31/2016 01:12 AM, Richard Sandiford wrote:
>> Richard Biener writes:
>>> On Thu, Oct 27, 2016 at 5:06 PM, Martin Liška wrote:
On 10/27/2016 03:35 PM, Richard Biener wrote:
> On Thu, Oct 27, 2016 at 9:41 AM, Martin Liška wrot
On 29/10/16 16:57, Jakub Jelinek wrote:
On Sat, Oct 29, 2016 at 10:07:22AM +0200, Andreas Schwab wrote:
That breaks Ada:
a-teioed.adb: In function 'Ada.Text_Io.Editing.Format_Number':
a-teioed.adb:127:4: error: alignment of array elements is greater than element
size
a-teioed.adb:127:4: error
On Fri, Oct 28, 2016 at 1:17 PM, Richard Biener
wrote:
> On Thu, Oct 27, 2016 at 3:37 PM, Bin Cheng wrote:
>> Hi,
>> During analysis, vect_slp checks if statements of a group are isomorphic to
>> each other, specifically, all statements have to be isomorphic to the first
>> one. Apparently, op
On Mon, Oct 31, 2016 at 8:26 AM, wrote:
> From: Trevor Saunders
>
> A demonstration we can do the same thing with a gimple test as -fno-tree-evrp
> but somewhat more precisely.
>
> I tested this passes on x86_64-linux-gnu, ok?
Looks good to me with the indentation fixed (once the FE is on trun
On 21/10/16 13:30, Bernd Schmidt wrote:
On 10/21/2016 02:04 PM, Jiong Wang wrote:
+ /* Locate the end of existing REG_NOTES in NEW_RTX. */
+ rtx *ptail = ®_NOTES (new_rtx);
+ while (*ptail != NULL_RTX)
+ptail = &XEXP (*ptail, 1);
I was thinking along the lines of something like this
On 21/10/16 09:30, Jiong Wang wrote:
Currently, GCC only support DW_CFA_expression in dwarf module, this patch
extend the support to DW_CFA_val_expression which share the same code
mostly the same code with DW_CFA_expression.
Meanwhile the existed dwarf expression parser only allows expressions
On Sun, Oct 30, 2016 at 08:31:47PM +0100, Jan Kratochvil wrote:
> On Fri, 21 Oct 2016 21:32:42 +0200, Jakub Jelinek wrote:
> > This patch changes the .debug_info headers to follow the current
> > specification (I still hope the useless padding1/padding2 fields will be
> > removed), and also changes
1 - 100 of 106 matches
Mail list logo
