Re: [PATCH, version 5a], Add support for _Float and _FloatX sqrt, fma, fmin, fmax built-in functions

On Mon, 30 Oct 2017, Michael Meissner wrote: > This patch fixes exporting the non __builtin_ names to be done by default only > for the C language. I added a target hook in case a port needs to enable > built-ins for C++ (either wholesale, or for particular built-in functions). Testing lang_GNU_

Re: [PATCH, version 5a], Add support for _Float and _FloatX sqrt, fma, fmin, fmax built-in functions

On Mon, Oct 30, 2017 at 11:30:12PM +, Joseph Myers wrote: > On Mon, 30 Oct 2017, Michael Meissner wrote: > > > This patch fixes exporting the non __builtin_ names to be done by default > > only > > for the C language. I added a target hook in case a port needs to enable > > built-ins for C++

Re: [patch] configure option to override TARGET_LIBC_PROVIDES_SSP

On Mon, 9 Oct 2017, Sandra Loosemore wrote: > On 10/09/2017 09:13 AM, Joseph Myers wrote: > > The install.texi documentation for --disable-libssp only says "Specify > > that the run-time libraries for stack smashing protection should not be > > built.". I think it needs updating to mention these

Re: [patch] Add -static-libquadmath option

On Thu, 19 Oct 2017, Janus Weil wrote: > Ping! > > Is there any hope to get this 3-year-old patch to trunk after all? (It > seems there was at least a review of the Fortran parts, which has not > seen a reply ...) I'm not clear here what the semantics of -static-libquadmath are meant to be with

Re: [PR other/79543] Fix GNU ld --version scanning to conform to the GNU Coding Standards

On Thu, 19 Oct 2017, Thomas Schwinge wrote: > | (It's possible some very old binutils versions may > | not have properly formatted output; my view is that each GCC version should > | have a minimum corresponding binutils version, no more than say five years > old, > | for targets using GNU binuti

Re: [patch] configure option to override TARGET_LIBC_PROVIDES_SSP

On 10/09/2017 02:08 PM, Sandra Loosemore wrote: > On 10/09/2017 09:13 AM, Joseph Myers wrote: >> The install.texi documentation for --disable-libssp only says "Specify >> that the run-time libraries for stack smashing protection should not be >> built.".  I think it needs updating to mention these 

Re: [PATCH 21/22] Enable building libitm with Intel CET

On 10/12/2017 03:21 PM, Tsimbalist, Igor V wrote: > Enable building libitm with Intel CET options. > > libitm/ > * Makefile.in: Regenerate. > * acinclude.m4: Add enable.m4 and cet.m4. > * config/x86/sjlj.S > (_ITM_beginTransaction): Save Shadow Stack pointer. > (GTM_l

Re: bootstrap-debug-lean + flags in producer vs compare

On 10/05/2017 07:15 PM, Alexandre Oliva wrote: > Unlike bootstrap-debug, bootstrap-debug-lean used to pass compare using > the traditional compare command, because it compiled both stage2 and > stage3 with options that used to generate identical output > (-fcompare-debug= in stage2 vs -fcompare-deb

Re: [PATCH, Makefile] improve libsubdir variable transmission to sub-makes on Windows

On 09/01/2017 02:42 AM, Olivier Hainque wrote: > Hello, > > To convey the value of libsubdir to sub-makes, gcc/Makefile.in has > > # Flags to pass to recursive makes. > # CC is set by configure. > # ??? The choices here will need some experimenting with. > > export AR_FOR_TARGET > ...

[PATCH 0/2] [i386] PR82002 Correct ICE with large stack frame

I originally intended to submit the first part of this patch set a few weeks ago as it was simpler, but here is the full fix.  The first part is a really simple follow-up fix to an off-by-one error H.J. originally fixed with r252099, but in the process of testing I discovered a more complex problem

[PATCH 1/2] [i386] PR82002 Part 1: Correct ICE caused by wrong calculation.

This is a residual problem caused by the off-by-one error in sp_valid_at and fp_valid_at originally corrected in r252099. However, adding tests that include an ms_abi to sysv_abi call reveals an additional, more complex problem with an invalid INSN due to overflowing the s32 offset. Therefore I'm

[PATCH 2/2] [i386] PR82002 Part 2: Correct non-immediate offset/invalid INSN

When we are realigning the stack pointer, making an ms_abi to sysv_abi call and alllocating 2GiB or more on the stack we end up with an invalid INSN due to a non-immediate offset. This occurs both with and without -mcall-ms2sysv-xlogues. Additionally, I've discovered that the stack allocation wit

Re: [PATCH 2/2] [i386] PR82002 Part 2: Correct non-immediate offset/invalid INSN

On 10/30/2017 09:09 PM, Daniel Santos wrote: > 3. Modify choose_baseaddr to take an optional scratch_regno argument >and never return rtx that cannot be used as an immediate. I should amend this, it actually does a gcc_assert, so that won't happen if --enable-checking=no, but it would still fa

Re: [PATCH, AArch64] Disable reg offset in quad-word store for Falkor.

Ping ? I see that Jim has clarified the comments from Andrew. Thanks, Kugan On 13 October 2017 at 08:48, Jim Wilson wrote: > On Fri, 2017-09-22 at 14:11 -0700, Andrew Pinski wrote: >> On Fri, Sep 22, 2017 at 11:39 AM, Jim Wilson >> wrote: >> > >> > On Fri, Sep 22, 2017 at 10:58 AM, Andrew Pins

Re: [PATCH] enhance -Warray-bounds to detect out-of-bounds offsets (PR 82455)

On 10/30/2017 05:29 PM, Martin Sebor wrote: > On 10/30/2017 03:48 PM, Jeff Law wrote: >> On 10/30/2017 09:19 AM, Martin Sebor wrote: >>> On 10/30/2017 05:45 AM, Richard Biener wrote: On Sun, 29 Oct 2017, Martin Sebor wrote: > In my work on -Wrestrict, to issue meaningful warnings, I f

Re: [RFA][PATCH] Provide a class interface into substitute_and_fold.

On 10/30/2017 03:32 AM, Pedro Alves wrote: > On 10/25/2017 06:20 PM, Jeff Law wrote: > >> My conclusion on the virtual dtor issue is that it's not strictly needed >> right now. >> >> IIUC the issue is you could do something like >> >> base *foo = new derived (); >> [ ... ] >> delete foo; >> >> If

Re: [PATCH 08/22] Add Intel CET support for EH in libgcc.

On 10/12/2017 01:56 PM, Tsimbalist, Igor V wrote: > Control-flow Enforcement Technology (CET), published by Intel, Introduces > the Shadow Stack feature, which ensures a return from a function is done > to exactly the same location from where the function was called. When EH > is present the contro

Re: [PATCH 6/9] [LVU] Allow final_start_function to skip initial insns

On 10/19/2017 05:01 AM, Richard Biener wrote: > On Sat, Sep 30, 2017 at 11:08 AM, Alexandre Oliva wrote: >> 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()

Re: [PATCH 6/9] [LVU] Allow final_start_function to skip initial insns

On 09/30/2017 03:08 AM, Alexandre Oliva wrote: > 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.

Re: [PATCH 8/9] [IEPM] Introduce debug hook for inline entry point markers

On 09/30/2017 03:08 AM, 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. > * debug.c (do_nothing_debu

Re: [PATCH 9/9] [IEPM] Introduce inline entry point markers

On 09/30/2017 03:08 AM, Alexandre Oliva wrote: > 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

Re: [patch][x86] GFNI enabling [2/4]

Hello Julia! On 30 Oct 19:02, Koval, Julia wrote: > Hi, > Fixed that. Your patch is OK for trunk. I've comitted it w/ minor re-indentation in gcc/ChangeLog entry. -- Thanks, K > > > > > > Ok for trunk? > > Few comments: > > 1. Why copyright in config/i386/gfniintrin.h starts from 2014? > > > > 2.

<    1   2