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
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
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
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
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
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
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
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 kirtc...@adacore.com
* sem_ch6.adb (Analyze_Subprogram_Body_Contract,
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 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;
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 modifies the parser to catch a case where the argument of SPARK
aspect Refined_State is not properly parenthesized.
-- Source --
-- no_parens.ads
package No_Parens
with SPARK_Mode = On,
Abstract_State = State
is
pragma Elaborate_Body;
end
Since this only affects m68k I have pushed this now.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different.
This marks two APIs (gimple_match_and_simplify overloads) as
obsolete - users should use fold_stmt and gimple_fold_stmt_to_constant
instead (actual implementation re-org pending).
It also adds a missing overload to gimple_convert with a location_t
argument.
Committed.
Richard.
2014-07-17
Hi,
This is a series of three patches improving induction variable elimination.
Currently GCC only eliminates iv for very specific case when the loop’s
latch could run zero times, i.e., when may_be_zero field of loop niter
information evaluates to true. In fact, it’s so specific that
Hi,
As quoted from the function difference_cannot_overflow_p,
/* TODO: deeper inspection may be necessary to prove the equality. */
switch (code)
{
case PLUS_EXPR:
return expr_equal_p (e1, offset) || expr_equal_p (e2, offset);
case POINTER_PLUS_EXPR:
return
Hi,
Function iv_elimination_compare_lt is used to eliminate induction variable
when the loop's latch could run for zero time (i.e., may_be_zero in loop
niter information evaluates to true). As stated in the first message, it
only handles very specific case that rarely happens for either GCC
Hi,
On 07/17/2014 02:40 AM, Jason Merrill wrote:
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
Hi,
I see regressions in some UBSan output pattern tests (bounds-2.c and
some others) on arm-linux-gnueabi if we use ssh to deliver executables
to remote target. After some investigation, I discovered, that Dejagnu
deletes trailing '\n' symbol from output message in this case. My patch
Hi all,
we have merged the gcc-4_9-branch into linaro/gcc-4_9-branch up to
revision 212419 as r212661. We have also backported this set of revisions:
r209794 as r212697 : PR c/60114
r209797 as r212675 : [ARM] Wrap long literals in HOST_WIDE_INT_C in
aarch-common.c
r209858 as r212697 :
On Thu, Jul 17, 2014 at 01:45:42PM +0400, Maxim Ostapenko wrote:
I see regressions in some UBSan output pattern tests (bounds-2.c and some
others) on arm-linux-gnueabi if we use ssh to deliver executables to remote
target. After some investigation, I discovered, that Dejagnu deletes
trailing
On 9 July 2014 15:37, Kyrill Tkachov kyrylo.tkac...@arm.com wrote:
Hi all,
These intrinsics are implemented as macros that map down to asms but the
types they accept are inconsistent with the ACLE spec. This patch fixes
them, although they should be reimplemented properly in C in the future.
On 20 June 2014 15:17, Kyrill Tkachov kyrylo.tkac...@arm.com wrote:
Hi all,
Now that Alan fixed the float64x1_t machinery, this patch implements some
low-hanging intrinsics
in arm_neon.h.
Tested aarch64-none-elf and bootstrapped on aarch64-linux.
Ok for trunk?
Thanks,
Kyrill
On 10 July 2014 08:56, Kyrill Tkachov kyrylo.tkac...@arm.com wrote:
On 02/07/14 08:59, Christophe Lyon wrote:
Hi,
It seems some of the scan-assembler directives fail:
On 07/17/2014 01:49 PM, Jakub Jelinek wrote:
On Thu, Jul 17, 2014 at 01:45:42PM +0400, Maxim Ostapenko wrote:
I see regressions in some UBSan output pattern tests (bounds-2.c and some
others) on arm-linux-gnueabi if we use ssh to deliver executables to remote
target. After some investigation,
On Thu, Jul 17, 2014 at 02:12:23PM +0400, Maxim Ostapenko wrote:
Thanks, fixed. Ok now?
-Maxim
2014-07-17 Max Ostapenko m.ostape...@partner.samsung.com
* c-c++-common/ubsan/bounds-2.c: Change output pattern.
* c-c++-common/ubsan/bounds-5.c: Likewise.
*
Committed as obvious.
commit 713d72fb657827ced70636147fd1c7217891f4f7
Author: Jonathan Wakely jwak...@redhat.com
Date: Thu Jul 17 11:43:21 2014 +0100
* doc/extend.texi (Template Instantiation): Remove stray parenthesis.
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index
On 07/17/2014 02:31 PM, Jakub Jelinek wrote:
On Thu, Jul 17, 2014 at 02:12:23PM +0400, Maxim Ostapenko wrote:
Thanks, fixed. Ok now?
-Maxim
2014-07-17 Max Ostapenko m.ostape...@partner.samsung.com
* c-c++-common/ubsan/bounds-2.c: Change output pattern.
*
On Wed, Jul 16, 2014 at 2:03 AM, Andrew MacLeod amacl...@redhat.com wrote:
I don't have the time I'd like to since I'm running about a month behind
schedule, but I wanted to make the code I've been experimenting with
available a bit before cauldron so we can discuss it both here and in the
On 07/16/2014 01:32 PM, Kyrill Tkachov wrote:
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
My earlier patch for 61659 caused more virtual functions to be
instantiated when -fdevirtualize is on, leading to additional errors
appearing at higher optimization levels. This patch shifts that
instantiation to a new flag, -fuse-all-virtuals, which is on by
default, and adds an explanatory
This fixes PR61823, we need to use the proper varpool API now
to access DECL_INITIAL of globals.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2014-07-17 Richard Biener rguent...@suse.de
PR ipa/61823
* tree-ssa-structalias.c
I see. Could you use vec_safe_grow_cleared(iv_map, loop_num) instead?
This shows probably better that you zero initialize the vector.
If I am not mistaken, vec_safe_grow_cleared has the following declaration:
vec_safe_grow_cleared (vecT, A, vl_embed *v, unsigned len CXX_MEM_STAT_INFO)
Should
I've attached the patch, which adds the requirement for isl 0.12.
Tobias, is it important to accept only 0.12.1, 0.12.2 and forbid 0.12?
--
Cheers, Roman Gareev
2014-07-12 Roman Gareev gareevro...@gmail.com
* configure.ac: Don't accept isl 0.11.
On 17/07/2014 16:11, Roman Gareev wrote:
I've attached the patch, which adds the requirement for isl 0.12.
Tobias, is it important to accept only 0.12.1, 0.12.2 and forbid 0.12?
I am not aware of any problems with isl 0.12 and would be surprised if
such problems exist. Are you?
The patch
On 17/07/2014 16:08, Roman Gareev wrote:
I see. Could you use vec_safe_grow_cleared(iv_map, loop_num) instead?
This shows probably better that you zero initialize the vector.
If I am not mistaken, vec_safe_grow_cleared has the following declaration:
vec_safe_grow_cleared (vecT, A, vl_embed *v,
On 06/30/2014 08:54 PM, Jeff Law wrote:
On 06/30/14 05:49, Martin Liška wrote:
On 06/17/2014 10:00 PM, Jeff Law wrote:
On 06/13/14 04:26, mliska wrote:
Hi,
this small patch prepares remaining needed infrastructure for
the new pass.
Changelog:
2014-06-13 Martin Liska mli...@suse.cz
With a recent mainline libsanitizer merge from upstream, we're now seeing a
lot of mainline 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 your application or manually preload it with
With a recent mainline libsanitizer merge from upstream, we're now seeing a
lot of mainline 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 your application or manually preload it with
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.
The
Bootstrapped/regtested x86_64-linux
Ready for trunk?
gcc/ChangeLog:
2014-07-17 Martin Liska mli...@suse.cz
* cgraph.h (varpool_node):
(availability get_availability (void)):
created from cgraph_variable_initializer_availability
(inline varpool_node
OK.
Jason
On 17 July 2014 02:51:14 Ulrich Weigand uweig...@de.ibm.com wrote:
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
Ok, the attached tests are passing on x86_64-none-linux-gnu, aarch64-none-elf,
arm-none-eabi, and a bunch of smaller platforms for which I've only built a
stage 1 compiler (i.e. as far as necessary to assemble). That's with either
change to simplify_shift_const_1.
As to the addition of
On Wed, Jul 16, 2014 at 4:42 PM, Jan Hubicka hubi...@ucw.cz wrote:
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
I see why you do not like first_global_object_name because changing it would
cause
all functions from that unit to drop the profiles. Perhaps we can combine
function name
and compilation unit (gcov file) name?
that is a good idea -- it will also solve the LTO problem you mentioned above.
Richard Sandiford rdsandif...@googlemail.com writes:
Jan Hubicka hubi...@ucw.cz 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
umips-lwp-[1234].c test that two loads from consecutive memory locations
to consecutive registers ($5 and $6) can use LWP. The idea was to have
2 tests where $5 was loaded first before $6 and 2 tests that were the
other way around (at least when scheduling is enabled). I'd tried to force
that by
The p5600 scheduler wasn't restricting itself to -mtune=p5600 and so
was being used for other CPUs too. This showed up as a failure in
various tests, including gcc.target/mips/octeon-pipe-1.c. (Thinking
about it, it was probably also why umips-lwp-*.c started failing,
although the patch I just
Unless someone objects, I am going to commit this to the
4.9 branch and head.
--joel
On 7/7/2014 1:42 AM, Sebastian Huber wrote:
Ping.
On 2014-06-26 13:43, Sebastian Huber wrote:
This patch should be applied to GCC 4.9 and mainline. I do not have
write access, so in case this gets
On Tue, 15 Jul 2014, Dan D. wrote:
Are you still interested in the mirrors?
Yep. This is the patch I just committed to our web site.
If there are further updates, best propose a patch against
https://gcc.gnu.org/mirrors.html , that is the fastest way
and ensure things show up as you want them
Because the atomic sync functions in config/pa/linux-atomic.c are not
lock free, we need to use
__kernel_cmpxchg for the __sync_lock_release. This was found in
glibc's pthread_spin_unlock
implementation.
Tested on hppa-unknown-linux-gnu. Committed to trunk.
Dave
--
John David Anglin
The attached change enables future support using the kernel assisted
atomic support. It's a bit
of a fudge since the libcall routines are not lock free, but
everything appears to work.
Tested on hppa-unknown-linux-gnu. Committed to trunk.
Dave
--
John David Anglin
On 07/08/2014 02:50 PM, Jan Hubicka wrote:
I am looking into tracking dynamic types now. Obviously I need to set very
exact rules about when these may change.
Let me first say that this area is somewhat in flux in the standard; if
we have a model of what we want the rules to be for GCC,
On Thu, Jul 17, 2014 at 06:36:31AM +0200, Andi Kleen wrote:
On Wed, Jul 16, 2014 at 10:40:53PM -0400, Trevor Saunders wrote:
+ public:
+
+ /* Start incremential hashing, optionally with SEED. */
+ void begin (hashval_t seed = 0)
+ {
+val = seed;
why isn't this
Hi!
As a leftover of r210931, an unused variable resulted in:
g++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions
-fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
On 07/14/14 20:25, Bernd Edlinger wrote:
Hi,
When I try to print the dumps of fold-const.c
with -fdump-rtl-all-slim cc1plus crashes.
This is caused by pretty-printing the ADDR_VEC pattern,
which has a single argument, a vector of LABEL_REFs at position 0.
But instead XEXP(x,0) is printed, which
On 07/15/14 06:03, Richard Biener wrote:
The following tries to clarify the always_inline docs, in particular
that it applies to non-O0 as well and what the failure mode is
(derived from how our implementation behaves).
Does this look ok?
Thanks,
Richard.
2014-07-15 Richard Biener
On 07/13/14 22:17, Maxim Kuvyrkov wrote:
Hi,
This patch adds dump printouts for scheduling heuristics in
rank_for_schedule. Rank_for_schedule is one of the cornerstones of
haifa scheduler, yet its decisions are hard to track and debug.
This patch adds statistical gathering for each branch of
On 07/11/14 03:01, Martin Liška wrote:
Hello,
I fixed Options That Control Optimization section according to 'gcc
-Q --help=optimizers' and after consultation with Jakub, I added missing
-foptimize-strlen option.
Ready for trunk?
Martin
ChangeLog:
2014-07-11 Martin Liska mli...@suse.cz
On 07/12/14 03:51, Zamyatin, Igor wrote:
Hi!
This patch adds correct handling of declarations whit initializations that
contain array notation.
It fixes ICE in PR61455.
Regtested for x86_64 (along with the first patch in the chain).
Ok for trunk/4.9?
Thanks,
Igor
gcc/c-family/ChangeLog:
On 05/22/14 03:52, Zhenqiang Chen wrote:
On 21 May 2014 20:43, Steven Bosscher stevenb@gmail.com wrote:
On Wed, May 21, 2014 at 11:58 AM, Zhenqiang Chen wrote:
Hi,
The patch fixes the gcc.target/i386/pr49095.c FAIL in PR61225. The
test case tends to check a peephole2 optimization, which
On 04/08/14 10:23, Marek Polacek wrote:
On Fri, Mar 28, 2014 at 02:44:21PM +, Joseph S. Myers wrote:
On Fri, 28 Mar 2014, Marek Polacek wrote:
PR51088 contains some Really Bizzare code. We should tell users
not to do any shenanigans like that.
Ok for trunk?
I don't think a doc patch
On 07/15/14 05:58, Richard Biener wrote:
The following introduces a new param, max-combine-insns, to
be able to limit the work done at -Og to linear complexity
in the number of log-links (thus, two-insn combines). It
also records statistics of performed combines where for
fold-const.ii on
On 07/07/14 03:02, Richard Biener wrote:
On Mon, Jun 30, 2014 at 8:56 AM, Jeff Law l...@redhat.com wrote:
SSA_NAME_VALUE is, in effect, a chain of values. ie, it's possible for
SSA_NAME_VALUE of any given SSA_NAME to refer to another SSA_NAME.
Hmm, but it shouldn't as we walk in
On 06/22/14 12:20, Marc Glisse wrote:
Hello,
I followed the advice in this discussion:
https://gcc.gnu.org/ml/gcc-patches/2014-04/msg00269.html
and here is a new patch. I made an effort to isolate a path in at least
one subcase so it doesn't look too strange that the warning is in this
file.
On 06/19/14 03:44, Zhenqiang Chen wrote:
ChangeLog:
2014-06-17 Zhenqiang Chen zhenqiang.c...@linaro.org
* cprop.c (try_replace_reg): Check cost for constants.
diff --git a/gcc/cprop.c b/gcc/cprop.c
index aef3ee8..c9cf02a 100644
--- a/gcc/cprop.c
+++ b/gcc/cprop.c
@@ -733,6 +733,14
On 06/21/14 13:16, Marc Glisse wrote:
Hello,
this is another small simplification of RTL for vectors. Note that it
doesn't really solve the problem, because these simplifications are only
performed for single-use objects. If I start from vectors [a,b] and
[c,d] and concatenate them into
On 07/15/14 02:18, Marek Polacek wrote:
This is a revised patch that Peter recently submitted
https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01571.html, but
it was lacking a testcase and a better comment. This patch
adds a testcase (kind of a hacky one), the comment is hopefully
better too.
On 04/16/14 05:52, Ilya Enkovich wrote:
Hi,
This patch introduces target hooks to be used by Pointer Bounds Checker. Hooks
set is different from what was approved for 4.9 (and later reverted). I added
hooks to work with returned bounds and to prepare incoming bounds for vararg
functions.
On 07/07/14 14:14, Jan Hubicka wrote:
On 07/04/14 03:05, Jan Hubicka wrote:
Hi,
BLOCK_SUPERCONTEXT for normal blocks leads all the way to FUNCTOIN_DECL. This
is not the case of some
automatically generated functions, like one for cilk. I think it is bug. This
patch fixes cilk, I will
look
On 04/16/14 06:19, Ilya Enkovich wrote:
Hi,
This patch introduces built-in functions used by Pointer Bounds Checker. It is
mostly similar to what was reverted from 4.9, I just added types and attributes
to builtins. This patch also introduces pointer_bounds_type_node to be used in
built-in
73 matches
Mail list logo
