An optional final named argument [Entity => local_NAME] is allowed
for pragma Annotate to indicate that the annotation is for a particular
entity, and a corresponding Annotate aspect is introduced.
Given the test program:
1. package AspectAnn is
2.Y : constant Integer := 43;
3.
This patch allows the renaming and subsequent instantiation of generic
subprograms that are marked Intrinsic, such as the predefined units
Unchecked_Conversion and Unchecked_Deallocation.
The following must execute quietly:
gnatmake -q -gnatws uncrename.adb
uncrename
---
with Mumble;
with
This new restriction No_Long_Long_Integer forbids any explicit reference
to type Standard.Long_Long_Integer, and also forbids declaring range
types whose implicit base type is Long_Long_Integer, and modular types
whose size exceeds Long_Integer'Size. The following is compiled with
-gnatl:
1.
This patch clarifies the need of saving and restoring SPARK_Mode in a stack
like fashion. No change in behavior, no test needed.
Tested on x86_64-pc-linux-gnu, committed on trunk
2014-07-17 Hristian Kirtchev
* sem_ch6.adb (Analyze_Subprogram_Body_Contract,
Analyze_Subprogram_C
This corrects a situation in which extra reads of volatile objects
was being done. It was detected in the case of validity checks
being done on case expressions that were volatile, where two
reads were being done, one for the validity check, and one for
the actual case selection. But the problem is
This patch corrects the transient object machinery to treat the renamed result
of a controlled function call as a finalizable transient when the context is an
expression with actions. If this was a different context, the lifetime of the
result would be considered extended and not finalized.
--
This patch ensures that all delayed SPARK aspects are analyzed with the proper
SPARK mode of their related construct.
-- Source --
-- modes.ads
package Modes
with SPARK_Mode => On,
Abstract_State => State
is
Var : Integer := 1;
procedure Disabled_1 (For
This patch updates the finalization machinery to recognize a case where the
result of a class-wide interface function call with multiple actual parameters
that appears in Object.Operation format requires finalization actions.
-- Source --
-- types.ads
with Ada.Finaliza
This change fixes the circuitry responsible for enforcing the uniqueness
of 'External_Tag attribute values. Previously uniqueness was checked at
type elaboration time only for types that have an explicit External_Tag
attribute definition clause. However we must also account for the fact
that the de
This change addresses a missing unlock operation for the case of a call
to a protected function appearing as the expression of a RETURN statement:
the unlock was inserted after the statement containing the protected function
call, which means that in the case of a RETURN statement it would never be
This change fixes a defect whereby GNAT would fail to generate secondary
stack cleanup code for a scope containing a local object of a limited
discriminated type initialized by a (build-in-place) function call,
thus causing a storage leak.
The following test case must not leak memory for each iter
When a gnat tool (gnatbind, gnatclean, gnatchop, gnatfind, gnatls,
gnatname, gnatprep or gnatmake) is incorrectly invoked, the usage is
no longer displayed. Instead, this line is displayed:
type "gnatxxx --help" for help
Tested on x86_64-pc-linux-gnu, committed on trunk
2014-07-17 Vincent Cel
On Wed, Jul 16, 2014 at 10:40:53PM -0400, Trevor Saunders wrote:
> > +++ b/gcc/inchash.h
> > +class inchash
> > +{
> > + hashval_t val;
>
> normal style would be explicit private: at the end.
Ok.
>
> > + public:
> > +
> > + /* Start incremential hashing, optionally with SEED. */
> > + void
Oops. I've left cris-linux and crisv32-linux alone and rot set
in...quite some time ago. The prerequisite config.gcc I kind of
knew about, but it fell in and out of mind; it was finally noted
in the referenced PR, but just as a side-comment. Regarding the
removed comment, there seems to be nothi
> +++ b/gcc/inchash.h
> +class inchash
> +{
> + hashval_t val;
normal style would be explicit private: at the end.
> + public:
> +
> + /* Start incremential hashing, optionally with SEED. */
> + void begin (hashval_t seed = 0)
> + {
> +val = seed;
why isn't this the ctor?
> + /* Add u
Minor bugfix, committed.
* config/rx/rx.c (rx_option_override): Fix alignment values.
(rx_align_for_label): Likewise.
Index: config/rx/rx.c
===
--- config/rx/rx.c (revision 212709)
+++ config/rx/rx.c (worki
Hello,
in testing the rs6000 ABI patches I noted a weird effect: usually, the
-Wpsabi warning notes are ignored in the compat test suites, so we get
a clean test run anyway.
However, when running the C++ version of the struct-layout-1.exp case
*alone* (using RUNTESTFLAGS=struct-layout-1.exp), sud
OK.
Jason
Hello,
this is the variant intended for the 4.8/4.9 branches of the patch:
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg01072.html
As discussed, it does *not* actually change ABI, but only warn when
encountering a situation where the ABI will change in a future GCC.
(Avoiding the specific term "
On 07/16/2014 12:39 AM, Paolo Carlini wrote:
In practice, both for the original testcase and for a conditional (and
in more cases, eg conditional expressions), what happens is that
perform_implicit_conversion_flags is called, which, when
implicit_conversion fails, calls instantiate_type (and then
Hello,
this is the variant intended for the 4.8/4.9 branches of the patch:
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00995.html
As discussed, it does *not* actually change ABI, but only warn when
encountering a situation where the ABI will change in a future GCC.
(Avoiding the specific term "
Hello,
this is the variant intended for the 4.8/4.9 branches of the patch:
https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00994.html
As discussed, it does *not* actually change ABI, but only warn when
encountering a situation where the ABI will change in a future GCC.
(Avoiding the specific term "
> Instrumentation based FDO is designed to work when the source files
> that are used to generate the instr binary match exactly with the
> sources in profile-use compile. It is known historically that using
> stale profile (due to source changes, not gcda format change) can lead
> to lots of misma
On Wed, 16 Jul 2014, David Wohlferd wrote:
>>> 2014-07-09 David Wohlferd
>>>
>>> PR target/61662
>>> * config/i386/ia32intrin.h: Use __LP64__ to determine size of
>>> long
>> This is OK for mainline and 4.9 backport.
> Thank you for reviewing and approving this. However while
Instrumentation based FDO is designed to work when the source files
that are used to generate the instr binary match exactly with the
sources in profile-use compile. It is known historically that using
stale profile (due to source changes, not gcda format change) can lead
to lots of mismatch warnin
Adhemerval,
This looks very good. Thanks for helping with the FENV implementation.
I will discuss this with some GIMPLE experts during Cauldron. I want
to check that the GIMPLE is correct before approving this.
Thanks, David
There are a few if statements in cfgrtl.c that are very fragile in the
sense that introducing an irrelevant edge flag breaks things.
This patch rewrites them to avoid such breakage.
--
2014-07-16 Yi Yang
gcc:
* cfgrtl.c (rtl_verify_edges, purge_dead_edges): Rewrite certain
if statements.
Ping.
On 03-07-2014 18:08, Adhemerval Zanella wrote:
> This patch implements the TARGET_ATOMIC_ASSIGN_EXPAND_FENV for
> powerpc-fpu. I have to adjust current c11-atomic-exec-5 testcase
> because for IBM long double 0 += LDBL_MAX might generate
> overflow/underflow in internal __gcc_qadd calculati
2014-07-15 13:51 GMT+04:00 S, Pitchumani :
> Hi,
>
> Attached patch adds support for new Atmel xmega devices (atxmega8e5,
> atxmega16e5, atxmega32c3, atxmega32d3).
>
> This patch is continuation of patch in
> https://gcc.gnu.org/ml/gcc-patches/2014-07/msg01038.html
>
> If OK, could someone commit p
2014-07-15 13:18 GMT+04:00 S, Pitchumani :
> Hi,
>
> Attached patch adds support for following Atmel devices.
> ata5702m322
> atmega325pa
> atmega64hve2
> atmega644rfr2
> atmega128rfr2
> atmega1284rfr2
> atmega256rfr2
> atmega2564rfr2
>
> If OK, could someone commit please?
>
> Regards,
> Pitchuman
On 2014-07-16, 7:56 AM, Richard Biener wrote:
This fixes a miscompile of glibc trunk on i?86 which happens because
the sched-deps treats a debug-insn with volatile ASM_OPERANDS
as a barrier.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Ok for trunk and branches?
Ok. It i
On Wed, Jul 16, 2014 at 11:01 AM, Paolo Carlini
wrote:
> Right. And reset too. I'm going to test and apply the below.
Sorry for not reacting to this, I was away from the machines I could
have done that work on.
2014-07-14 15:44 GMT+04:00 S, Pitchumani :
>> -Original Message-
>> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-ow...@gcc.gnu.org]
>> On Behalf Of Denis Chertykov
>> Sent: Friday, July 11, 2014 9:53 PM
>> To: S, Pitchumani
>> Cc: gcc-patches@gcc.gnu.org; Georg-Johann Lay
>> Subj
Aha! Thanks for the update, I can cross that one off my TODO list :)
On Fri, Jun 6, 2014 at 4:31 PM, Jonathan Wakely wrote:
> On 06/06/14 12:40 +0200, Uros Bizjak wrote:
>>
>> On Fri, Jun 6, 2014 at 11:19 AM, Jonathan Wakely
>> wrote:
>>>
>>> On 06/06/14 10:27 +0200, Uros Bizjak wrote:
These two tests timeout on alpha-linux-gnu:
FAIL: 30_t
On Jul 16, 2014, at 7:51 AM, Ed Smith-Rowland <3dw...@verizon.net> wrote:
> Deprecate c++1y. Chane language to reflect greater confidence in C++14
Chane -> Change. I looked at your patch, all seems fine. I like the
documentation edits you did, nice job.
On Tue, Jul 15, 2014 at 04:50:33PM -0500, Segher Boessenkool wrote:
> On Tue, Jul 15, 2014 at 05:20:31PM -0400, Michael Meissner wrote:
> > I did some timing tests to compare the new PowerPC IEEE 128-bit results to
> > the
> > current implementation of long double using the IBM extended format.
>
...as I've not managed to build such a gcc. If so, is there any chance you could
please test check-ada with the following patch (in gcc/ directory), which rolls
back r76965:
Index: combine.c
===
--- combine.c (revision 212523)
++
Thanks for the suggestions! I think I've got a reasonably platform-independent
testcase that scans the rtl dump, just trying it on a few more platforms now...
As to running on Alpha: bootstrap succeeds, and the regression testsuite doesn't
raise any issues (https://gcc.gnu.org/ml/gcc-testresult
Hi,
Richard Smith noticed another case, like '[' in C++11, where we want to
keep the parsing uncommitted after the parenthesized type-id. Tested
x86_64-linux.
Thanks,
Paolo.
/
/cp
2014-07-16 Paolo Carlini
PR c++/61804
* parser.c (cp_parser_tokens_start
On 7/15/2014 11:10 AM, Uros Bizjak wrote:
Hello!
The detailed description and examples can be found in pr61662, but in short: using
"#ifdef
__x86_64__" to determine the size of a 'long' does not reliably yield the
correct result. This
causes _lrotl and _lrotr to return incorrect results on L
Hi,
On 07/16/2014 01:05 PM, Ed Smith-Rowland wrote:
One thing we all forgot: the operator== is also non-trivial because it
needs to compare _M_n.
Right. And reset too. I'm going to test and apply the below.
Thanks,
Paolo.
///
2014-07-16 Paolo Carlini
* include/
This change reorganizes expansion of object initialization statements, which
need to be captured under a single node id. Previously these were represented
as a (malformed) N_Expression_With_Actions with a NULL statement as its
expression. This irregularity is fixed by instead introducing a separate
This patch completes the implementation of Ada 2012 static predicates, by
adding support for case expressions that can be transformed into a statically
evaluable expression on values of the subtype. Compiling:
gcc -c -gnata test_predicate.adb
must yield:
test_predicate.adb:11:20:
warnin
This implements a new warning (on by default, controlled
by -gnatw.z/-gnatw.Z, included in -gnatwa), that warns
if a record type has a specified size and alignment where
the size is not a multiple of the alignment resulting in
an object size greater than the specified size.
The warning is suppress
It is now illegal to use Unrestricted_Access to directly generate a
thin pointer of an unconstrained array type which references a non-
aliased object. This never worked, and we might as well catch it as
illegal, since it is not hard to do so, as shown in the following
example:
1. with System
Hi,
This patch adds myself to the MAINTAINERS file. Commmitted as 212652.
--
2014-07-16 Adhemerval Zanella mailto:azanella%40linux.vnet.ibm.com>>
* MAINTAINERS (Write After Approval): Add myself.
---
--- trunk/MAINTAINERS 2014/07/16 14:21:34 212651
+++ trunk/MAINTAINERS 201
The warning message pattern given for pragma Warning_As_Error or
for pragma Warnings no longer requires leading and trailing asterisks.
The match can be anywhere in the string without these characters
as shown in this example, compiled with -gnatwa -gnatld7 -gnatj55
Compiling: warnmatch.adb
Hello,
Consider this function-like macro definition in this inc.h file:
--->inc.h<---
#define F() const int line = __LINE__
--->8<---
Now consider its use in a file test.c:
-->cat -n test.c<-
This patch modifies the analysis of aspects Abstract_State, Initializes and
Initial_Condition to ensure that they are inserted after pragma SPARK_Mode.
The proper placement allows for SPARK_Mode to be analyzed first and dictate
the mode of the related package.
-- Source --
---
This patch corrects the transient object machinery to treat the renamed result
of a controlled function call as a finalizable transient when the context is an
expression with actions. If this was a different context, the lifetime of the
result would be considered extended and not finalized.
--
This change fixes a compiler crash that would occur in some cases where
an expression involving transient return values of a limited view of a
class-wide interface type occur on the right hand side of a short circuit
operator.
The following compilation must be accepted quietly:
$ gcc -c par-ed.ad
On Wed, 2014-07-16 at 11:23 +0200, Jakub Jelinek wrote:
> On Wed, Jul 16, 2014 at 05:18:06AM -0400, David Edelsohn wrote:
> > > This passed bootstrap and regtesting on powerpc64-linux with no
> > > regressions.
> > > Ok for mainline?
> > >
> > > Peter
> > >
> > > * config.gcc (powerpc*-*-l
Ping.
On Mon, Jun 30, 2014 at 6:07 PM, Siva Chandra wrote:
> On Mon, Jun 30, 2014 at 8:00 AM, Tom Tromey wrote:
>>> "Siva" == Siva Chandra writes:
>>
>> Siva> +# Load the xmethods.
>> Siva> +from libstdcxx.v6.xmethods import register_libstdcxx_xmethods
>> Siva> +register_libstdcxx_xmethods
Richard Biener writes:
> On Tue, Jul 15, 2014 at 3:27 PM, Dodji Seketeli wrote:
>> Hello,
>>
>> When a built-in macro is expanded, the location of the token in the
>> epansion list is the location of the expansion point of the built-in
>> macro.
>>
>> This patch creates a virtual location for th
On 16/07/2014 14:03, Roman Gareev wrote:
Could you prepare such a patch?
Yes, I've started working on it.
I have a question about isl. Can we require that isl is always
compiled with GMP support?
isl 0.12.2 is always compiled with GMP support. Only for the unreleased
isl-0.14 imath was intr
> Could you prepare such a patch?
Yes, I've started working on it.
I have a question about isl. Can we require that isl is always
compiled with GMP support?
--
Cheers, Roman Gareev
This fixes a miscompile of glibc trunk on i?86 which happens because
the sched-deps treats a debug-insn with volatile ASM_OPERANDS
as a barrier.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Ok for trunk and branches?
Thanks,
Richard.
2014-07-16 Richard Biener
PR r
Hi all,
This fixes the PR mentioned in the subject. When expanding
atomic_test_and_set we try the corresponding sync optabs and if none
exist, like for pre-SMP ARM architectures (-march=armv6 and earlier) the
code in optabs.c reverts to a single-threaded implementation that just
does a load a
On 07/14/2014 04:14 AM, Paolo Carlini wrote:
Hi,
On 07/14/2014 09:58 AM, Andreas Schwab wrote:
FAIL: ext/random/arcsine_distribution/cons/default.cc (test for
excess errors)
Excess errors:
/daten/aranym/gcc/gcc-20140714/libstdc++-v3/include/ext/random.tcc:1587:22:
error: '_M_n' was not declar
> On 07/15/2014 04:46 AM, Jan Hubicka wrote:
> >I think we still want to check that the local comdats are linked into
> >the corresponding comdat group, so we probably want
> >to test node->definition instead of node->public, or perhaps just clear
> >COMDAT_GROUP info when removing symbol?
>
> Lik
> On 07/15/2014 11:29 AM, Jan Hubicka wrote:
> >Yep, you are right. I was looking into this, too. I think dump_ada_template
> >should be moved into C++ FE somehow because it deals with C++ trees.
> >What would be most appropriate way to do so?
>
> I suppose we could pass a pointer to it into dump
This fixes two patterns to cure some testsuite FAILs.
Committed.
Richard.
2014-07-16 Richard Biener
* match.pd: Fix two patterns.
Index: gcc/match.pd
===
--- gcc/match.pd(revision 212557)
+++ gcc/match.pd
> Jan Hubicka writes:
> >> Index: gcc/toplev.c
> >> ===
> >> --- gcc/toplev.c 2014-07-11 11:54:41.604838961 +0100
> >> +++ gcc/toplev.c 2014-07-16 08:22:36.226034738 +0100
> >> @@ -1604,6 +1604,10 @@ backend_init_target (void)
> >
Jan Hubicka writes:
>> Index: gcc/toplev.c
>> ===
>> --- gcc/toplev.c 2014-07-11 11:54:41.604838961 +0100
>> +++ gcc/toplev.c 2014-07-16 08:22:36.226034738 +0100
>> @@ -1604,6 +1604,10 @@ backend_init_target (void)
>> on
Uli,
Bootstrap on AIX has been broken because of the generic GCC latent bug
that seems to be popping up on various architectures. I could not
bootstrap GCC from 11 Jul to 14 Jul. I was able to bootstrap on 15
Jul. I want to ensure that bootstrap is functioning consistently
before approving thes
Hi all,
This patch implements the vbsl_f64 intrinsic and adds an execution test
for it.
Not much else to say about it.
Tested aarch64-none-elf.
Ok for trunk?
2014-07-16 Kyrylo Tkachov
* config/aarch64/arm_neon.h (vbsl_f64): New intrinsic.
2014-07-16 Kyrylo Tkachov
* gcc.tar
>
> This causes a segfault on gcc.target/mips/umips-store16-1.c. The register
> asm:
>
> register unsigned int global asm ("$16");
>
> causes us to globalise $16 and call reinit_regs. reinit_regs in turn
> calls ira_init, but IRA hasn't been initialised at this point and
> prerequisites like i
On 16/07/14 09:25, James Greenhalgh wrote:
On Wed, Jul 16, 2014 at 09:05:22AM +0100, Kyrill Tkachov wrote:
Hi all,
I noticed we don't document the clrsb2 optab but it does exist.
The proposed description is based on the clrsb RTL code documentation in
rtl.texi.
While we're at it, clean up the
On 16/07/2014 11:36, Richard Biener wrote:
On Tue, Jul 15, 2014 at 5:34 PM, Tobias Grosser wrote:
On 15/07/2014 17:02, Roman Gareev wrote:
I'm seeing the error:
gcc/graphite-isl-ast-to-gimple.c:31:25: warning: isl/val_gmp.h: No such
file
or directory
when building for aarch64.
isl/val_gmp.
On Tue, Jul 15, 2014 at 3:27 PM, Dodji Seketeli wrote:
> Hello,
>
> When a built-in macro is expanded, the location of the token in the
> epansion list is the location of the expansion point of the built-in
> macro.
>
> This patch creates a virtual location for that token instead,
> effectively tr
On Tue, Jul 15, 2014 at 5:34 PM, Tobias Grosser wrote:
> On 15/07/2014 17:02, Roman Gareev wrote:
>>>
>>> I'm seeing the error:
>>>
>>> gcc/graphite-isl-ast-to-gimple.c:31:25: warning: isl/val_gmp.h: No such
>>> file
>>> or directory
>>>
>>> when building for aarch64.
>>>
>>> isl/val_gmp.h is incl
On 16/07/14 10:22, Marat Zakirov wrote:
Christophe,
Please look at a new patch. Draft tests are OK.
I'll ask your commit approval when full regression (ARM/thumb1/thumb2)
tests are done.
Hi Marat,
I was about to propose the thumb2.md hunk myself, but I'll defer to the
arm maintainers to com
On Wed, Jul 16, 2014 at 05:18:06AM -0400, David Edelsohn wrote:
> > This passed bootstrap and regtesting on powerpc64-linux with no regressions.
> > Ok for mainline?
> >
> > Peter
> >
> > * config.gcc (powerpc*-*-linux*): Include gnu-user.h in tm_file.
> > * config/rs6000/sysv4.h (C
Christophe,
Please look at a new patch. Draft tests are OK.
I'll ask your commit approval when full regression (ARM/thumb1/thumb2)
tests are done.
Thank for your attention.
--Marat
On 07/11/2014 11:19 PM, Christophe Lyon wrote:
The new testcase causes an ICE when the compile is configured
--
On Tue, Jul 15, 2014 at 6:43 PM, Peter Bergner wrote:
> With a recent libsanitizer merge from upstream, we're now seeing a lot
> of ASAN test suite failures with the following error:
>
> ==26426==ASan runtime does not come first in initial library list; you
> should
> either link runtime to y
On Wed, Jul 16, 2014 at 09:05:22AM +0100, Kyrill Tkachov wrote:
> Hi all,
>
> I noticed we don't document the clrsb2 optab but it does exist.
> The proposed description is based on the clrsb RTL code documentation in
> rtl.texi.
> While we're at it, clean up the wording for some other cases in t
Hi all,
I noticed we don't document the clrsb2 optab but it does exist.
The proposed description is based on the clrsb RTL code documentation in
rtl.texi.
While we're at it, clean up the wording for some other cases in the file
which refer to an argument 'x' when they mean to refer to operand
Jan Hubicka writes:
> Hi,
> IRA initialization shows high in profiles even when building lto
> objects. This patch simply delays RTL backend initialization until we
> really decide to output a function. In some cases this avoids the
> initialization completely (like in the case of LTO but also
79 matches
Mail list logo