On 7/4/19 6:33 AM, Richard Biener wrote:
On Wed, Jul 3, 2019 at 2:17 PM Aldy Hernandez wrote:
On 7/3/19 7:08 AM, Richard Biener wrote:
On Wed, Jul 3, 2019 at 11:19 AM Aldy Hernandez wrote:
How about we keep VARYING and UNDEFINED typeless until right before we
call into the ranger. At w
On Tue, 9 Jul 2019, Marc Glisse wrote:
On Mon, 8 Jul 2019, Martin Liška wrote:
The patch apparently has DECL_IS_OPERATOR_DELETE only on the replaceable
global deallocation functions, not all delete operators, contrary to
DECL_IS_OPERATOR_NEW, so the name is misleading. On the other hand, thos
Check for declaration of global variables prior to use in the ownership
checking for SPARK.
There is no impact on compilation.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Yannick Moy
gcc/ada/
* sem_spark.adb (Get_Perm_Or_Tree): Issue an error when
encounteri
Under validity checking mode the compiler may silently skip generating
code to perform runtime range checks.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Javier Miranda
gcc/ada/
* exp_util.adb (Remove_Side_Effects): Preserve the
Do_Range_Check flag.
gcc/tests
No impact on compilation with GCC.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Ed Schonberg
gcc/ada/
* sem_util.adb (Scope_Within_Or_Same): Handle properly task
bodies and protected bodies, so that local variables within have
their proper scopes after
This changes the -gnatRj output from a concatenation of entities to an
array of entities, thus making it strictly conforming JSON and easier to
be parsed by means of GNATColl or Python.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Eric Botcazou
gcc/ada/
* repinfo.ads
Checking of the readable status of sub-expressions occurring in the
target path of an assignment should occur before the right-hand-side is
moved or borrowed or observed.
There is no impact on compilation.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Yannick Moy
gcc/ada/
This patch fixes an exception or erroneous execution, when the
declaration for an object of a composite type that has a dynanic
predicate is initialized with an aggregate that requires expansion into
individual components. Prior to this patch the predicate check for the
object appeared before intia
In the special GNATprove mode for proof of programs, expand the Enum_Rep
attribute reference so that a suitable static integer is in the AST
where required by the rest of analysis.
There is no impact on compilation.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Yannick Moy
gcc
In GNATprove mode, subprograms with a body to inline should have been
filtered in Analyze_Subprogram_Body_Helper to match the conditions for
inlining subprograms in GNATprove. Prevent a call to Set_Body_To_Inline
in GNATprove mode that did not go through this filtering.
There is no impact on compi
This patch fixes and issue whereby applying 'Img to a constant
enumerated character type would result in a compiler crash when
assertions are enabled and infinite recursion when they are not.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Justin Squirek
gcc/ada/
* sem_e
This patch updates the library graph augmentation mechanism of the
elaboration order v4.0 to emulate a particular behavior of the v3.0
scheme involving generic instantiations. If a unit without any
elaboration code instantiates a generic without any elaboration code,
the invocation edge from the in
This patch removes a spurious bug on the use of the current instance of
a generic package G as the actual in a nested instantiation of a generic
unit GU that has a formal package whose generic_package name is G. This
is only legal if G has no generic formal part, and the formal package
declaration
This patch fixes a code generation error on an equality operation one of
whose operands is an overloaded call, and several equality operators are
visible. The resolution would succes but in some cases the wrong entity
was lwfton the equality node, leading to expansion with the wrong
interpretation.
The compiler does not report an error on a generic type that has a
representation clause when its ultimate parent is not a generic formal.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Javier Miranda
gcc/ada/
* sem_ch13.adb (Rep_Item_Too_Early): Representation clauses
Allocator expressions and sub-expressions of (extension) aggregates are
implicitly the source of assignments in Ada. Thus, they should be moved
when of a deep type when checking ownership rules in SPARK.
There is no impact on compilation.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07
This patch enables the elaboration order v4.0 as the default elaboration
order in GNATbind. The previous v3.0 elaboration order is now referred
to as the "legacy elaboration order mechanism" and is available using
binder switch -H.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Hri
This patch fixes the behavior of the compiler on a program with multiple
visibility errors. Previous to this fix the compiler would either crash
or enter an infinite loop on a declaration for the formal in a
subprogram declaration, when the parameter type was given by a selected
component that does
This patch enhances the compiler to add an optional warning for
allocators of anonymous access types due to the somewhat confusing
runtime accessibility checks that they generate. For more details see RM
3.10.2 sections 14/3, 14.1/3, and 14.2/3.
These warnings can now be enabled with -gnatw_a, dis
Replace ". " (i.e. a period followed by two spaces) with ". "; this is
meant to avoid distraction when reading comments, except for the license
section, where apparently this makes the formating nicer. Some comments
have been refilled, in particular those that could fit into fewer lines.
Also, so
This patch adds another suggestion to the elaboration order diagnostics.
An elaboration circularity involving a task activation may be resolved
through pragma Restrictions (No_Entry_Calls_In_Elaboration_Code).
-- Source --
-- no_entry_calls.txt
pragma Restrictions (No_
In the special mode for GNATprove, expand the type of static expressions
like done during compilation, to both get suitable legality checks and
increase the precision of the formal analysis.
There is no impact on compilation.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-09 Yannick
In Ada, the name of operators contains a pair of double quotes, which
need to be properly escaped when the name appears in the JSON output of
-gnatR.
The change also ensures that formal parameters are not listed in the
layout information, since this information is not back-annotated for
them.
Tes
On Mon, 8 Jul 2019, Richard Biener wrote:
>
> This re-instantiates the patch I had to revert earlier, doing it in
> a safer way. We record the original ref so we can do an additional
> disambiguation during vn_reference_lookup_3.
>
> Bootstrap and regtest running on x86_64-unknown-linux-gnu.
A
On 7/9/19 9:49 AM, Marc Glisse wrote:
> On Tue, 9 Jul 2019, Marc Glisse wrote:
>
>> On Mon, 8 Jul 2019, Martin Liška wrote:
>>
The patch apparently has DECL_IS_OPERATOR_DELETE only on the replaceable
global deallocation functions, not all delete operators, contrary to
DECL_IS_OPER
On 02.07.19 17:34, Ilya Leoshkevich wrote:
...
> 2019-06-28 Ilya Leoshkevich
>
> * asan.c (asan_emit_stack_protection): Provide an alignment
> hint.
> * config/s390/s390.h (CODE_LABEL_BOUNDARY): Specify that s390
> requires code labels to be aligned on a 2-byte boundary.
On 7/4/19 6:02 PM, Jan Hubicka wrote:
> perhaps we want to also document that builtin-expect can be used this way?
> It owuld be also nice to have a testcase.
Good idea! I'm going to install the following patch.
Martin
>From 6b59938eff83600ae237409de027040b7904f66d Mon Sep 17 00:00:00 2001
From:
Hi Gaius,
>> it rather depends upon what you want, if you want the latest complete
>> gm2 grafting onto the svn gcc trunk then these two scripts will create a
>> patched tree and also rebuild gm2.
>
> that's my goal: I'd like to see if gm2 and libgm2 build on Solaris and
> pass at least a reasonab
Hi Christophe,
On 7/2/19 3:41 PM, Christophe Lyon wrote:
Hi,
While running the GCC testsuite with an armv8-m target, I noticed that
a few tests where causing the BFD linker to crash. I opened PR
ld/24709 for this [1], but fixing it properly is tricky and not worth
the headache.
I "fixed" the l
Hi Sylvia,
On 7/5/19 12:32 PM, Sylvia Taylor wrote:
Greetings,
This patch removes the arch-common aese/aesmc and aesd/aesimc fusions
(i.e. aes fusion) implemented in the scheduling phase through the
aarch_crypto_can_dual function. The reason is due to observing
undesired behaviour in cases such
On Tue, Jul 9, 2019 at 12:13 AM Jakub Jelinek wrote:
>
> Hi!
>
> The 4 testcases below weren't vectorized, because while
> tree-vect-data-refs.c now allows more forms of simd lane access,
> scan_operand_equal_p didn't allow combining them together.
>
> Fixed thusly, bootstrapped/regtested on x86_6
On 08.07.19 23:19, Matthias Klose wrote:
> On 14.06.19 15:09, Gaius Mulley wrote:
>>
>> Hello,
>>
>> here is version two of the patches which introduce Modula-2 into the
>> GCC trunk. The patches include:
>>
>> (*) a patch to allow all front ends to register a lang spec function.
>>(inc
> Hi.
>
> I'm suggesting to restrict LOOP_ALIGN to only loop headers. That are the
> basic blocks for which it makes the biggest sense. I quite some binary
> size reductions on SPEC2006 and SPEC2017. Speed numbers are also slightly
> positive.
>
> Patch can bootstrap on x86_64-linux-gnu and survi
On Tue, Jul 9, 2019 at 9:28 AM Aldy Hernandez wrote:
>
>
>
> On 7/4/19 6:33 AM, Richard Biener wrote:
> > On Wed, Jul 3, 2019 at 2:17 PM Aldy Hernandez wrote:
> >>
> >> On 7/3/19 7:08 AM, Richard Biener wrote:
> >>> On Wed, Jul 3, 2019 at 11:19 AM Aldy Hernandez wrote:
> >
> >> How about we keep
On 08/07/2019 23:10, Jakub Jelinek wrote:
This broke following testcase.
error_mark_node type isn't really incomplete, it is errorneous, doesn't have
TYPE_MAIN_DECL and we should have diagnosed it earlier, so it makes no sense
to emit extra explanation messages.
Apologies. Did I miss something
> 2019-07-08 Eric Botcazou
>
> * emit-rtl.c (set_insn_locations): New function moved from...
> * function.c (set_insn_locations): ...here.
> * ira-emit.c (emit_moves): Propagate location of the first instruction
> to the inserted move instructions.
> * reg-stack.c
On 7/9/19 11:56 AM, Jan Hubicka wrote:
>> Hi.
>>
>> I'm suggesting to restrict LOOP_ALIGN to only loop headers. That are the
>> basic blocks for which it makes the biggest sense. I quite some binary
>> size reductions on SPEC2006 and SPEC2017. Speed numbers are also slightly
>> positive.
>>
>> Patc
Hi,
On 08/07/19 23:44, Jason Merrill wrote:
On 6/23/19 7:58 AM, Paolo Carlini wrote:
+ error_at (smallest_type_location (get_type_quals (declspecs),
+ declspecs->locations),
How about adding a smallest_type_location overload that just takes
declspecs?
Sure. The below
On Tue, 9 Jul 2019, Martin Liška wrote:
On 7/9/19 9:49 AM, Marc Glisse wrote:
On Tue, 9 Jul 2019, Marc Glisse wrote:
On Mon, 8 Jul 2019, Martin Liška wrote:
The patch apparently has DECL_IS_OPERATOR_DELETE only on the replaceable global
deallocation functions, not all delete operators, con
On Tue, Jul 9, 2019 at 11:56 AM Jan Hubicka wrote:
>
> > Hi.
> >
> > I'm suggesting to restrict LOOP_ALIGN to only loop headers. That are the
> > basic blocks for which it makes the biggest sense. I quite some binary
> > size reductions on SPEC2006 and SPEC2017. Speed numbers are also slightly
> >
On Tue, Jul 9, 2019 at 12:22 PM Richard Biener
wrote:
>
> On Tue, Jul 9, 2019 at 11:56 AM Jan Hubicka wrote:
> >
> > > Hi.
> > >
> > > I'm suggesting to restrict LOOP_ALIGN to only loop headers. That are the
> > > basic blocks for which it makes the biggest sense. I quite some binary
> > > size r
On Tue, Jul 9, 2019 at 12:23 PM Richard Biener
wrote:
>
> On Tue, Jul 9, 2019 at 12:22 PM Richard Biener
> wrote:
> >
> > On Tue, Jul 9, 2019 at 11:56 AM Jan Hubicka wrote:
> > >
> > > > Hi.
> > > >
> > > > I'm suggesting to restrict LOOP_ALIGN to only loop headers. That are the
> > > > basic bl
On Mon, Jul 8, 2019 at 2:04 PM Martin Liška wrote:
>
> On 6/21/19 4:28 PM, Richard Biener wrote:
> > On Fri, Jun 21, 2019 at 4:13 PM Jakub Jelinek wrote:
> >>
> >> On Fri, Jun 21, 2019 at 04:04:00PM +0200, Martin Liška wrote:
> >>> On 6/21/19 1:58 PM, Jakub Jelinek wrote:
> On Fri, Jun 21, 2
I've backported Jakub's patch to openacc-gcc-9-branch.
Andrew
On 08/07/2019 23:10, Jakub Jelinek wrote:
On Thu, Jul 04, 2019 at 12:44:32PM +0100, Andrew Stubbs wrote:
On 03/07/2019 18:58, Jason Merrill wrote:
OK, thanks.
Committed.
This broke following testcase.
error_mark_node type isn't
Rainer Orth writes:
> here are some initial issues. I'll reply to Matthias' mail to expand on
> other problems he's raised.
>
> * First, the build broke like this:
>
> /vol/gcc/src/hg/trunk/solaris/gcc/gm2/mc-boot/GRTint.c:57:30: error: 'time'
> redeclared as different kind of symbol
>57 |
On 7/9/19 6:39 AM, Richard Biener wrote:
On Mon, Jul 8, 2019 at 2:04 PM Martin Liška wrote:
Same happens also for GCC7. It does 17 iteration (#define MAX_ITERATIONS 17) and
apparently 17 is not enough to resolve all symbols. And it's really slow.
Ouch.
hm, 17 is a magic number. in C++
Hi,
this is updated patch. I based the logic on gimple_compare_field_offset but
dropped bits about PLACEHOLDER_EXPR since my understanding is that to get
comparsion done I would then need to compare operand #2 of COMPONENT_REF which
I don't.
I also wrote the range checks using polyint since I bel
Matthias Klose writes:
>> - There are three letter libraries with pretty generic
>>names installed into the system libdir: log, iso, cor,
>>min, ulm. At least for log, you have a file conflict
>>with another library. Shouldn't these libraries named
>>mpre specific, like libgm2lo
On Tue, 9 Jul 2019, Jan Hubicka wrote:
> Hi,
> this is updated patch. I based the logic on gimple_compare_field_offset but
> dropped bits about PLACEHOLDER_EXPR since my understanding is that to get
> comparsion done I would then need to compare operand #2 of COMPONENT_REF which
> I don't.
>
> I
We're relying on this for correctness, placing an assert triggers
easily so we're not handling things fully correctly in all paths
leading up to here. So simply valueize appropriately in
vn_nary_build_or_lookup_1 which should make using value-numbers
where it is more natural possible.
I've also
Hello Jim,
On 2019/07/08 13:41, Jim Wilson wrote:
On Sat, Jul 6, 2019 at 1:26 AM Katsuhiro Suzuki wrote:
This patch fixes ambiguous mode of some compare insns of RISC-V.
Only sge, slt and sle are using but other compare insns use
. It seems first group mode settings are ambiguous.
Richard S
Hi Matthias,
> I had a look at the GCC 9 version of the patches, with a build including a
> make
> install. Some comments:
>
> - A parallel build (at least with -j4) isn't working. A sequental
>build works fine. I think forcing a sequential build will not
>work well, increasing the buil
> For consistency yes I guess but IIRC they cannot really appear in
> FIELD_DECLs.
OK, i tought that if I put SVE into structures, we may end up with
these.
> > + /* Different fields of the same record type cannot overlap.
> > +??? Bitfields can overlap at RTL level so punt on them. */
On Tue, 9 Jul 2019, Jan Hubicka wrote:
> > For consistency yes I guess but IIRC they cannot really appear in
> > FIELD_DECLs.
>
> OK, i tought that if I put SVE into structures, we may end up with
> these.
> > > + /* Different fields of the same record type cannot overlap.
> > > + ??? Bitf
Hi Sylvia,
On 7/8/19 5:59 PM, Sylvia Taylor wrote:
Hi James,
I forgot to mention that. Yes, please do commit it on my behalf.
I've committed this on your behalf with r273304.
Thanks,
Kyrill
Cheers,
Syl
On 7/9/19 1:41 PM, Nathan Sidwell wrote:
> On 7/9/19 6:39 AM, Richard Biener wrote:
>> On Mon, Jul 8, 2019 at 2:04 PM Martin Liška wrote:
>>>
>
>>>
>>> Same happens also for GCC7. It does 17 iteration (#define MAX_ITERATIONS
>>> 17) and
>>> apparently 17 is not enough to resolve all symbols. And
Hello,
New since v2:
- Fix comment formatting pointed out by Segher in valatile patch
- Fix issue and add test for rotrsi3 options pointed out by Segher
- Fix issue with reg mask for doubles being backwards Pointed out by Segher
and Richard.
New since v1:
- Changed 64-bit FPU operations to
Volatile memory does not match the memory_operand predicate. This
causes extra extend/mask instructions instructions when reading
from volatile memory. On OpenRISC loading volatile memory can be
treated the same as regular memory loads which supports combined
sign/zero extends. Fixing this elimi
This adds support for OpenRISC hardware floating point instructions.
This is enabled with the -mhard-float option.
Double-prevision floating point operations work using register pairing as
specified in: https://openrisc.io/proposals/orfpx64a32. This has just been
added in the OpenRISC architectur
The force_reg in or1k_expand_compare is hard coded for SImode, which is fine as
this used to only be used on SI expands. However, with FP support this will
cause issues. In general we should only force the right hand operand to a
register if its an immediate. This patch adds an condition to chec
Fixes bad assembly logic with software divide as reported by Richard Selvaggi.
Also, add a basic test to verify the soft math works when enabled.
gcc/testsuite/ChangeLog:
PR target/90362
* gcc.target/or1k/div-mul-3.c: New test.
libgcc/ChangeLog:
PR target/90362
*
gcc/ChangeLog:
* config.gcc (or1k*-*-*): Add mrori and mror to validation.
* doc/invoke.texi (OpenRISC Options): Add mrori option, rewrite all
documenation to be more clear.
* config/or1k/elf.opt (mboard=, mnewlib): Rewrite documentation to be
more clear.
> > tree_int_cst_equal will return false if offsets are not INTEGER_CST.
> > I was not sure if I can safely use operand_equal_p. What happens for
> > fields with variable offsets when I inline two copies of same function
> > which takes size as parameter and make the size different? Will I get
> >
Hi,
On Tue, 9 Jul 2019, Richard Biener wrote:
> > So a "backedge" in this sense would be e->dest->index < e->src->index.
> > No?
>
> To me the following would make sense.
The basic block index is not a DFS index, so no, that's not a test for
backedge.
Ciao,
Michael.
On 09.07.19 14:02, Gaius Mulley wrote:
> Matthias Klose writes:
>
>>> - There are three letter libraries with pretty generic
>>>names installed into the system libdir: log, iso, cor,
>>>min, ulm. At least for log, you have a file conflict
>>>with another library. Shouldn't these lib
The following fixes PR91114. It's not really the most desirable
solution but hey.
Bootstrapped / tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2019-07-09 Richard Biener
PR tree-optimization/91114
* tree-vect-data-refs.c (vect_analyze_data_refs): Failure to
On Tue, 9 Jul 2019, Jan Hubicka wrote:
> > > tree_int_cst_equal will return false if offsets are not INTEGER_CST.
> > > I was not sure if I can safely use operand_equal_p. What happens for
> > > fields with variable offsets when I inline two copies of same function
> > > which takes size as param
Hi,
this is updated variant I am testing.
It documents better how function works and streamlines the checks.
OK assuming it passes the tests?
Honza
Index: tree-ssa-alias.c
===
--- tree-ssa-alias.c(revision 273193)
+++ tree-ssa-a
On Tue, 9 Jul 2019, Jan Hubicka wrote:
> Hi,
> this is updated variant I am testing.
> It documents better how function works and streamlines the checks.
>
> OK assuming it passes the tests?
>
> Honza
>
> Index: tree-ssa-alias.c
>
Matthias Klose writes:
>> the libraries ./usr/lib/x86_64-linux-gnu/lib{ulm,pim,gm2,cor,iso,min}.a
>> are not needed the correct locations of the static libraries are:
>>
>> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/ulm/libulm.a
>> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/min/libmin.a
>> ./usr/lib/gcc/x86_6
Martin Sebor writes:
> Hopefully with the right patch this time (thanks Jon).
>
> On 7/8/19 4:00 PM, Martin Sebor wrote:
>> The attached patch changes the class-key of class definitions that
>> satisfy the requirements on a POD struct to 'struct', and that of
>> struct definitions that aren't POD
Hi,
Without the patch, I see these error messages with gdb 8.3:
(gdb) Python Exception 'fclose@@GLIBC_2.2.5' has
unknown return type; cast the call to its declared return type:
(gdb) Error occurred in Python: 'fclose@@GLIBC_2.2.5' has unknown
return type; cast the call to its dec
Martin Sebor writes:
> diff --git a/gcc/cp/cp-tree.h b/gcc/cp/cp-tree.h
> index cfc41e1ed86..625d5b17413 100644
> --- a/gcc/cp/cp-tree.h
> +++ b/gcc/cp/cp-tree.h
> @@ -6428,7 +6428,7 @@ extern tree get_scope_of_declarator (const
> cp_declarator *);
> extern void grok_special_member_p
This patch suppresses the warning: "enumeration value not handled in
switch", for enumerators that are defined in system headers and use
reserved names.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2019-07-08 Matthew Beliveau
PR c++/90590
* c-warn.c (c_do_switch_warnings): Suppress
Rainer Orth writes:
> Hi Matthias,
>
>> I had a look at the GCC 9 version of the patches, with a build including a
>> make
>> install. Some comments:
>>
>> - A parallel build (at least with -j4) isn't working. A sequental
>>build works fine. I think forcing a sequential build will not
>>
On 09.07.19 15:41, Gaius Mulley wrote:
> Matthias Klose writes:
>
>>> the libraries ./usr/lib/x86_64-linux-gnu/lib{ulm,pim,gm2,cor,iso,min}.a
>>> are not needed the correct locations of the static libraries are:
>>>
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/ulm/libulm.a
>>> ./usr/lib/gcc/x86_64-lin
Hi Jeff,
Please find attached the updated patch.
What is new:
- mailing list feedback is taken into account.
- some comments are updated.
- a new test is added.
- the ARC AUX registers used by ZOL (hardware loop) and FPX (a custom
floating point implementation) are saved before fp-register.
- the
On 7/9/19 7:48 AM, Richard Sandiford wrote:
Martin Sebor writes:
Hopefully with the right patch this time (thanks Jon).
On 7/8/19 4:00 PM, Martin Sebor wrote:
The attached patch changes the class-key of class definitions that
satisfy the requirements on a POD struct to 'struct', and that of
s
On July 9, 2019 3:10:19 PM GMT+02:00, Michael Matz wrote:
>Hi,
>
>On Tue, 9 Jul 2019, Richard Biener wrote:
>
>> > So a "backedge" in this sense would be e->dest->index <
>e->src->index.
>> > No?
>>
>> To me the following would make sense.
>
>The basic block index is not a DFS index, so no, that'
On Tue, Jul 09, 2019 at 10:28:06AM +0800, Kewen.Lin wrote:
> on 2019/7/9 上午12:32, Segher Boessenkool wrote:
> > On Mon, Jul 08, 2019 at 04:07:00PM +0800, Kewen.Lin wrote:
> >> --- /dev/null
> >> +++ b/gcc/testsuite/gcc.dg/tree-ssa/pr88497-1.c
> >> @@ -0,0 +1,60 @@
> >> +/* { dg-do run } */
> >> +/*
Matthias Klose writes:
> And an unrelated one: You are introducing python2 as a build-dependency.
> Afaics, it's only one invocation
>
> python ../../src/gcc/gm2/tools-src/def2texi.py -uLibraries -s../../src/gcc/gm2
> -b/home/packages/gcc/9/u/gcc-9-9.1.1/build/gcc/gm2 >
> /home/packages/gcc/9/u/g
On 07/04/2019 03:43 AM, Richard Biener wrote:
Hmm...a GCC plugin for CTF generation at compile-time may work out for a single
compilation unit. But I am not sure how will LTO be supported in that case.
Basically, for LTO and -gtLEVEL to work together, I need the lto-wrapper to be
aware of the
On 09.07.19 17:53, Gaius Mulley wrote:
> Rainer Orth writes:
>
>> Hi Matthias,
>>
>>> I had a look at the GCC 9 version of the patches, with a build including a
>>> make
>>> install. Some comments:
>>>
>>> - A parallel build (at least with -j4) isn't working. A sequental
>>>build works fine
On Mon, Jul 08, 2019 at 01:53:13PM -0500, Segher Boessenkool wrote:
> Please do; as a separate patch. Thanks in advance. A patch purely moving
> it back is pre-approved.
I just committed this patch:
2019-07-09 Michael Meissner
* config/rs6000/rs6000-internal.h (create_TOC_reference)
On Tue, Jul 09, 2019 at 11:18:53AM -0400, Matthew Beliveau wrote:
> index 000..8aa65cf0afd
> --- /dev/null
> +++ gcc/testsuite/c-c++-common/pr90590-2.c
> @@ -0,0 +1,8 @@
> +#include "pr90590-2.h"
> +
> +void
> +fn ()
> +{
> + switch (c.b) // { dg-bogus "enumeration value" }
> +;
> +}
On 7/9/19 9:00 AM, Martin Liška wrote:
On 7/9/19 1:41 PM, Nathan Sidwell wrote:
On 7/9/19 6:39 AM, Richard Biener wrote:
On Mon, Jul 8, 2019 at 2:04 PM Martin Liška wrote:
Same happens also for GCC7. It does 17 iteration (#define MAX_ITERATIONS 17) and
apparently 17 is not enough to reso
On Tue, Jul 09, 2019 at 01:32:26PM -0400, Michael Meissner wrote:
> On Mon, Jul 08, 2019 at 01:53:13PM -0500, Segher Boessenkool wrote:
> > Please do; as a separate patch. Thanks in advance. A patch purely moving
> > it back is pre-approved.
>
> I just committed this patch:
>
> 2019-07-09 Mich
On 7/9/19 9:17 AM, Richard Sandiford wrote:
Martin Sebor writes:
diff --git a/gcc/cp/cp-tree.h b/gcc/cp/cp-tree.h
index cfc41e1ed86..625d5b17413 100644
--- a/gcc/cp/cp-tree.h
+++ b/gcc/cp/cp-tree.h
@@ -6428,7 +6428,7 @@ extern tree get_scope_of_declarator (const
cp_declarator *);
On 7/8/19 8:37 PM, Martin Sebor wrote:
> Ping: https://gcc.gnu.org/ml/gcc-patches/2019-06/msg01506.html
>
> Jeff (et al.), do you have any outstanding questions/concerns
> about the patch?
Sorry I wasn't clear. All my concerns are resolved. The patch is fine
for the trunk.
jeff
>
On Mon, 8 Jul 2019 09:05:04 -0700
Steve Kargl wrote:
> On Mon, Jul 08, 2019 at 04:02:17PM +0300, Janne Blomqvist wrote:
> >
> > Good point. If you happen to have a USB stick handy, can you try the
> > simple C benchmark program at
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91030#c38 ?
> >
On 7/8/19 1:11 AM, John Darrington wrote:
> gcc/
> * simplify-rtx.c (simplify_unary_operation_1): Change BITSIZE to PRECISION
> in simplification of (extend ashiftrt (ashift ..))) Otherwise the
> gcc_assert can catch when dealing with partial int modes.
THanks. I edited the ChangeLog entry a bi
On Wed, 27 Feb 2019, Tom G. Christensen wrote:
> Latest results for 7.x.
>
> -tgc
>
> Testresults for 7.4.0:
> x86_64-w64-mingw32
Thank you, applied (finally).
Gerald
Matthias Klose writes:
>> - libpth.{a,so} is installed in the system libdir, which
>>conflicts with the installation of the libpth packages
>>on most distros.
>
> found out that a system provided libpth can be used. Otoh if you build the
> in-tree libpth, it shouldn't be installed, but
On Wed, 27 Feb 2019, Tom G. Christensen wrote:
> Latest results for 6.x.
Applied, thank you! Note, I had to manually apply the last
three hunks, since patch somehow did not like the format (w/o
me seeing anything obviously wrong):
> Testresults for 6.5.0:
> hppa2.0w-hp-hpux11.11
> hppa64-hp-
On Sat, 19 Jan 2019, Jakub Jelinek wrote:
>> how about the refinement below?
> LGTM. Thanks.
The context has changed a bit since then (due to links being
added), so I had to manually re-apply the patch and committed
the following now.
Gerald
Index: changes.html
=
This patch prevents merging of CALL instructions that that have different
REG_CALL_DECL notes attached to them.
On most architectures this is not an important distinction. Usually instruction
patterns
for calls to different functions reference different SYMBOL_REF-s, so they
won't match.
On MIPS
On 7/9/19 6:17 AM, Marc Glisse wrote:
On Tue, 9 Jul 2019, Martin Liška wrote:
On 7/9/19 9:49 AM, Marc Glisse wrote:
On Tue, 9 Jul 2019, Marc Glisse wrote:
On Mon, 8 Jul 2019, Martin Liška wrote:
The patch apparently has DECL_IS_OPERATOR_DELETE only on the
replaceable global deallocation fu
On 9 July 2019 15:37:30 CEST, Richard Biener wrote:
>On Tue, 9 Jul 2019, Jan Hubicka wrote:
>
>> Hi,
>> this is updated variant I am testing.
>> It documents better how function works and streamlines the checks.
>>
>> OK assuming it passes the tests?
>>
>> Honza
>>
>> Index: tree-ssa-alias.c
>>
On 7/9/19 6:10 AM, Paolo Carlini wrote:
Hi,
On 08/07/19 23:44, Jason Merrill wrote:
On 6/23/19 7:58 AM, Paolo Carlini wrote:
+ error_at (smallest_type_location (get_type_quals (declspecs),
+ declspecs->locations),
How about adding a smallest_type_location overload that
On 7/9/19 1:48 PM, Nathan Sidwell wrote:
On 7/9/19 9:00 AM, Martin Liška wrote:
On 7/9/19 1:41 PM, Nathan Sidwell wrote:
On 7/9/19 6:39 AM, Richard Biener wrote:
On Mon, Jul 8, 2019 at 2:04 PM Martin Liška wrote:
Same happens also for GCC7. It does 17 iteration (#define
MAX_ITERATIONS
1 - 100 of 122 matches
Mail list logo
