On Dec 7, 2017, Jeff Law wrote:
> On 11/09/2017 07:34 PM, Alexandre Oliva wrote:
>> This patch completes the infrastructure for the introduction of
>> statement frontiers in C-family languages.
> Note I expect minor updates will be necessary due to the Cilk+ removal.
> Such changes are pre-appro
On Dec 7, 2017, Jeff Law wrote:
> On 11/09/2017 07:34 PM, Alexandre Oliva wrote:
>> Introduce a command line option to enable statement frontiers, enabled
>> by default in optimized builds with DWARF2+ debug information.
> OK once all prereqs are ack'd.
Thanks, here's what's installed, FTR:
>F
On Dec 7, 2017, Jeff Law wrote:
> On 11/09/2017 07:34 PM, Alexandre Oliva wrote:
>> The inline_entry hook will be given a definition in a later patch.
>>
>> for gcc/ChangeLog
>>
>> * debug.h (gcc_debug_hooks): Add inline_entry.
>> * dbxout.c (dbx_debug_hooks, xcoff_debug_hooks): Likewise.
>>
On Dec 11, 2017, Jeff Law wrote:
> On 11/09/2017 07:34 PM, Alexandre Oliva wrote:
>> This patch introduces an option to enable the generation of location
>> views along with location lists. The exact format depends on the
>> void
>> +dw2_asm_output_symname_uleb128 (const char *lab1 ATTRIBUTE_UNU
On Nov 10, 2017, Alexandre Oliva wrote:
> Output DW_AT_entry_pc based on markers.
Here's an updated version of the patch.
[IEPM] Introduce inline entry point markers
Output DW_AT_entry_pc based on markers.
Introduce DW_AT_GNU_entry_view as a DWARF extension.
If views are enabled are we're no
On Dec 7, 2017, Jeff Law wrote:
> On 11/09/2017 07:34 PM, Alexandre Oliva wrote:
>> This patch introduces a number of new macros and functions that will
> OK. Again, I think this can probably go in as-is.
Thanks, FTR here's the installed patch:
>From c64f38bf4d2f6c50fdc5122d129d2ad34088d19c M
On Dec 7, 2017, Jeff Law wrote:
> On 11/09/2017 07:34 PM, Alexandre Oliva wrote:
>> This patch removes unused RTL functions, introduces alternate ones for
>> use in a later SFN patch, and regroups other related functions so that
>> they appear in a more consistent order.
>>
>> for gcc/ChangeLo
On 12/11/2017 10:29 AM, Jakub Jelinek wrote:
Hi!
Diagnostics should not start with capital letters unless the first word is
capitalized that way even in the middle of a sentence.
Fixed thusly, ok for trunk?
2017-12-11 Jakub Jelinek
* config/aarch64/aarch64.c (aarch64_print_operand)
On Dec 7, 2017, Richard Biener wrote:
>> + FOR_EACH_SSA_USE_OPERAND (use_p, stmt, iter, SSA_OP_ALL_USES)
> SSA_OP_USE avoids walking virtual uses
and we don't want to walk those because we already know writes to
memory are not going to be dead anyway, I suppose.
>> + {
>> +
On Dec 11, 2017, Jeff Law wrote:
>> + gcc_assert (path->length () == 0 || path->last ()->e == e);
>> + if (path->length () == 0)
>> +return estimate_threading_killed_stmts (e->dest);
>> +
>> + int total = 0;
>> + int i = 0;
>> + jump_thread_edge *je;
>> + FOR_EACH_VEC_ELT (*path, i, je)
Hello Julia,
On 25 Oct 12:02, Koval, Julia wrote:
> Hi,
> This patch enables VAES isaset option. The doc for isaset and instruction:
> https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf
>
> Ok for trunk?
Your patch is OK.
Hello Julia,
On 08 Nov 12:32, Koval, Julia wrote:
> Hi, this patch enables VAESDEC instruction from VAES isaset, defined here:
> https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf
>
> Ok for trunk?
Patch is OK. Checked in
Jakub Jelinek writes:
> Hi!
>
> On Fri, Dec 08, 2017 at 08:10:08PM +0100, Christophe Lyon wrote:
>> >> Can you check?
>> >
>> > I think that's a separate preexisting problem. Could you file a PR?
>> >
>>
>> Sure, I filed:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83335
>>
>> > Personally
On Tue, Dec 12, 2017 at 06:21:37AM +, Richard Sandiford wrote:
> Jakub Jelinek writes:
> > Hi!
> >
> > On Fri, Dec 08, 2017 at 08:10:08PM +0100, Christophe Lyon wrote:
> >> >> Can you check?
> >> >
> >> > I think that's a separate preexisting problem. Could you file a PR?
> >> >
> >>
> >> Su
On Mon, 11 Dec 2017, Jakub Jelinek wrote:
> On Mon, Dec 11, 2017 at 06:00:11PM +0100, Kilian Verhetsel wrote:
> > Jakub Jelinek writes:
> > > Of course it can be done efficiently, what we care most is that the body
> > > of
> > > the vectorized loop is efficient.
> >
> > That's fair, I was look
101 - 115 of 115 matches
Mail list logo