Hi Martin,
he header file will be install by glibc (glibc-devel package).
Why actually glibc-devel? Needing glibc-devel for fast compilation
of Fortran seems to be counter-intuitive. Maybe glibc would be better.
Regards
Thomas
On 11/22/18 12:56 PM, Jakub Jelinek wrote:
> Hi!
>
> This test apparently FAILs on s390x-linux, which is an effective target of
> both logical_op_short_circuit and branch_cost.
> The test has
> /* { dg-additional-options "-mbranch-cost=2" { target branch_cost } } */
> and that option effectively m
On Mon, 26 Nov 2018 at 12:12, Jonathan Wakely wrote:
>
> On 26/11/18 09:30 +0100, Christophe Lyon wrote:
> >On Thu, 22 Nov 2018 at 10:20, Jonathan Wakely wrote:
> >>
> >> On 20/11/18 17:58 -0500, Ed Smith-Rowland wrote:
> >> >On 11/19/18 6:13 AM, Jonathan Wakely wrote:
> >> >>On 16/11/18 19:39 -0
On 11/26/18 8:32 PM, Martin Sebor wrote:
On 11/26/18 11:13 AM, Sandra Loosemore wrote:
On 11/26/18 10:17 AM, Martin Sebor wrote:
On 11/25/18 6:40 PM, Sandra Loosemore wrote:
I've checked in the attached patch for PR79738.
I think we have lost something important with the clarification
of att
On 11/26/18 11:13 AM, Sandra Loosemore wrote:
On 11/26/18 10:17 AM, Martin Sebor wrote:
On 11/25/18 6:40 PM, Sandra Loosemore wrote:
I've checked in the attached patch for PR79738.
I think we have lost something important with the clarification
of attribute const:
The @code{const} attribu
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-11/msg01674.html
On 11/19/18 6:14 PM, Martin Sebor wrote:
The recent -Wbuiltin-declaration-mismatch enhancement to detect
calls with incompatible arguments to built-ins declared without
a prototype introduced a subtle bug in the detection of floating
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-11/msg01759.html
If there are no objections or suggestions for tweaks I'll commit
this updated comment this week.
On 11/20/18 1:24 PM, Martin Sebor wrote:
On 11/20/2018 11:02 AM, Martin Sebor wrote:
Would the updated comments in the attached patch
Just so there is some record of what I did here -- in order to backport the
gpr strncmp expansion improvement patch to gcc 8 I had to pull in some pieces
of an earlier cleanup patch from June of this year.
I'll get this committed to gcc-8-branch when I'm done with the bootstrap/regtest
on a couple
On Mon, 2018-11-26 at 22:17 +, Mike Gulick wrote:
> On 11/13/18 3:12 PM, David Malcolm wrote:
> > On Tue, 2018-11-13 at 14:54 -0500, Mike Gulick wrote:
> > > 2018-11-13 Mike Gulick
> >
> > [...]
> >
> > > * gcc/diagnostic-core.h (num_digits): Add extern definition.
> >
> > FWIW you move
On Mon, Nov 12, 2018 at 10:13:43PM +1030, Alan Modra wrote:
> There are a few places in libgcc assembly where we don't emit call
> frame information for functions, potentially breaking unwinding from
> asynchronous signal handlers. This patch fixes most. Although I
> patch tramp.S there is no att
On Mon, Nov 12, 2018 at 10:12:13PM +1030, Alan Modra wrote:
> The -mcpu=native support has bit-rotted a little, in particular the
> fallback when the native cpu couldn't be determined. This patch fixes
> the bit-rot and reorganizes ASM_CPU_SPEC so that it should be a little
> easier to keep the -m
This libgo patch changes the mksysinfo shell script to always define
WEXITED and WNOWAIT on GNU/Linux. This fixes PR 88135. Bootstrapped
and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
===
On Mon, Nov 26, 2018 at 05:16:38PM -0600, Segher Boessenkool wrote:
> On Mon, Nov 12, 2018 at 09:56:37PM +1030, Alan Modra wrote:
> > Using the macros in config/linux.h rather than duplicating them helps
> > stop future bitrot, and repairs existing bitrot (4 choices for libc in
> > linux.h, fewer i
On 11/21/18 1:42 PM, Jozef Lawrynowicz wrote:
> On Wed, 21 Nov 2018 20:19:29 +0100
> Rainer Orth wrote:
>
>> new effective-target keywords always need documenting in
>> gcc/doc/sourcebuild.texi.
>>
>> Rainer
>>
> Whoops, thanks for the heads up, fixed in attached.
>
> I'll add documentation
On Mon, Nov 26, 2018 at 04:20:18PM -0600, Segher Boessenkool wrote:
> > --- gcc/config/rs6000/rs6000.c.jj 2018-11-16 21:35:42.497982764 +0100
> > +++ gcc/config/rs6000/rs6000.c 2018-11-26 10:56:28.079516458 +0100
> > @@ -20644,7 +20644,11 @@ print_operand (FILE *file, rtx x, int co
> >
> >
On Mon, Nov 12, 2018 at 10:05:03PM +1030, Alan Modra wrote:
> This patch removes some duplication in rs6000/sysv4.h of macros found
> in gnu-user.h that we want for linux. Including gnu-user.h will mean
> powerpc doesn't miss updates to that file.
>
> Requires https://gcc.gnu.org/ml/gcc-patches/2
Hi Alan,
On Mon, Nov 12, 2018 at 09:56:37PM +1030, Alan Modra wrote:
> Using the macros in config/linux.h rather than duplicating them helps
> stop future bitrot, and repairs existing bitrot (4 choices for libc in
> linux.h, fewer in the rs6000 files not that it matters much). Also
> fixes the fa
On Mon, 26 Nov 2018 12:51:26 -0800
Mike Stump wrote:
> On Nov 14, 2018, at 7:56 AM, Jozef Lawrynowicz
> wrote:
> >
> > Patch 5 deals with ISO C errors emitted by tests when the large memory
> > model is
> > used. size_t and ptrdiff_t are __int20 with -mlarge, and if the test is
> > compiled w
On Nov 13, 2018, at 10:39 AM, Peter Bergner wrote:
>
> On 11/13/18 12:06 PM, Iain Sandoe wrote:
>> As far as I expect, Darwin should be untouched by this - we have a separate
>> assembler (which doesn’t even respond to -many), so unless there’s some
>> higher level translation done (it’s not me
On Mon, Nov 26, 2018 at 03:08:32PM -0600, Aaron Sawdey wrote:
> When I previously added the use of unaligned vsx stores to inline expansion
> of memset, I didn't do a good job of managing boundary conditions. The
> intention
> was to only use unaligned vsx if the block being cleared was more than
On 11/23/18 1:55 PM, Tom de Vries wrote:
> [ was: Re: [PATCH 2/2][libbacktrace] Don't point to released memory in
> backtrace_vector_release ]
>
> On Thu, Nov 22, 2018 at 01:36:49PM +0100, Tom de Vries wrote:
>> Hi,
>>
>> When backtrace_vector_release is called with vec.size == 0, it releases the
On 11/23/18 1:51 PM, Tom de Vries wrote:
> [ was: Re: [PATCH 1/2][libbacktrace] Handle realloc returning NULL if size ==
> 0 ]
>
> On Thu, Nov 22, 2018 at 06:16:20PM +, Joseph Myers wrote:
>> On Thu, 22 Nov 2018, Tom de Vries wrote:
>>
>>> Hi,
>>>
>>> If realloc is called with size 0, realloc
On 26-11-18 22:43, Mike Stump wrote:
> On Nov 20, 2018, at 3:51 AM, Tom de Vries wrote:
>>
>> this patch ensures that gcc --help=params lines end with a period by:
>> - fixing the help message of param HOT_BB_COUNT_FRACTION, and
>> - adding a test-case.
>>
>> Build and tested on x86_64.
>>
>> OK f
2018-11-26 Mike Gulick
PR preprocessor/83173
* gcc/input.c (dump_location_info): Dump reason and
included_from fields from line_map_ordinary struct. Fix
indentation when location > 5 digits.
* libcpp/location-example.txt: Update example
-fdump-in
Hi Jakub,
On Mon, Nov 26, 2018 at 09:43:47PM +0100, Jakub Jelinek wrote:
> The following patch fixes a bunch of ICEs in rs6000 print_operand; we
> shouldn't ICE on them when users write mess in their inline asm.
> 2018-11-26 Jakub Jelinek
>
> PR target/88188
> * config/rs6000/rs60
On Nov 16, 2018, at 8:16 AM, Matthew Malcomson
wrote:
>
> On 16/11/18 16:04, Jeff Law wrote:
>> On 11/15/18 12:06 PM, Martin Sebor wrote:
>>> On 11/15/2018 02:39 AM, Matthew Malcomson wrote:
If not we could add an
{ dg-require-effective-target unwrapped }
directive in the test
On 11/13/18 3:12 PM, David Malcolm wrote:
> On Tue, 2018-11-13 at 14:54 -0500, Mike Gulick wrote:
>> 2018-11-13 Mike Gulick
>
> [...]
>
>> * gcc/diagnostic-core.h (num_digits): Add extern definition.
>
> FWIW you moved the decl to diagnostic.h, but didn't update the above
> ChangeLog ent
OK.
On Mon, Nov 26, 2018 at 12:12 PM Marek Polacek wrote:
>
> The problem here was that we were calling save_expr in a template, which
> we shouldn't, as the comment in cp_save_expr explains. This problem
> only appears on ptrmemfunc_vbit_in_delta targets.
>
> Bootstrapped/regtested on aarch64-li
On Nov 16, 2018, at 8:28 AM, Andrew Stubbs wrote:
>
> [This patch was previously approved by Richard Sandiford (with added
> documentation I've still not done), but objected to by Mike Stump. I
> need to figure out who's right.]
Since the planned port is done and someone isn't actively finishin
On 11/21/18 6:24 AM, Umesh Kalappa wrote:
> Hi Jakub and All,
>
> We don't have the commit access ,can someone please commit for us ?
Looks like Uros took care of it a few days ago.
jeff
On Nov 20, 2018, at 3:51 AM, Tom de Vries wrote:
>
> this patch ensures that gcc --help=params lines end with a period by:
> - fixing the help message of param HOT_BB_COUNT_FRACTION, and
> - adding a test-case.
>
> Build and tested on x86_64.
>
> OK for trunk?
So, normally we'd punt approval t
This patch to the Go frontend adds initial support for exporting
function bodies. It creates a framework for putting function bodies
in export data. At present only empty functions will be put there,
and they will be ignored on import. Later patches will get this to
the point of supporting inlin
On Mon, Nov 26, 2018 at 10:32:40PM +0100, Iain Buclaw wrote:
> Hi,
>
> This adds filters for upstream dmd, druntime, and phobos libraries, so
> that the update-copyright script doesn't complain or try to update the
> copyright years for those files.
>
> OK for trunk?
> --
> Iain
>
> ---
> contri
Hi,
This adds filters for upstream dmd, druntime, and phobos libraries, so
that the update-copyright script doesn't complain or try to update the
copyright years for those files.
OK for trunk?
--
Iain
---
contrib/ChangeLog:
2018-11-13 Iain Buclaw
* update-copyright.py (TestsuiteFilt
On Mon, 26 Nov 2018 12:20:10 -0800
Mike Stump wrote:
> On Nov 21, 2018, at 2:39 PM, Jozef Lawrynowicz
> wrote:
> >
> > On Wed, 14 Nov 2018 15:41:00 +
> > Jozef Lawrynowicz wrote:
> >
> >> Patch 3 sets up require-effective-target directives for tests which
> >> require the compilation o
On Nov 20, 2018, at 12:36 PM, Jakub Jelinek wrote:
>
> The following testcase fails on Solaris, because it doesn't print there
> 'size_t', but 'std::size_t', as the type is defined by system headers and
> it is not under gcc control how exactly is size_t defined.
>
> The following patch fixes th
On Mon, Nov 26, 2018 at 9:52 PM Jakub Jelinek wrote:
>
> Hi!
>
> The following patch makes def_builtin2 behave consistently wrt.
> OPTION_MASK_ISA_64BIT requirement to def_builtin.
> The latter has:
> tree decl = NULL_TREE;
>
> if (!(mask & OPTION_MASK_ISA_64BIT) || TARGET_64BIT)
> {
> ...
On 11/25/18 1:13 PM, Maya Rashish wrote:
> ---
> gcc/config.host | 4 ++
> gcc/config/host-netbsd.c | 85
> gcc/config/x-netbsd | 4 ++
> 3 files changed, 93 insertions(+)
> create mode 100644 gcc/config/host-netbsd.c
> create mode 100644
On 11/26/18 1:55 PM, Martin Sebor wrote:
> In the committed patch I forgot that the CONSTRUCTOR to STRING_CST
> transformation introduced this summer only takes place for arrays
> of char and not also those of wide characters. That resulted in
> sprintf incorrectly getting STRING_CSTs for individu
On Nov 26, 2018, at 12:04 PM, Mike Stump wrote:
>
> I'll Ok the signal one, if you prefer it over a dummy signal routine.
> Though, would be nice for you to add signal if possible/reasonable.
Oh, and my long term thinking on signal is that logically, it's fine to have:
#if __has_include("sign
On 11/26/18 2:00 PM, Jakub Jelinek wrote:
> Hi!
>
> The following testcase fails to assemble, because with -ffunction-sections
> and hot/cold partitioning, secname_for_decl returns the same section
> for both the hot and cold partition, even when we actually use two different
> sections - .text._Z
When I previously added the use of unaligned vsx stores to inline expansion
of memset, I didn't do a good job of managing boundary conditions. The intention
was to only use unaligned vsx if the block being cleared was more than 32 bytes.
What it actually did was to prevent the use of unaligned vsx
On Fri, Nov 23, 2018 at 03:09:49PM +0100, Jakub Jelinek wrote:
> On Fri, Nov 23, 2018 at 02:57:44PM +0100, Martin Liška wrote:
> > > Unfortunately, haven't figured out how to convince automake that I want to
> > > write my own check-am goal, so had to drop dejagnu automake option and
> > > add all
On Mon, Nov 26, 2018 at 04:36:26PM +0100, Richard Biener wrote:
>
> With the relatex outer loop reduction support we need to avoid picking
> up a different nested cycles reduction def. That's easy given we
> record the PHI we are looking at - almost, at least.
Thanks for fixing it. Just a nit,
Hi!
The following testcase fails to assemble, because with -ffunction-sections
and hot/cold partitioning, secname_for_decl returns the same section
for both the hot and cold partition, even when we actually use two different
sections - .text._Z3fooi and .text.unlikely._Z3fooi. If the secname is
t
In the committed patch I forgot that the CONSTRUCTOR to STRING_CST
transformation introduced this summer only takes place for arrays
of char and not also those of wide characters. That resulted in
sprintf incorrectly getting STRING_CSTs for individual elements
of constant wide character arrays li
Hi!
On the following patch -fpack-struct forces TYPE_PACKED on all the classes
and their variants, but we then create a variant of a class instantiation
(const) which doesn't have the TYPE_PACKED set and later finalize the
template main variant, but don't propagate that to the already created
vari
2018-11-26 Uros Bizjak
PR target/88178
* config/i386/i386.c (dbx_register_map): Use IGNORED_DWARF_REGNUM
for registers for which no debug information can be generated.
Use INVALID_REGNUM for non-existent registers.
(dbx64_register_map): Ditto.
(svr4_dbx_register_map): Di
Hi!
The following patch makes def_builtin2 behave consistently wrt.
OPTION_MASK_ISA_64BIT requirement to def_builtin.
The latter has:
tree decl = NULL_TREE;
if (!(mask & OPTION_MASK_ISA_64BIT) || TARGET_64BIT)
{
...
}
return decl;
and so if some builtin requires TARGET_64BIT, it is
On Nov 14, 2018, at 7:56 AM, Jozef Lawrynowicz wrote:
>
> Patch 5 deals with ISO C errors emitted by tests when the large memory model
> is
> used. size_t and ptrdiff_t are __int20 with -mlarge, and if the test is
> compiled with -pedantic-errors and -std=* or -ansi, then use of these types
> ca
Hi!
Marek has changed grokdeclarator in r263836, so that in this part of code
it is either a funcdecl_p (previously the only allowed one), which
implies inner_declarator is non-NULL and therefore unqualified_id too,
or newly inner_declarator == NULL. In that case, we IMHO shouldn't be
testing for
On 11/26/18 7:03 AM, Martin Liška wrote:
> On 11/23/18 6:10 PM, Martin Sebor wrote:
>> On 11/23/18 8:06 AM, Martin Liška wrote:
>>> Hi.
>>>
>>> It's patch proposal that suggests to use an enum instead of 'int endp' for
>>> functions that expand memory move builtins. I've touch the code multiple
>>
Hi!
The following patch fixes a bunch of ICEs in rs6000 print_operand; we
shouldn't ICE on them when users write mess in their inline asm.
Bootstrapped/regtested on powerpc64{,le}-linux (including -m32 testing
on powerpc64-linux), ok for trunk?
2018-11-26 Jakub Jelinek
PR target/8818
On 11/26/18 10:59 AM, Martin Sebor wrote:
> Martin suggested we update the Coding Conventions to describe
> the expected style for function declarations with a pointer
> return types, and for overloaded operators. Below is the patch.
THanks. That's fine.
>
> As an aside, regarding the space con
On Nov 14, 2018, at 7:52 AM, Jozef Lawrynowicz wrote:
>
> Patch 4 fixes tests when int is 16-bits by default.
Ok,
On Nov 14, 2018, at 7:58 AM, Jozef Lawrynowicz wrote:
>
> Patch 6 fixes tests expecting printf float support for targets which have been
> configured with "newlib-nano-formatted-io". When newlib is configured in this
> way, float printf is enabled at build time by registering _printf_float as an
On Nov 21, 2018, at 2:39 PM, Jozef Lawrynowicz wrote:
>
> On Wed, 14 Nov 2018 15:41:00 +
> Jozef Lawrynowicz wrote:
>
>> Patch 3 sets up require-effective-target directives for tests which
>> require the compilation of large arrays.
>> Targets which have 16-bit or 20-bit size_t fail to comp
On Nov 14, 2018, at 7:48 AM, Jozef Lawrynowicz wrote:
>
> Patch 3 sets up require-effective-target directives for tests which
> require the compilation of large arrays.
Ok.
On Nov 20, 2018, at 5:00 PM, Jeff Law wrote:
>
> On 11/16/18 9:29 AM, Andrew Stubbs wrote:
>> This collection of miscellaneous patches configures the testsuite to run on
>> AMD
>> GCN in a standalone (i.e. not offloading) configuration. It assumes you have
>> your Dejagnu set up to run binaries
The aarch64 ISA specification allows a left shift amount to be applied
after extension in the range of 0 to 4 (encoded in the imm3 field).
This is true for at least the following instructions:
* ADD (extend register)
* ADDS (extended register)
* SUB (extended register)
The result of this patc
On 11/26/18 10:27 AM, Joseph Myers wrote:
On Fri, 23 Nov 2018, Martin Sebor wrote:
I have now committed this patch as r266418.
This commit introduced spurious warnings that break the glibc testsuite
build.
bug-ungetwc2.c:62:17: error: '%ls' directive argument is not a nul-terminated
string
On Mon, 2018-11-26 at 18:29 +, Joseph Myers wrote:
> On Mon, 26 Nov 2018, Mark Wielaard wrote:
>
> > Define a new target macro TARGET_HAS_DEFAULT_NOEXEC_STACK for those
> > targets
> > that have a non-executable default stack based on when they call
> > file_end_indicate_exec_stack.
>
> Some
On Mon, 26 Nov 2018, Martin Liška wrote:
> > I don't see how this version ensures that NATIVE_SYSTEM_HEADER_DIR is
> > properly sysrooted. Note there's add_sysrooted_prefix separate from
> > add_prefix (but that's *not* the correct thing to use here because it uses
> > target_sysroot_suffix wh
On Mon, 26 Nov 2018, Martin Liška wrote:
> The header file will be install by glibc (glibc-devel package).
To confirm: you intend to submit a patch to glibc upstream to install this
file (rather than it only being something in distribution packaging)?
--
Joseph S. Myers
jos...@codesourcery.com
On Mon, 26 Nov 2018, Mark Wielaard wrote:
> Define a new target macro TARGET_HAS_DEFAULT_NOEXEC_STACK for those targets
> that have a non-executable default stack based on when they call
> file_end_indicate_exec_stack.
Some targets (e.g. ia64) may default to no-exec stacks without needing
that h
I've checked in this patch for PR 57182.
-Sandra
2018-11-26 Sandra Loosemore
PR c/57182
gcc/
* doc/invoke.texi (Optimize Options): Document that
-freorder-functions also uses "hot" and "cold" attributes.
Index: gcc/doc/invoke.texi
=
On 11/26/18 10:17 AM, Martin Sebor wrote:
On 11/25/18 6:40 PM, Sandra Loosemore wrote:
I've checked in the attached patch for PR79738.
I think we have lost something important with the clarification
of attribute const:
The @code{const} attribute imposes greater restrictions on
a functio
Martin suggested we update the Coding Conventions to describe
the expected style for function declarations with a pointer
return types, and for overloaded operators. Below is the patch.
As an aside, regarding the space convention in casts: a crude
grep search yields about 10,000 instances of the
Hi Martin,
> I have now committed this patch as r266418.
this patch has created a bunch of XPASSes everywhere:
+XPASS: gcc.dg/tree-ssa/builtin-fprintf-warn-1.c pr87756 (test for warnings,
line 119)
+XPASS: gcc.dg/tree-ssa/builtin-fprintf-warn-1.c pr87756 (test for warnings,
line 120)
+XPASS: g
Committing as obvious.
Thanks,
Kyrill
2018-11-26 Kyrylo Tkachov
* config/aarch64/aarch64.c (aarch64_mangle_type): Fix typo in comment.
diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c
index 77d12603e3b9bfdf0f65733162a4320ffc9239f7..58858ef935ba744e6e50b9ceb8cdf182
Hi Christoph,
On 22/11/18 08:00, Christoph Müllner wrote:
On 11/22/18 8:54 AM, Andrew Pinski wrote:
One small comment.
On Tue, Nov 20, 2018 at 10:01 AM Christoph Muellner
wrote:
Tested with "make check" and no regressions found.
This patch depends on the struct xgene1_prefetch_tune,
which
Hi all,
On some cores the X-register MADD/MSUB (and hence MUL and MNEG) instructions
may behave differently
than the W-register forms and the scheduling models may want to reflect that.
That is currently not possible because both sizes use the mla scheduling type.
This patch introduces the mla6
Hi all,
The mul64 attribute in types.md causes some confusion as it is used to represent
aarch32 instructions that do widening multiplication to generate 32->64 bit
results.
But these types are shared with aarch64, which has native 64-bit multiplication
operations.
Those are currently not prop
Hi all,
In the AAarch64 ISA the MUL and MNEG instructions are actually aliases of MADD
and MSUB.
Therefore they should have the type attribute mla, rather than mul, which
should only be used
for AArch32 32-bit multiplication instructions.
This will ensure more consistent scheduling decisions.
Hi Sam,
On 23/11/18 16:55, Sam Tebbs wrote:
Hi all,
The mtune= documentation in doc/invoke.texi contains some obsolete CPU names
that have been removed from the Arm and AArch64 backends. This patch removes
them.
All removed CPU names:
* arm2
* arm250
* arm3
* ar
Hi,
This patch is backported from druntime 2.083, in continuation of
finishing off AArch64 library support.
When throwing an Exception in the Fiber the backtrace generation
crashes. This happens because backtrace does not func the stack
bottom. Using '.cfi_undefined x30' tells the debug info th
On Fri, 23 Nov 2018, Martin Sebor wrote:
> I have now committed this patch as r266418.
This commit introduced spurious warnings that break the glibc testsuite
build.
bug-ungetwc2.c:62:17: error: '%ls' directive argument is not a nul-terminated
string [-Werror=format-overflow=]
62 | fprint
On 11/25/18 6:40 PM, Sandra Loosemore wrote:
I've checked in the attached patch for PR79738.
I think we have lost something important with the clarification
of attribute const:
The @code{const} attribute imposes greater restrictions on
a function's definition than the similar @code{pure} a
The problem here was that we were calling save_expr in a template, which
we shouldn't, as the comment in cp_save_expr explains. This problem
only appears on ptrmemfunc_vbit_in_delta targets.
Bootstrapped/regtested on aarch64-linux, ok for trunk?
2018-11-26 Marek Polacek
PR c++/88120
On 11/23/18 7:08 PM, Joseph Myers wrote:
> On Fri, 23 Nov 2018, Martin Liška wrote:
>
>> Looks the problematic is quite complex as I can understand. I prepared a
>> patch
>> that should hopefully follow advises provided.
Hello.
>
> I don't see how this version ensures that NATIVE_SYSTEM_HEADER
On 11/26/18 5:19 PM, Matthias Klose wrote:
> On 26.11.18 13:20, Martin Liška wrote:
>> On 11/23/18 7:08 PM, Joseph Myers wrote:
>>> In the multiarch case, do you want
>>> /include/finclude/ or
>>> /include//finclude? (This is where I'd hope Debian
>>> / Ubuntu GCC people would comment.)
>>
>> M
On 26.11.18 13:20, Martin Liška wrote:
> On 11/23/18 7:08 PM, Joseph Myers wrote:
>> In the multiarch case, do you want
>> /include/finclude/ or
>> /include//finclude? (This is where I'd hope Debian
>> / Ubuntu GCC people would comment.)
>
> Mathias can you please reply to this?
this should n
On Nov 26, 2018, at 1:46 AM, Thomas Preudhomme
wrote:
> Ping?
The testsuite parts are Ok.
> On Mon, 19 Nov 2018 at 10:51, Thomas Preudhomme
> wrote:
>>
>> FWIW, the testcases were taken from
>> https://gcc.gnu.org/ml/gcc-patches/2015-01/msg01026.html
With the relatex outer loop reduction support we need to avoid picking
up a different nested cycles reduction def. That's easy given we
record the PHI we are looking at - almost, at least.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2018-11-26 Richard Bien
> Am 26.11.2018 um 16:07 schrieb Segher Boessenkool
> :
>
>> # ppc64le-redhat-linux:
>> 511.povray_r -1.29%
>> 482.sphinx3-0.65%
>> 456.hmmer -0.53%
>> 519.lbm_r -0.51%
>> # skip |dt| < 0.5%
>> 549.fotonik3d_r+1.13%
>> 403.gcc+1.76%
>> 500.perlbench
Hi!
On Mon, Nov 26, 2018 at 01:11:40PM +0100, Ilya Leoshkevich wrote:
> In the end, the main question was: does this make the code better on
> architectures other than s390?
> https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00993.html
Yup.
> - Code size decreases in most cases. In general, the ma
gcc/ChangeLog:
2018-11-26 Andreas Krebbel
* doc/invoke.texi: Document z14/arch12 -march option.
---
gcc/doc/invoke.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 38e27a5..e70db55 100644
--- a/gcc/doc/invoke.
On Mon, 2018-11-26 at 08:19 -0500, Paul Koning wrote:
> > On Nov 26, 2018, at 4:13 AM, Mark Wielaard wrote:
> >
> > With -Wtrampolines a warning is produced whenever gcc generates
> > executable
> > code on the stack at runtime to support taking a nested function
> > address
> > that is used to c
On 11/23/18 6:10 PM, Martin Sebor wrote:
> On 11/23/18 8:06 AM, Martin Liška wrote:
>> Hi.
>>
>> It's patch proposal that suggests to use an enum instead of 'int endp' for
>> functions that expand memory move builtins. I've touch the code multiple
>> times
>> and it always take me time to realize
Hi,
Attached is a small patch that, in case of inline assembler code,
indicates that the function stack usage is uncertain due to inline
assembler.
The test suite are using "nop" as an assembler instruction on all
targets, is this acceptable or is there a better way to test this?
Patch has be
On 11/26/18 12:18 PM, Jakub Jelinek wrote:
> On Mon, Nov 26, 2018 at 12:03:53PM +0100, Martin Liška wrote:
>>> For Cascade Lake the model number is the same as Skylake Server,
>>> it can only be distinguished based on the stepping (5 vs 4)
>>
>> Very interesting, probably the first time a distingui
On 26.11.18 14:30, Arnaud Charlet wrote:
>> that fixes the build, taken from the sparc64 file. not sure if that is
>> appropriate.
>
> The patch looks good, you can go ahead and commit it.
done.
>> The build continues, but then fails with:
>>
>> /home/packages/cross/9/p/gcc-cross-ports/gcc/build
> that fixes the build, taken from the sparc64 file. not sure if that is
> appropriate.
The patch looks good, you can go ahead and commit it.
> --- gcc/ada/libgnarl/s-linux__alpha.ads (revision 266457)
> +++ gcc/ada/libgnarl/s-linux__alpha.ads (working copy)
> @@ -87,6 +87,7 @@
>
On 26.11.18 10:22, Arnaud Charlet wrote:
>> r266136 broke the ada build on alpha-linux-gnu, filed as PR88191. I didn't
>> find this patch posted to gcc-patches.
>
> Thanks for the heads up.
>
> This is this change:
>
> [Ada] Update signal constants for GNU/Linux
>
> Add the signal SIGSYS and m
> On Nov 26, 2018, at 4:13 AM, Mark Wielaard wrote:
>
> With -Wtrampolines a warning is produced whenever gcc generates executable
> code on the stack at runtime to support taking a nested function address
> that is used to call the nested function indirectly when it needs to access
> any vari
On 26/11/18 12:03 +, Jonathan Wakely wrote:
On 24/11/18 22:58 +0100, François Dumont wrote:
Tests have shown a regression. I was building the _ReuseOrAllocNode
instance too early, node ownership was transfered but was still
owned by _Hashtable instance.
This new version pass all tests.
On 11/23/18 7:08 PM, Joseph Myers wrote:
> In the multiarch case, do you want
> /include/finclude/ or
> /include//finclude? (This is where I'd hope Debian
> / Ubuntu GCC people would comment.)
Mathias can you please reply to this?
Thanks,
Martin
On 24/11/18 22:58 +0100, François Dumont wrote:
---
a/libstdc++-v3/testsuite/23_containers/unordered_set/allocator/move_assign.cc
+++
b/libstdc++-v3/testsuite/23_containers/unordered_set/allocator/move_assign.cc
@@ -18,6 +18,8 @@
// { dg-do run { target c++11 } }
#include
+#include
+
#includ
Bootstrapped and regtested on x86_64-redhat-linux, s390x-redhat-linux
and ppc64le-redhat-linux.
Previous iteration:
https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00495.html
In the end, the main question was: does this make the code better on
architectures other than s390?
https://gcc.gnu.org/ml/g
On 24/11/18 22:58 +0100, François Dumont wrote:
Tests have shown a regression. I was building the _ReuseOrAllocNode
instance too early, node ownership was transfered but was still owned
by _Hashtable instance.
This new version pass all tests.
This is why it's worth waiting until tests have r
1 - 100 of 113 matches
Mail list logo
