Sebastian Perta writes:
> Please let me know if this is OK, Thank you!
Sorry for the delay, it's OK and I committed it for you with a few minor
changes to make it work with today's tree.
Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78809
Wilco changed:
What|Removed |Added
CC||wdijkstr at arm dot com
--- Comment #4 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82274
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Fri, 2017-10-13 at 13:01 +0100, Pedro Alves wrote:
> On 10/13/2017 10:26 AM, Richard Biener wrote:
> > On Fri, Oct 13, 2017 at 2:40 AM, David Malcolm > > wrote:
> > > From: Trevor Saunders
> > >
> > > I had a go at updating Trevor's unique_ptr
-pc-linux-gnu/8.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/home/su/software/tmp/gcc/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 8.0.0 20171013 (experimental) [trunk revision 253721] (GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78809
Qing Zhao changed:
What|Removed |Added
CC||qing.zhao at oracle dot com
--- Comment #3
On 7 October 2017 at 12:35, Prathamesh Kulkarni
wrote:
> On 7 October 2017 at 11:23, Jan Hubicka wrote:
>>> On 6 October 2017 at 06:04, Jan Hubicka wrote:
>>> >> Hi Honza,
>>> >> Thanks for the detailed suggestions, I have updated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82548
Bug ID: 82548
Summary: After -r 253646 GCC 8.0 can't build cross compiler for
mingw32
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
On 13/10/17 14:06 -0600, Sandra Loosemore wrote:
On 10/13/2017 06:35 AM, Jonathan Wakely wrote:
This adds an item to the list of options for the -fdump-tree option,
because we show an example using 'vect' but don't document it.
OK for trunk?
No, I think this patch is addressing an imaginary
On Fri, Oct 13, 2017 at 10:25 PM, Richard Earnshaw
wrote:
> On 13/10/17 18:28, vladimir.mezent...@oracle.com wrote:
>> On 10/12/2017 03:40 AM, Richard Earnshaw wrote:
>>> On 12/10/17 06:21, vladimir.mezent...@oracle.com wrote:
From: Vladimir Mezentsev
On 13/10/17 18:28, vladimir.mezent...@oracle.com wrote:
> On 10/12/2017 03:40 AM, Richard Earnshaw wrote:
>> On 12/10/17 06:21, vladimir.mezent...@oracle.com wrote:
>>> From: Vladimir Mezentsev
>>>
>>> FMA (floating-point multiply-add) instructions are supported on
On Fri, Oct 13, 2017 at 05:08:51PM +0100, Richard Sandiford wrote:
> Yeah, I agree this'll change the handling of paradoxical subregs that
> occupy more words than the SUBREG_REG, but I think the new version is
> correct. The comment says:
>
> /* If the destination is anything other than
On Fri, Oct 13, 2017 at 6:38 AM, Jan Hubicka wrote:
> Hi,
> this patch enables check that no edge probabilities are missing.
This caused a bootstrap failure on aarch64-linux-gnu with go enabled.
But I see you have disabled the code for now.
Just for reference the failure:
Hi,
this patch fixes costs of basic operations for Zen. It also models SSE more
carefully. ix86_rtx_costs is still based on x87 costs of operations which is
not very realistic today when x87 and SSE costs are often quite different.
The latencies in this patch are based on Agner Fog's values and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81404
David Malcolm changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
Hi,
To continue the review of the AArch64 frame code I tried a few examples
to figure out what it does now. For initial_adjust <= 63*1024 and final_adjust <
1024 there are no probes inserted as expected, ie. the vast majority of
functions are unaffected. So that works perfectly.
For larger
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82353
--- Comment #9 from Jakub Jelinek ---
Author: jakub
Date: Fri Oct 13 20:19:17 2017
New Revision: 253744
URL: https://gcc.gnu.org/viewcvs?rev=253744=gcc=rev
Log:
PR sanitizer/82353
* g++.dg/ubsan/pr82353-2.C: New test.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82274
--- Comment #8 from Jakub Jelinek ---
Author: jakub
Date: Fri Oct 13 20:14:34 2017
New Revision: 253743
URL: https://gcc.gnu.org/viewcvs?rev=253743=gcc=rev
Log:
PR target/82274
* internal-fn.c (expand_mul_overflow): If both
On 10/13/2017 06:35 AM, Jonathan Wakely wrote:
This adds an item to the list of options for the -fdump-tree option,
because we show an example using 'vect' but don't document it.
OK for trunk?
No, I think this patch is addressing an imaginary bug. I see no "vect"
option listed in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82544
--- Comment #7 from Igor Kozhukhov ---
i can provide build zone on on real SPARC64 T5220 with DilOS if needed.
just ping me directly to igor at dilos dot org.
i have with DilOS:
gcc-4.4.7 (32bit default) + SunAS + illumos ld - for dilos-illumos
On Wed, 2017-10-11 at 16:17 +0200, Marc Glisse wrote:
> On Wed, 11 Oct 2017, David Malcolm wrote:
>
> > On Wed, 2017-10-11 at 11:18 +0200, Paulo Matos wrote:
> > >
> > > On 11/10/17 11:15, Christophe Lyon wrote:
> > > >
> > > > You can have a look at
> > > >
On 10/13/2017 01:30 PM, Jakub Jelinek wrote:
> Hi!
>
> I've noticed that for {L,R}ROTATE_EXPR created during GENERIC folding
> we end up with e.g. long int etc. second arguments, while for shifts
> we truncate those to unsigned int.
>
> Fixed thusly, bootstrapped/regtested on x86_64-linux and
Hi!
First of all, there was a typo, we are optimizing
(x != 0) ? x + y : y
into x + y rather than y.
And, as the comment mentions, the condition that there is just a single
stmt is too restrictive and in the various patterns posted in the various
rotate related PRs there are cases where in
On 10/13/2017 12:06 AM, Sebastian Huber wrote:
The end-of-life of Solaris 2.6 was 2006. Is it worth to mention this here?
The reference to Solaris 2.6 is no longer useful. Just mention ELF here.
This "AIX may have these optimizations in the future." is there since at
least 1996. What is the
Hi!
The forwprop rotate pattern recognizer is able to detect various
patterns, but for the case where we want to support all rotate
counts without UB, it requires
Y &= B - 1;
R = (X << Y) | (X >> ((-Y) & (B - 1)));
where
R = (X << (Y & (B - 1))) | (X >> ((-Y) & (B - 1)));
is another reasonable
> On Fri, Oct 13, 2017 at 09:06:55PM +0200, Jan Hubicka wrote:
> > For EH we should set it to profile_probability::zero () because we know it
> > is unlikely
> > path. I will take a look.
>
> With the
>
> --- gcc/cfghooks.c.jj 2017-10-13 18:27:12.0 +0200
> +++ gcc/cfghooks.c
Hi!
I've noticed that for {L,R}ROTATE_EXPR created during GENERIC folding
we end up with e.g. long int etc. second arguments, while for shifts
we truncate those to unsigned int.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, ok for
trunk?
2017-10-13 Jakub Jelinek
On Fri, Oct 13, 2017 at 09:06:55PM +0200, Jan Hubicka wrote:
> For EH we should set it to profile_probability::zero () because we know it is
> unlikely
> path. I will take a look.
With the
--- gcc/cfghooks.c.jj 2017-10-13 18:27:12.0 +0200
+++ gcc/cfghooks.c 2017-10-13
Jakub spotted this wart in my last change.We have already tested
that we do not have 0 or 1 ops. So != 2 is more clearly written as > 2.
Bootstrapped and regression tested on x86_64. Committed to the trunk.
Jeff
commit 04acc76e9d46299f5251bf9f495d1b7688d7907f
Author: law
> On Fri, Oct 13, 2017 at 03:38:33PM +0200, Jan Hubicka wrote:
> > Hi,
> > this patch enables check that no edge probabilities are missing.
> >
> > Honza
> >
> > * cfghooks.c (verify_flow_info): Check that edge probabilities are
> > set.
>
> This broke bootstrap on x86_64-linux with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82357
Jason Merrill changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
This patch also caused a huge number of testsuite failures on PowerPC,
although it didn't break bootstrap.
Thanks, David
On Thu, Oct 12, 2017 at 4:46 AM, Oren Ben-Kiki wrote:
> Motivation/Use case:
>
> * Since gcc/g++ intentionally does not have `-Weverything`, there is a
> number of explicit `-W...` flags one might wish to specify explicitly. Fair
> enough.
>
> * Additional `-W...` flags are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82357
--- Comment #5 from Jason Merrill ---
Author: jason
Date: Fri Oct 13 19:03:41 2017
New Revision: 253739
URL: https://gcc.gnu.org/viewcvs?rev=253739=gcc=rev
Log:
PR c++/82357 - bit-field in template
* tree.c
On Fri, Oct 13, 2017 at 1:21 PM, Markus Trippelsdorf
wrote:
> On 2017.10.13 at 12:02 -0400, Jason Merrill wrote:
>> On Fri, Oct 13, 2017 at 5:40 AM, Markus Trippelsdorf
>> wrote:
>> > r253266 introduced a bogus "cannot bind bitfield" error that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81048
--- Comment #4 from Paul Thomas ---
Author: pault
Date: Fri Oct 13 18:59:34 2017
New Revision: 253738
URL: https://gcc.gnu.org/viewcvs?rev=253738=gcc=rev
Log:
2017-10-13 Paul Thomas
PR fortran/81048
*
On 09/20/2017 06:21 AM, Richard Sandiford wrote:
> This is needed by the later SVE LAST reductions, where an 8-bit
> or 16-bit result is zero- rather than sign-extended to 32 bits.
> I think it could occur in other situations too.
>
> Tested on aarch64-linux-gnu, x86_64-linux-gnu and
Good you caught the missing LF. Thanks!
Paul
On 13 October 2017 at 19:29, Steve Kargl
wrote:
> On Fri, Oct 13, 2017 at 07:06:57PM +0100, Paul Richard Thomas wrote:
>>
>> This patch undoes a side effect of r225447 that had the effect of
>> eliminating the
Jeff Law wrote:
>> Btw reminds me a little bit of
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28417
> I wouldn't expect 28417
> to move forward without something other than Tege and Denys pushing on it.
Hmm that doesn't look optimal. You can typically do a multiply with the magic
constant
On 10/13/2017 12:45 PM, Sebastian Huber wrote:
>
>
> - Am 13. Okt 2017 um 20:39 schrieb David Edelsohn dje@gmail.com:
>
>> On Fri, Oct 13, 2017 at 2:34 PM, Sebastian Huber
>> wrote:
>>
> Do these options affect the code generation?
They can
On 09/18/2017 05:26 AM, Richard Sandiford wrote:
> Originally subregs operated at the word level and subreg offsets
> were measured in words. The offset units were later changed from
> words to bytes (SUBREG_WORD became SUBREG_BYTE), but the fundamental
> assumption that subregs should operate at
>> It places each function and each datum into a separate section, which
>> can be placed or removed independently. It is not combining data or
>> altering the order of structures. It allows the linker to position
>> functions and data items as individual components instead of a single
>> object
- Am 13. Okt 2017 um 20:39 schrieb David Edelsohn dje@gmail.com:
> On Fri, Oct 13, 2017 at 2:34 PM, Sebastian Huber
> wrote:
>
Do these options affect the code generation?
>>> They can affect code generation. By placing each object into its
On Fri, Oct 13, 2017 at 2:34 PM, Sebastian Huber
wrote:
>>> Do these options affect the code generation?
>> They can affect code generation. By placing each object into its own
>> section it's no longer viable to use one object to refer to another
>> because
- Am 13. Okt 2017 um 16:11 schrieb Jeff Law l...@redhat.com:
> On 10/13/2017 01:06 AM, Sebastian Huber wrote:
>> Hello,
>>
>> I would like to update the documentation of these compiler flags and
>> have some questions. The -ffunction-sections and -fdata-sections
>> documentation is
On 10/12/2017 10:49 AM, Jakub Jelinek wrote:
> Hi!
>
> On Wed, Oct 11, 2017 at 06:41:05PM -0400, Vladimir Makarov wrote:
>>> Tested on x86_64-linux -m32/-m64, and verified with cc1plus before your
>>> change, ok for trunk?
>
> BTW, I think it is quite fragile to scan for the reload messages, so
On 10/13/2017 12:27 PM, Uros Bizjak wrote:
> On Fri, Oct 13, 2017 at 7:30 PM, Jeff Law wrote:
>> On 09/05/2017 07:50 AM, Uros Bizjak wrote:
>>> Revised patch, incorporates fixes from Alexander's review comments.
>>>
>>> I removed some implementation details from Alexander's
On 10/13/2017 12:18 PM, Geoff Wozniak wrote:
> My team and I are working on a procedural abstraction (PA) optimization
> for GCC based on the ARM Embedded Toolchain distribution that uses GCC
> 6.2.1. Our initial attempt to get something functional has been
> successful, but it is a very messy
- Am 13. Okt 2017 um 16:02 schrieb David Edelsohn dje@gmail.com:
> On Fri, Oct 13, 2017 at 3:06 AM, Sebastian Huber
> wrote:
>> Hello,
>>
>> I would like to update the documentation of these compiler flags and have
>> some questions. The
[Although I filed this as a middle-end bug, it's really a core infra
bug, not sure who the best reviewer is]
In working on tree streaming in the modules branch, I discovered poor
tree node size and hierarchy bits.
Here's a fix for the first part of that. tree.c (tree_code_size)
returns
On Fri, Oct 13, 2017 at 07:06:57PM +0100, Paul Richard Thomas wrote:
>
> This patch undoes a side effect of r225447 that had the effect of
> eliminating the default intialization of derived type array results.
>
> The patch corrects the offending changes to the condition in resolve_symbol.
>
>
On Fri, Oct 13, 2017 at 7:30 PM, Jeff Law wrote:
> On 09/05/2017 07:50 AM, Uros Bizjak wrote:
>> Revised patch, incorporates fixes from Alexander's review comments.
>>
>> I removed some implementation details from Alexander's description of
>> memory_blockage named pattern.
>>
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70515
Paolo Carlini changed:
What|Removed |Added
Priority|P3 |P2
CC|gcc at norgg dot
On 09/18/2017 10:29 AM, Richard Sandiford wrote:
> Ping for some minor cleanups that help with the move to variable-length
> modes. Segher has approved the combine.c parts (thanks).
>
> https://gcc.gnu.org/ml/gcc-patches/2017-08/msg01339.html
> Make more use of HWI_COMPUTABLE_MODE_P
OK.
>
>
My team and I are working on a procedural abstraction (PA)
optimization for GCC based on the ARM Embedded Toolchain
distribution that uses GCC 6.2.1. Our initial attempt to get
something functional has been successful, but it is a very messy
solution because we don't see a reasonable way to do
On 09/16/2017 03:39 PM, Bernhard Reutner-Fischer wrote:
> On 15 September 2017 18:50:26 CEST, Jeff Law wrote:
>> On 09/13/2017 03:20 PM, Wilco Dijkstra wrote:
>>> Jeff Law wrote:
On 09/06/2017 03:55 AM, Jackson Woodruff wrote:
> On 08/30/2017 01:46 PM, Richard Biener
Dear All,
This patch undoes a side effect of r225447 that had the effect of
eliminating the default intialization of derived type array results.
The patch corrects the offending changes to the condition in resolve_symbol.
Bootstraps and regtests of FC23/x86_64 - OK for trunk, 7- and 6-branches?
On 09/06/2017 09:56 AM, Michael Collison wrote:
> Patch updated with all relevant comments and suggestions.
>
> Bootstrapped and tested on arm-none-linux-gnueabihf, and
> aarch64-none-linux-gnu and x86_64.
>
> Ok for trunk?
>
> 2017-08-05 Kyrylo Tkachov
>
The attached patch is an incremental step toward GCC LTO on AIX. The
recent Libiberty Simple Object improvements for XCOFF provide more
capabilities for operations on XCOFF object files, which are a
prerequisite for GCC LTO functionality.
This patch adds the basic LTO scanning pass to the COFF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82511
--- Comment #4 from Steve Kargl ---
On Fri, Oct 13, 2017 at 01:39:26AM +, foreese at gcc dot gnu.org wrote:
>
> Fritz Reese changed:
>
> Under other DEC compilers, it seems STRUCTUREs are to be treated consistently
> with derived types in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69078
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69078
--- Comment #3 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Fri Oct 13 17:38:50 2017
New Revision: 253736
URL: https://gcc.gnu.org/viewcvs?rev=253736=gcc=rev
Log:
2017-10-13 Paolo Carlini
PR
On 09/05/2017 07:50 AM, Uros Bizjak wrote:
> Revised patch, incorporates fixes from Alexander's review comments.
>
> I removed some implementation details from Alexander's description of
> memory_blockage named pattern.
>
>
> 2017-09-05 Uros Bizjak
>
> *
On 10/12/2017 03:40 AM, Richard Earnshaw wrote:
> On 12/10/17 06:21, vladimir.mezent...@oracle.com wrote:
>> From: Vladimir Mezentsev
>>
>> FMA (floating-point multiply-add) instructions are supported on aarch64.
>> These instructions can produce different result if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82274
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Fri Oct 13 17:26:28 2017
New Revision: 253735
URL: https://gcc.gnu.org/viewcvs?rev=253735=gcc=rev
Log:
PR target/82274
* internal-fn.c (expand_mul_overflow): If both
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Alex Potapenko changed:
What|Removed |Added
CC||opotapenko at gmail dot com
---
On 2017.10.13 at 12:02 -0400, Jason Merrill wrote:
> On Fri, Oct 13, 2017 at 5:40 AM, Markus Trippelsdorf
> wrote:
> > r253266 introduced a bogus "cannot bind bitfield" error that breaks
> > building Chromium and Node.js.
> > Fix by removing the ugly goto.
> >
> > Tested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82274
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Fri Oct 13 17:19:12 2017
New Revision: 253734
URL: https://gcc.gnu.org/viewcvs?rev=253734=gcc=rev
Log:
PR target/82274
* internal-fn.c (expand_mul_overflow): If both
Hi
Here is the last patch I will propose for istreambuf_iterator.
This is mostly to remove the mutable keyword on _M_sbuf.
To do so I had to reset _M_sbuf in valid places that is to say
constructors and increment operators. Despite that we might still have
eof iterators with
On 09/03/2017 09:47 AM, Maya Rashish wrote:
> Hi, in my first attempt to fix a build issue I found that the order of
> tm files matters, would prefer to move linux-looking parts of elf.h to
> linux.h.
>
> other targets that include alpha/elf.h besides linux:
> openbsd: provides their own
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82547
Bug ID: 82547
Summary: wide_int is not setting overflow properly for large
unsigned add/subtract calculations.
Product: gcc
Version: unknown
Status: UNCONFIRMED
On Fri, Oct 13, 2017 at 03:38:33PM +0200, Jan Hubicka wrote:
> Hi,
> this patch enables check that no edge probabilities are missing.
>
> Honza
>
> * cfghooks.c (verify_flow_info): Check that edge probabilities are
> set.
This broke bootstrap on x86_64-linux with Ada
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82509
--- Comment #5 from Eric Botcazou ---
> This uses your patch to gcc, plus the following patch to gdb:
>
> https://sourceware.org/ml/gdb-patches/2017-10/msg00266.html
Great, thanks for the testing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82544
Ian Lance Taylor changed:
What|Removed |Added
CC||ian at airs dot com
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68093
--- Comment #1 from Eric Niebler ---
Still happens on trunk, 2 years later:
template
concept bool True = true;
template
struct S {
friend bool operator==(S, int) requires True { return true; }
friend bool operator==(S, int) requires
On Fri, Sep 22, 2017 at 6:03 AM, Jakub Jelinek wrote:
>
> 2017-09-22 Jakub Jelinek
>
> PR target/82274
> * internal-fn.c (expand_mul_overflow): If both operands have
> the same highpart of -1 or 0 and the topmost bit of lowpart
>
On 13 October 2017 at 17:02, David Edelsohn wrote:
> On Fri, Oct 13, 2017 at 3:06 AM, Sebastian Huber
> wrote:
>> Hello,
>>
>> I would like to update the documentation of these compiler flags and have
>> some questions. The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82546
Bug ID: 82546
Summary: tree_size handling for TYPE nodes is confused
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367
Bug 54367 depends on bug 80873, which changed state.
Bug 80873 Summary: ICE in tsubst_copy when trying to use an overloaded function
without a definition in a lambda
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80873
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80873
Paolo Carlini changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80873
--- Comment #3 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Fri Oct 13 16:50:13 2017
New Revision: 253733
URL: https://gcc.gnu.org/viewcvs?rev=253733=gcc=rev
Log:
2017-10-13 Paolo Carlini
PR
"Tsimbalist, Igor V" writes:
>
> This file is included to simplify building a library that might have
> assembler files.
> This is an auxiliary file to automate creation of a special section in
> an output object
> file. Without it every assembler file has to be
> On Oct 13, 2017, at 18:07 , Jeff Law wrote:
>
>>* gcc/config.gcc (powerpc*-*-*spe*): Pick 8548 as the
>> default with_cpu for an e500v2 target cpu name, in addition
>> to --enable-e500-double.
> GIven this hits the powerpcspe port, I'd like Andrew Jenner to
On 09/06/2017 03:26 AM, Jakub Jelinek wrote:
> On Tue, Sep 05, 2017 at 11:21:48PM -0600, Jeff Law wrote:
>> --- a/gcc/tree-ssa-reassoc.c
>> +++ b/gcc/tree-ssa-reassoc.c
>> @@ -5763,14 +5763,15 @@ reassociate_bb (basic_block bb)
>> "Width = %d was chosen for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82542
--- Comment #6 from joseph at codesourcery dot com ---
glibc does not use this option. ABI checking in glibc works on binaries
via objdump -T. linknamespace tests do use -aux-info to list functions
exported by a header, and would find it
Hi,
I'd like to request comments to the patch below which aims to fix PR
80689, which is an instance of a store-to-load forwarding stall on
x86_64 CPUs in the Image Magick benchmark, which is responsible for a
slow down of up to 9% compared to gcc 6, depending on options and HW
used. (Actually,
Hi,
Sorry for the delay - I finally had a chance to look at this again.
I'll start with alloca:
@@ -15245,6 +15455,28 @@ aarch64_sched_can_speculate_insn (rtx_insn *insn)
}
}
+/* It has been decided that to allow up to 1kb of outgoing argument
+ space to be allocated w/o probing. If
Jeff Law writes:
> On 08/24/2017 12:25 PM, Richard Sandiford wrote:
>> Segher Boessenkool writes:
>>> On Wed, Aug 23, 2017 at 11:49:03AM +0100, Richard Sandiford wrote:
This patch uses df_read_modify_subreg_p to check whether writing
to a
On 08/31/2017 12:54 PM, Olivier Hainque wrote:
> Hello,
>
> gcc can be configured with an "e500v2" cpu target
> name, conveying SPE with double precision floats.
>
> config.gcc already has a provision for a good default
> cpu selection for SPE with double precision floats
> when the latter is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82542
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
On Fri, Oct 13, 2017 at 5:40 AM, Markus Trippelsdorf
wrote:
> r253266 introduced a bogus "cannot bind bitfield" error that breaks
> building Chromium and Node.js.
> Fix by removing the ugly goto.
>
> Tested on ppc64le.
> Ok for trunk?
No, this just undoes my change, so we
On 08/28/2017 02:26 AM, Richard Sandiford wrote:
> This patch adds helper functions that say which of the two modes
> involved in a subreg is the larger, preferring the outer mode in
> the event of a tie. It also converts IRA and reload to track modes
> instead of byte sizes, since this is
On 08/24/2017 12:25 PM, Richard Sandiford wrote:
> Segher Boessenkool writes:
>> On Wed, Aug 23, 2017 at 11:49:03AM +0100, Richard Sandiford wrote:
>>> This patch uses df_read_modify_subreg_p to check whether writing
>>> to a subreg would preserve some of the existing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82542
--- Comment #4 from Andrew Pinski ---
> Debian and Glibc use it for ABI checking; I and others use it to help generate
> C bindings for my toy language without having to write a C parser for no
> reason
I always have maintained that this is an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82542
--- Comment #3 from Andrew Pinski ---
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg01668.html
On 08/17/2017 02:31 PM, Sergei Trofimovich wrote:
> Looks like the following patch falled through the cracks
> https://gcc.gnu.org/ml/gcc-patches/2012-12/msg01397.html
> https://bugs.gentoo.org/show_bug.cgi?id=434180#c16
Yea. Looks like it did fall through the cracks.
I've updated Mike's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82478
--- Comment #1 from Jonathan Wakely ---
Reduced:
struct true_type { static const bool value = true; };
struct false_type { static const bool value = false; };
template
using void_t = void;
template
struct
On 10/13/2017 08:04 AM, Richard Sandiford wrote:
> The name inchash::add_wide_int is a bit misleading, since it sounds
> like it's hashing a wide_int. This patch renames it to add_hwi instead.
>
> Tested on aarch64-linux-gnu, x86_64-linux-gnu and powerpc64le-linux-gnu.
> OK to install?
>
>
> -Original Message-
> From: Ian Lance Taylor [mailto:i...@airs.com]
> Sent: Friday, October 13, 2017 1:59 AM
> To: Tsimbalist, Igor V
> Cc: gcc-patches@gcc.gnu.org; Jeff Law
> Subject: Re: [PATCH 09/22] Enable building libbacktrace with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82544
Andrew Pinski changed:
What|Removed |Added
Component|go |target
Assignee|ian at airs
1 - 100 of 219 matches
Mail list logo