Various implementations of C99/C11 have the property that
their macro expansions contain many copies of the macro arguments, so
resulting in exponential blowup of the size of macro expansions where
a call to such a macro contains other such calls in the macro
arguments.
This patch adds a (C-only)
Disabling software prefetching and switching the autoprefetcher to weak improves
CPU2017 rate and speed benchmarks for both int and fp sets on Falkor.
SPECrate 2017 fp is up 0.38%
SPECspeed 2017 fp is up 0.54%
SPECrate 2017 int is up 3.02%
SPECspeed 2017 int is up 3.16%
There are only a couple in
On Tue, Nov 14, 2017 at 6:00 PM, Luis Machado wrote:
> Disabling software prefetching and switching the autoprefetcher to weak
> improves
> CPU2017 rate and speed benchmarks for both int and fp sets on Falkor.
>
> SPECrate 2017 fp is up 0.38%
> SPECspeed 2017 fp is up 0.54%
> SPECrate 2017 int is
On 11/14/2017 02:30 PM, Jakub Jelinek wrote:
> On Tue, Nov 14, 2017 at 02:24:28PM -0700, Martin Sebor wrote:
>> On 11/14/2017 02:04 PM, Jakub Jelinek wrote:
>>> Hi!
>>>
>>> strlen_to_stridx.get (rhs1) returns an address into the hash_map, and
>>> strlen_to_stridx.put (lhs, *ps); (in order to be eff
> I think the best thing is to leave this tuning structure in place and
> just change default_opt_level to -1 to disable it at -O3.
>
> Thanks,
> Andrew
>
Indeed that seems to be more appropriate if re-enabling prefetches in the
future is a possibility.
How about the following?
Thanks,
Luis
With my local patches to remove jump threading from VRP I was seeing a
fairly obvious jump threading path left in the CFG after DOM. This
missed jump thread ultimately caused a false positive uninitialized warning.
Interestingly enough when I looked at the dumps it appeared DOM was
finding the ap
On Nov 13, 2017, Richard Biener wrote:
> What does final.c need langhooks for?
Thanks for catching this.
At some point I had a check on whether there could be being stmt markers
emitted by the language, but that's long gone, in part because of LTO;
that's now computed dynamically, on a per-func
On Nov 13, 2017, Sergio Durigan Junior wrote:
> On Tuesday, September 26 2017, I wrote:
>> Ping^2.
> Ping^3.
> I'm sending the updated ChangeLog/patch. I'm also removing gdb-patches
> from the Cc list.
> libcc1/ChangeLog:
> 2017-09-01 Sergio Durigan Junior
> Pedro Alves
>
On Fri, Nov 10, 2017 at 04:45:17PM -0500, David Malcolm wrote:
> This patch provides a mechanism in tree.c for adding a wrapper node
> for expressing a location_t, for those nodes for which
> !CAN_HAVE_LOCATION_P, along with a new method of cp_expr.
>
> It's called in later patches in the kit via
On November 14, 2017 10:25:28 PM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>I'll be working on further store-merging improvements next two days
>and hope to use some of the bswap pass APIs to handle stuff like:
>void foo (char *__restrict p, char *__restrict q)
>{
> p[0] = q[3];
> p[1] = q[2];
>
Testing within Red Hat of the aarch64 stack clash bits turned up an
additional problem, one I probably should have expected.
aarch64 is a bit odd in that we may need to emit a probe in the residual
alloca space to enforce certain probing rules related to the outgoing
argument space.
When the siz
So the next group of changes is focused on breaking down evrp into an
analysis engine and the actual optimization pass. The analysis engine
can be embedded into other dom walker passes quite easily. I've done it
for the sprintf warnings as well as the main DOM optimizer locally.
Separating anal
debug info: partial noentry functions: infra
This is the first patch of a set that addresses two different but
somewhat related issues.
On the one hand, after partial inlining, the non-inlined function
fragment is output in a way that debug info consumers can't distinguish
from the entire functio
On 11/14/2017 02:59 PM, Joseph Myers wrote:
> On Tue, 14 Nov 2017, Martin Liška wrote:
>
>> Hello.
>>
>> Quite obvious fix for SH target. Joseph can you please continue with testing?
>> I don't have a machine to test the patch.
>
> I don't have SH hardware, but can confirm that, in conjunction wi
Hello.
This is partial revert of my commit r254257 because having
-fkeep-inline-functions
causes many unresolved symbols. And it would force us to add e.g. many objects
for libcommon.a.
I'm going to install the patch.
gcc/ChangeLog:
2017-11-15 Martin Liska
* configure.ac: Remove -f
This is a respin of a AArch64 patch that adds support for builtin arithmetic
overflow operations. This update separates the patch into multiple pieces and
addresses comments made by Richard Earnshaw here:
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00249.html
Original patch and motivation for
This is a respin of a AArch64 patch that adds support for builtin arithmetic
overflow operations. This update separates the patch into multiple pieces and
addresses comments made by Richard Earnshaw here:
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00249.html
Original patch and motivation for
This is a re-spin of a AArch64 patch that adds support for builtin arithmetic
overflow operations. This update separates the patch into multiple pieces and
addresses comments made by Richard Earnshaw here:
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00249.html
Original patch and motivation fo
This is a respin of a AArch64 patch that adds support for builtin arithmetic
overflow operations. This update separates the patch into multiple pieces and
addresses comments made by Richard Earnshaw here:
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00249.html
Original patch and motivation for
On 11/08/2017 05:31 PM, Jeff Law wrote:
> I don't see an updated patch in this thread? THe last message I see is
> this one where you indicate you're going to tweak the patch and re-test.
>
> Jeff
Yes, I tweaked and tested following patch.
Martin
>From a369ac78b887e219a375e17d6817c1f744e71779 M
PING^1
On 11/07/2017 11:08 AM, Martin Liška wrote:
> On 11/06/2017 06:33 PM, Jakub Jelinek wrote:
>> On Mon, Nov 06, 2017 at 06:23:11PM +0100, Eric Botcazou wrote:
Thank you for review, done that.
>>>
>>> This has enabled -Wreturn-type for Ada, what we don't want since the
>>> warning
>>> i
On 11/14/2017 02:38 PM, David Malcolm wrote:
On Tue, 2017-11-14 at 14:08 -0500, Aldy Hernandez wrote:
https://gcc.gnu.org/codingconventions.html#Class_Form
says that:
"When defining a class, first [...]
declare all public member functions,
[...]
then declare all non-public member functio
On 11/14/2017 10:46 PM, Jeff Law wrote:
With my local patches to remove jump threading from VRP I was seeing a
fairly obvious jump threading path left in the CFG after DOM. This
missed jump thread ultimately caused a false positive uninitialized warning.
This wouldn't be uninit-pred-[68]* or
101 - 123 of 123 matches
Mail list logo
