Since size of "void *" is 4 bytes for x32, check if __x86_64__ is defined
by $CC, instead of
if test x$ac_cv_sizeof_void_p = x8; then
to decide wether anitizer_linux_x86_64.lo should be used.
I am testing this on i686 and x86-64. OK for trunk and GCC 7 branch if
there are no regression? Please
Sorry. Here is the patch.
-Original Message-
From: James Greenhalgh [mailto:james.greenha...@arm.com]
Sent: Friday, September 29, 2017 3:57 PM
To: Michael Collison
Cc: GCC Patches ; nd
Subject: Re: [PING][PATCH][Aarch64] Improve int<->FP conversions
On Fri, Sep 29, 2017 at 10:42:14PM +
On Fri, Sep 29, 2017 at 11:15 AM, David Malcolm wrote:
> On Sun, 2017-09-17 at 20:00 -0400, Eric Gallager wrote:
>> Attached is a version of
>> https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00481.html that
>> contains
>> a combination of both the fix and the testcase update, as requested
>> in
>>
2017-10-01 Rasmus Villemoes
PR preprocessor/64965
* gcc.c-torture/compile/pr64965.c: New test.
If the current filename contains a newline character, __FILE__ would
expand to a string literal containing an actual embedded newline,
which is of course illegal. Similarly, even in t
On Sun, Sep 3, 2017 at 5:16 PM, Maya Rashish wrote:
> grouping netbsd.h netbsd-stdint.h netbsd-elf.h as "nbsd_tm_file",
> similar to freebsd.
I found a small bug in the patch -- the NetBSD stdint.h have different
definitions for 8- and 16-bit "fast" types than what is in the
netbsd-stditn.h, so t
On September 29, 2017 9:58:41 PM GMT+02:00, Sebastian Pop
wrote:
>On Fri, Sep 29, 2017 at 2:37 PM, Sven Verdoolaege
> wrote:
>> [Sorry for the resend; I used the wrong email address to CC Alex]
>>
>> On Wed, Sep 27, 2017 at 02:18:51PM +0200, Richard Biener wrote:
>>> Ah, so I now see why we do no
The attached patch fixes the PR and most of the remaining, if not all,
problems associated with deferred string length targets in the
associate construct.
Bootstraps and regtests on FC23/x86_64 - OK for trunk?
Paul
2017-09-29 Paul Thomas
PR fortran/77296
* resolve.c (resolve_assoc_va
On 09/30/2017 04:15 AM, Richard Sandiford wrote:
Vladimir Makarov writes:
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81481
The patch was bootstrapped and tested on x86-64.
Committed as rev. 253300.
Index: ira-costs.c
===
As noticed by Thomas on IRC, the FX's patch may not be translator friendly. I
have now tested the following
--- ../_clean/gcc/fortran/parse.c 2017-09-01 19:00:10.0 +0200
+++ gcc/fortran/parse.c 2017-09-28 17:55:14.0 +0200
@@ -5742,16 +5742,28 @@ gfc_global_used (gfc_gsymbol
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 not in strict compliance mode, output
DW_AT_GNU_entry_view if it might be nonzero.
This patch depends on SFN and LVU patchsets, and on the IEPM patch that
introduces the in
This patch introduces an option to enable the generation of location
views along with location lists. The exact format depends on the
DWARF version: it can be a separate attribute (DW_AT_GNU_locviews) or
(DW_LLE_view_pair) entries in DWARF5+ loclists.
Line number tables are also affected. If the
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.
* debug.c (do_nothing_debug_hooks): Likewise.
* sdbout.c (sdb_debug_hooks
This API change will enable final_start_function() to "consume"
initial insns, and choose the first insn to be passed to final().
Many ports call final_start_function() and final() when creating
thunks and whatnot, so they needed adjusting.
for gcc/ChangeLog
* output.h (final_start_func
This patch adjusts numerous parts of the compiler that would
malfunction should they find debug markers at points where they may be
introduced. The changes purport to allow the compiler to pass
bootstrap-debug-lean (-fcompare-debug in stage3) at various
optimization levels, as well as bootstrap-de
This patch completes the infrastructure for the introduction of
statement frontiers in C-family languages.
It brings in all the code remaining code needed to introduce and
transform begin stmt trees, gimple stmts, insns and notes, and
ultimately use them to generate the is_stmt column in DWARF2+ l
This patch introduces a number of new macros and functions that will
be used to distinguish between different kinds of debug stmts, insns
and notes, namely, preexisting debug bind ones and to-be-introduced
nonbind markers.
In a seemingly mechanical way, it adjusts several uses of the macros
and fu
Introduce a command line option to enable statement frontiers, enabled
by default in optimized builds with DWARF2+ debug information.
This patch depends on an earlier patch that completed the
infrastructure for debug markers, and on another patch that turns -g
into a negatable option prefix.
gcc/
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/ChangeLog
* emit-rtl.c (next_nondebug_insn, prev_nondebug_insn): Reorder.
(next_nonnote_no
On Aug 31, 2017, Alexandre Oliva wrote:
> On Aug 23, 2017, Richard Biener wrote:
>> Just separating the boilerplate changes out from the "meat" of the change
>> into a separate patch for easier reviewing would be nice.
> I've broken up the patch into a patchset with 10 patches. I've already
>
Greetings to all,
This patch fixes a bug where the pointer assignment to the derived
component of a class entity was resulting in the base entity's vptr
being set to the vtable of the target. This resulted in the wrong
typebound procedure being called.
The patch corrects the logic in resolve code
Vladimir Makarov writes:
> The following patch fixes
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81481
>
> The patch was bootstrapped and tested on x86-64.
>
> Committed as rev. 253300.
>
>
> Index: ira-costs.c
> ===
> --- ira-co
On Fri, Sep 29, 2017 at 11:05 PM, Jakub Jelinek wrote:
> Hi!
>
> The following patch adds patterns and splitters for {,u}divmodsi4 followed
> by zero-extension, similarly to other 32-bit operand instructions divl and
> idivl zero extends both results to 64-bit, so there is no need to extend it
> a
On Fri, Sep 29, 2017 at 10:59 PM, Jakub Jelinek wrote:
> Hi!
>
> While working on the following patch, I've discovered that the REG_EQUAL
> notes for DImode signed/unsigned division/modulo are wrong, there is
> e.g. (div:SI (reg:DI ...) (reg:DI ...)).
>
> Fixed thusly, bootstrapped/regtested on x8
23 matches
Mail list logo
