This patch removes the checks on mode duplication for the configuration form of
the pragma to keep the behavior in line with other configuration pragmas.
-- Source --
-- unit_spark_mode.ads
pragma SPARK_Mode (Auto);
pragma SPARK_Mode (On);
package Unit_SPARK_Mode is
e
This patch fixes a compiler bug that caused the master of incomplete views to
be missing, which caused a crash when allocating an object of the type, if the
full type contains tasks.
The following example must compile quietly:
gcc -c -gnat05 lim_view_example.adb lim_view_example-child.adb
limite
This patch modifies the approach taken by the compiler to save/restore
the scope stack. The save routine now returns the list of entitites
which have been temporarily removed from visibility, and that list
is passed to the restore routine to restore their visibility.
This approach consumes more me
This patch treats the GNAT-specific 'Img attribute as a callable entity which
therefore can be renamed as a function. The prefix of the attribute reference
is an object rather than a subtype, and it is not evaluated at the point of the
renaming declaration.
Executing the following :
gnatmake
This patch prevents the generation of deallocation code in order to clean up an
allocated object when it fails an accessibility check when profile Ravenscar is
in effect.
Tested on x86_64-pc-linux-gnu, committed on trunk
2013-07-08 Hristian Kirtchev
* exp_ch4.adb (Apply_Accessibility_
This patch corrects the expansion of if expressions to generate finalization
code for transient controlled function results that appear in the "then" or
"else" alternatives. The transient objects are now properly finalized after the
if expression is evaluated.
-- Source --
---
> 2013-07-05 Jakub Jelinek
>
> PR rtl-optimization/57829
> * simplify-rtx.c (simplify_binary_operation_1) : Ensure that
> mask bits outside of mode are just sign-extension from mode to HWI.
>
> * gcc.c-torture/execute/pr57829.c: New test.
OK everywhere, thanks.
--
Er
The restriction SPARK is replaced by SPARK_05 (since this restriction
is specifically about violating rules of SPARK 2005). The restriction
SPARK is retained for backward compatibility, but will generate a
warning that it is obsolescent if it is used.
The following program compiles giving the expe
This is a followup patch that ensures that the hides directives
work with both SPARK_05 and the obsolete synonym SPARK (the latter
was broken by the previous patch).
The following programs compile as shown:
1. pragma Restrictions (SPARK);
|
>>> warning: r
This patch allows pragma Partition_Elaboration_Policy to be recognized
in system.ads in a manner analogous to the other Policy pragmas.
Given a version of System to which the line
pragma Partition_Elaboration_Policy (Sequential);
has been added, compilation of the following program
with switch -
This patch relaxes the restriction that ! and !! must appear at the end
of a compiler message. They can now appear anywhere. This is only an
internal implementation change with no functional effect, so no test.
Tested on x86_64-pc-linux-gnu, committed on trunk
2013-07-08 Robert Dewar
Two anonymous_access_to_subprograsm types are type conformant if the designated
type of one is protected and the other is not. Convention of the designated
types only matters when checking subtype conformance. Previous to this patch,
the compiler failed to recognize that the following declarations
This attribute allows compile time testing of restrictions that
are currently in effect. It is primarily intended for specializing
code in the run-time based on restrictions that are active (e.g.
don't need to save fpt registers if restriction No_Floating_Point
is known to be in effect), but can be
This patch modifies the processing of pre- and postconditions that apply to
a body that acts as a spec to provide a uniform interface for compiler client
tools. The patch also augments routine Get_Pragma to retrieve delayed pragmas
stored in subprogram contracts.
Tested on x86_64-pc-linux-gnu, com
> So, my first approach was trying to simplify that, because nonzero_bits
> on the subreg operand say that no bits outside of QImode may be non-zero,
> both the zero_extend and subreg can be dropped. That is the simplify-rtx.c
> change. Then I've figured out that combine.c doesn't actually attemp
As spotted by Po-Chun Chang, we can add a break in the loop dealing with the
multi-hard registers case in the REG_DEAD case of distribute_notes.
Bootstrapped/regtested on x86_64-suse-linux, applied on the mainline.
2013-07-08 Po-Chun Chang
PR rtl-optimization/57786
* combine
This is a regression from the 4.6.x series. Tested on x86_64-suse-linux,
applied on all active branches as obvious.
2013-07-08 Eric Botcazou
* Makefile.in (tree-ssa-reassoc.o): Add dependency on $(PARAMS_H).
--
Eric BotcazouIndex: Makefile.in
=
Hi,
the attached patch adds F0_REGNUM ... F15_REGNUM and uses these
throughout the s390.c file. The FPR numbering in the s390 backend is
not obvious and this hopefully makes it easier to get right for me.
Committed to mainline after regtesting on s390 and s390x.
Bye,
-Andreas-
2013-07-08 And
Ping^2~
Thanks,
Yufeng
On 07/02/13 23:44, Yufeng Zhang wrote:
Ping~
Can I get an OK please if there is no objection?
Regards,
Yufeng
On 06/26/13 23:39, Yufeng Zhang wrote:
This patch updates assign_parm_find_data_types to assign passed_mode and
nominal_mode with the mode of the built point
Hi,
This patch consists of the nds32 specific settings for configure process.
Because there are two kinds of libgcc support (newlib/mculib) in nds32 target,
we add --with-nds32-lib option in gcc/config.gcc and libgcc/config.host.
The nds32*|nds32le*|nds32be* recognition in config.sub has already
Hi,
This patch consists of testsuite changes, including skip cases,
expected fail cases, and __nds32__ specific cases.
In additon, we also add checking in lib/target-supports.exp
because profiling is not available for nds32*-*-elf target.
gcc/testsuite/
2013-07-08 Chung-Ju Wu
Shiv
Hello!
> the attached patch adds F0_REGNUM ... F15_REGNUM and uses these
> throughout the s390.c file. The FPR numbering in the s390 backend is
> not obvious and this hopefully makes it easier to get right for me.
Index: gcc/config/s390/s390.h
Hi,
This patch consists of the nds32 specific content in documentation,
including options, constraints, --with-nds32-lib configure option,
and attributes for nds32 target.
gcc/
2013-07-08 Chung-Ju Wu
Shiva Chen
* doc/invoke.texi (NDS32 options): Document nds32 specific
Hi,
This patch consists of webpage changes for describing a new 'nds32'
target port and related information.
The following is a brief overview of changes:
htdocs/
2013-07-08 Chung-Ju Wu
Shiva Chen
* backends.html: Add architecture characteristic key for nds32 target.
Hi, GCC Steering Committee, reviewers, and developers,
On behalf of Andes Technology Corp., we are submitting a new port 'nds32'
for GCC contribution. In this contribution, we use the design and strategy
as modern as possible, such as having LRA enabled and taking soft-fp as
our software floating
I've fixed the issue with the warnings and have now comitted the patch with a
corrected
ChangeLog entry as revision 200783
Graham
Hi Bruce,
That was my original letter:
>Hi,
>
>Could you please take a look at the attached fixinclude patch
>that addresses the problem:
>
>" We have test fail for gcc.dg/cpp/trad/include.c on Android. The
>reason for that is that
>-ftraditional-cpp is not expected to work on Android due to vari
Manfred Schwarb wrote:
dg-compile, dg!final and missing parens protection.
Thanks for the patch! I committed it as Rev. 200784. (The dg!final was a
left-over from some testing; I should switch to something more visible
for commenting out those.)
Tobias
Index: defined_assignment_7.f90
Tobias Burnus wrote:
Built and regtested on x86-64-gnu-linux.
OK for the trunk?
Committed as obvious (Rev. 200785) with the test-case's grammar in the
comment fixed. (Thanks Dominique for the review.)
Tobias
*Ping*
>>> Another bunch of tests that fails with -fpic.
>>>
>>> from here: http://gcc.gnu.org/ml/gcc-patches/2013-01/msg00539.html
>>> "Since -fpic option is turned on by default in Android we have certain test
>>> fails. The reason for that is that those tests rely on the
>>> availability of fun
On Mon, Jul 08, 2013 at 01:03:38PM +0200, Uros Bizjak wrote:
> Hello!
>
> > the attached patch adds F0_REGNUM ... F15_REGNUM and uses these
> > throughout the s390.c file. The FPR numbering in the s390 backend is
> > not obvious and this hopefully makes it easier to get right for me.
>
> Index:
Not yet. Why is this not a problem in the LT / UNLT case ?
The testcase is not correctly written.
@@ -0,0 +1,16 @@
+/* { dg-do compile } */
+/* { dg-options "-O3 -mfpu=neon -mcpu=cortex-a9 -mthumb
-mfloat-abi=hard -S" } */
dg-add-options arm_neon ?
dg-require-effective-target arm_neon ?
reg
The __cxa_atexit support is a reqirement for destructor registration of
thread-local objects.
For *-*-elf it is already enabled by default. See comment line 810 in
"gcc/config.gcc".
Define TARGET_LIBGCC_SDATA_SECTION on PowerPC for RTEMS to ".sdata" to
place the __dso_handle. The __dso_handle i
On Sun, Jul 07, 2013 at 07:54:34PM +0200, Georg-Johann Lay wrote:
> Ondrej Bilka schrieb:
>
> >http://kam.mff.cuni.cz/~ondra/gcc_misspell.patch
>
> This is wrong:
>
> @@ -10834,7 +10834,7 @@ avr_convert_to_type (tree type, tree expr)
> XOP[2] # Bytes to copy
>
> Return TRUE if the exp
On 07/04/2013 03:06 AM, Kai Tietz wrote:
> Hi,
>
> here is the adjusted patch for this PR.
>
> 2013-07-04 Kai Tietz
>
> PR target/56892
> * config/i386/i386.c (TARGET_FUNCTION_ATTRIBUTE_INLINABLE_P): Define as
> hook_bool_const_tree_true.
Ok.
r~
Am 03.07.2013 14:05, schrieb Tobias Burnus:
Thanks goes to Dominique for debugging the issue!
Build and regtested on x86-64-gnu-linux.
OK for the trunk? I think one should also backport it to 4.7/4.8.
(Folding - and hence the bug - exist since GCC 4.5.)
For the trunk, committed as Rev. 200786
On Sun, Jul 07, 2013 at 09:57:05PM +0200, Oleg Endo wrote:
> On Sun, 2013-07-07 at 19:54 +0200, Georg-Johann Lay wrote:
> > Ondrej Bilka schrieb:
> >
> > > http://kam.mff.cuni.cz/~ondra/gcc_misspell.patch
> >
I fixed most comments, put it here so you can diff these two files.
http://kam.mff.cuni.c
Hi Richard,
The problem was with adjusting to be more expansive the load imm + mul sequence
and
the shift + add sequence were the smake cost when optimizing for size so the
code in expmed.c
choose the MUL.
I also considered this version also I couldn't decide which was better just
went with
Hi,
On Mon, Jul 8, 2013 at 5:05 AM, Alexander Ivchenko wrote:
> Hi Bruce,
>
> That was my original letter:
>>Hi,
>>
>>Could you please take a look at the attached fixinclude patch
>>that addresses the problem:
>>
>>" We have test fail for gcc.dg/cpp/trad/include.c on Android. The
>>reason for th
On 8 July 2013 20:57, Ramana Radhakrishnan wrote:
> Not yet. Why is this not a problem in the LT / UNLT case ?
>From the context, after the first switch, only GE/LE/EQ might have
operands[5] which is not REG (CONST0_RTX). For others including
LT/UNLT, operands[5] should be REG.
if (!REG_P (opera
On 07/07/2013 08:02 AM, Marc Glisse wrote:
+ error_at (loc, "could not find an integer type "
+ "of the same size as %qT", ctype);
Why try to find a result element type the same size as the condition
element type? For scalars the condition is
On 07/07/2013 12:32 PM, Paolo Carlini wrote:
-auto int; // { dg-error "multiple types|can only be specified for variables" }
+auto int; // { dg-error "multiple types|does not declare anything" }
This is a regression. Please limit the change to when the type is a class.
Jason
Now committed as obvious (Rev. 200790).
Tobias
Tobias Burnus wrote:
Tobias Burnus wrote:
Actually, I wonder whether the following (untested) shouldn't be
sufficient:
Seems to work.
Build and regtested on x86-64-gnu-linux.
OK for the trunk?
Tobias
On 07/07/2013 11:54 AM, Marc Glisse wrote:
it turns out there wasn't much missing here. I got side-tracked because
fold_unary_loc doesn't call fold_indirect_ref_1, and fold_indirect_ref_1
has a too strict comparison type == TREE_TYPE (optype) (should compare
TYPE_MAIN_VARIANT instead?), but none
** PING **
On July 01, Tobias Burnus wrote:
The following patches are pending to be reviewed:
* http://gcc.gnu.org/ml/fortran/2013-06/msg00142.html
* http://gcc.gnu.org/ml/fortran/2013-06/msg00132.html
* http://gcc.gnu.org/ml/fortran/2013-06/msg00137.html
It would help me tremendously if my l
On Mon, Jul 08, 2013 at 04:32:13PM +0100, Zhenqiang Chen wrote:
> On 8 July 2013 20:57, Ramana Radhakrishnan wrote:
> > Not yet. Why is this not a problem in the LT / UNLT case ?
>
> From the context, after the first switch, only GE/LE/EQ might have
> operands[5] which is not REG (CONST0_RTX). Fo
OK.
Jason
On 06/30/2013 04:21 AM, Lubos Lunak wrote:
Are you sure this should be covered by -Wunused-but-set-variable rather than
plain -Wunused-variable? While strictly technically speaking the variable is
set by the ctor, it's conceptually confusing (is "string s;" really set from
the developer's point o
Hello,
These passes are implementing type-demotion (type sinking into statements) for
some gimple statements. I limitted inital implementation to the set of
multiply, addition, substraction, and binary-and/or/xor. Additional this pass
adds some rules to sink type-cast sequences - eg. (int) (s
Hi,
>On 07/07/2013 12:32 PM, Paolo Carlini wrote:
>> -auto int; // { dg-error "multiple types|can only be specified for
>variables" }
>> +auto int; // { dg-error "multiple types|does not declare anything" }
>
>This is a regression. Please limit the change to when the type is a
>class.
Ah I see
Please add support for unwinding through signal handler for GNU/kFreeBSD.
The attached patch is tested on GNU/kFreeBSD, both 32-bit and 64-bit.
The i386/freebsd-unwind.h is probably also suitable for plain FreeBSD.
As suggested in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57851
I am posting it
On 07/04/2013 11:30 AM, Andrew Sutton wrote:
I ran through every test in the is_convertible unit test with
__is_convertible. There are 2 cases it doesn't address. The conversion
of a function type (int()) to its reference type (int(&)()),
I looked into this a bit more; it seemed odd to consider
On 07/08/2013 01:49 PM, Paolo Carlini wrote:
Ah I see. I take your indication as meaning class *or enum*
Yes.
Jason
2013/7/8 Bruce Korb :
> Hi,
>
> On Mon, Jul 8, 2013 at 5:05 AM, Alexander Ivchenko wrote:
>> Hi Bruce,
>>
>> That was my original letter:
>>>Hi,
>>>
>>>Could you please take a look at the attached fixinclude patch
>>>that addresses the problem:
>>>
>>>" We have test fail for gcc.dg/cpp/trad/inclu
On 07/08/2013 08:32 AM, Zhenqiang Chen wrote:
> On 8 July 2013 20:57, Ramana Radhakrishnan wrote:
>> Not yet. Why is this not a problem in the LT / UNLT case ?
>
>>From the context, after the first switch, only GE/LE/EQ might have
> operands[5] which is not REG (CONST0_RTX). For others including
On Mon, Jul 08, 2013 at 11:44:04AM -0700, Janis Johnson wrote:
> >> @@ -0,0 +1,16 @@
> >> +/* { dg-do compile } */
> >> +/* { dg-options "-O3 -mfpu=neon -mcpu=cortex-a9 -mthumb
> >> -mfloat-abi=hard -S" } */
> >>
> >> dg-add-options arm_neon ?
> >> dg-require-effective-target arm_neon ?
> >
> > I
Committed as obvious (Rev. 200794) after regtesting on x86-64-gnu-linux.
Without the patch, the following bogus error was shown for -std=f2003/f2008:
call C_F_POINTER(cptr, str, [255])
1
Error: TS 29113: Noninteroperable array FPTR at (1) to C_F_POINTER: Only
expl
On Mon, 2013-07-08 at 16:12 +0200, Ondřej Bílka wrote:
> On Sun, Jul 07, 2013 at 09:57:05PM +0200, Oleg Endo wrote:
> > On Sun, 2013-07-07 at 19:54 +0200, Georg-Johann Lay wrote:
> > > Ondrej Bilka schrieb:
> > >
> > > > http://kam.mff.cuni.cz/~ondra/gcc_misspell.patch
> > >
> I fixed most comment
Tests gcc.target/powerpc/sd-vsx.c and sd-pwr6.c assume that decimal
floating point is supported on the target, but this is not true for
powerpc-none-eabi. This obvious patch skips the test if dfp is
not supported; checked in for mainline.
Janis
2013-07-08 Janis Johnson
* gcc.target/po
Test gcc.target/powerpc/pr47197.c passes "-maltivec" without first
checking that the option is allowed on the target, which is not the case
for powerpc-eabispe. This obvious patch fixes the problem by requiring
powerpc_altivec_ok; checked in on mainline and the 4.8 branch.
Janis
2013-07-08 Janis
The error message checked in gcc.target/powerpc/ppc-spe64-1.c changed
for GCC 4.8. This obvious patch fixes the test to expecte the current
message; checked in for mainline and the 4.8 branch.
Janis
2013-07-08 Janis Johnson
* gcc.target/powerpc/ppc-spe64-1.c: Update expected error mes
Tests gcc.target/powerpc/20020118-1.c and
gcc.c-torture/execute/nest-align-1.c sometimes fail because they expect
a stack alignment that is greater than that required for powerpc-eabi.
This patch forces stack alignment to 128 bits by passing "-mno-eabi".
Is this OK for mainline and the 4.8 branch,
Test gcc.target/powerpc-tfmode_off.c fails for powerpc-eabi* targets,
which do not support TFmode. This patch skips the test for
powerpc-*-eabi*.
OK for mainline and the 4.8 branch?
Janis
2013-07-08 Janis Johnson
* gcc.target/powerpc/tfmode_off.c: Skip for EABI targets.
Index: gcc.t
On Jul 8, 2013, at 12:47 PM, Janis Johnson wrote:
> Tests gcc.target/powerpc/20020118-1.c and
> gcc.c-torture/execute/nest-align-1.c sometimes fail because they expect
> a stack alignment that is greater than that required for powerpc-eabi.
> This patch forces stack alignment to 128 bits by passin
On Jul 8, 2013, at 12:48 PM, Janis Johnson wrote:
> Test gcc.target/powerpc-tfmode_off.c fails for powerpc-eabi* targets,
> which do not support TFmode. This patch skips the test for
> powerpc-*-eabi*.
>
> OK for mainline and the 4.8 branch?
Ok, but could you please add a comment why it is skip
On Mon, Jul 8, 2013 at 11:42 AM, Alexander Ivchenko wrote:
>> It sounds like it is better to fix the system headers instead. Via a
>> fixincludes for older headers and have the android folks fix them for
>> newer releases.
>
> Would that count for verifing? :)
:) Indeed. I confess I didn't look
On Mon, 8 Jul 2013, Ondrej Bilka wrote:
> Hi now, when I have infrastructure ready I made another patch (its 500kb so
> link not to overload list). It is here;
> http://kam.mff.cuni.cz/~ondra/gcc_misspell_conventions.patch
>
> It uses dictionary made by reading gcc conventions.
> http://gcc.gnu.
On Mon, 8 Jul 2013, Kai Tietz wrote:
These passes are implementing type-demotion (type sinking into
statements) for some gimple statements. I limitted inital
implementation to the set of multiply, addition, substraction, and
binary-and/or/xor. Additional this pass adds some rules to sink
ty
This is fine, thanks.
Ben
signature.asc
Description: Digital signature
On Mon, 8 Jul 2013, Jason Merrill wrote:
On 07/07/2013 08:02 AM, Marc Glisse wrote:
+ error_at (loc, "could not find an integer type "
+ "of the same size as %qT", ctype);
Now that I think of it, if a?b:c fails for this reason, it would also
On Thu, 28 Mar 2013, Alexander Ivchenko wrote:
> Hi,
>
> 4.8 is now branched, lets come back to the discussion that we had
> before. I updated the patch a little
> bit since we now have linux-protos.h and linux-android.c files.
>
> I tried to preserve the avaiability of c99 for all targets, but
Hello,
> "Jürgen Urban" writes:
> >> "Jürgen Urban" writes:
> >> > I used the SPU code in GCC as example for creating an
> >> > r5900_single_format structure. The patch is attached to the e-mail. I
> >> > want to submit this patch.
> >>
> >> Thanks. Are there any real differences though? E.g. i
On 07/08/2013 08:01 PM, Jason Merrill wrote:
On 07/08/2013 01:49 PM, Paolo Carlini wrote:
Ah I see. I take your indication as meaning class *or enum*
Yes.
Thanks. Thus, as agreed, I tested the below. Ok?
Paolo.
///
Index: cp/parser.c
==
In lookup_stmt_eh_lp, negative return value indicates a MUST_NOT_THROW
region index. In this case, we should *not* add an EH edge during VPT.
Bootstrapped and passed regression test.
OK for trunk?
Thanks,
Dehao
gcc/ChangeLog:
2013-07-08 Dehao Chen (de...@google.com)
* value-prof.c (g
On Mon, 1 Jul 2013 14:55:35 -0600
Ryan Hill wrote:
Ping.
http://gcc.gnu.org/ml/gcc-patches/2013-07/msg00032.html
> libatomic is currently unconditionally built with -Werror. This patch adds
> --enable-werror to control it (enabled by default). Bootstrapped and tested
> on x86_64, and inspecte
On Mon, 1 Jul 2013 14:56:01 -0600
Ryan Hill wrote:
Ping.
http://gcc.gnu.org/ml/gcc-patches/2013-07/msg00033.html
> libitm is currently unconditionally built with -Werror. This patch adds
> --enable-werror to control it (enabled by default). Bootstrapped and tested
> on x86_64, and inspected
Well, this has taken a lot of revisions to get right. In this testcase, in
MakeHandler(Wrapper >);
we need to check the access for Append in the context of the expression.
But we don't know which Append we want until we do template argument
deduction. In other testcases, we need to chec
On 07/08/2013 07:32 PM, Paolo Carlini wrote:
+ && (CLASS_TYPE_P (decl_specifiers.type)
+ || TREE_CODE (decl_specifiers.type) == ENUMERAL_TYPE))
You can use OVERLOAD_TYPE_P here if you want. OK either way.
Jason
On 07/08/2013 05:28 PM, Marc Glisse wrote:
Perhaps the most conservative rule would be to only accept the case
where the sizes match and reject the others for now, so whatever is
decided later for other cases is unlikely to require a breaking change.
Though I would like the general case to be acc
Lawrence's overhaul of the debug() functions changed the behavior of the
pvt macro in gdbinit.in. Previously it used print_node to dump each of
the elements of the vector, but after the change it uses debug, which
both prints less information by default and fails to handle many C++
tree nodes.
Is it possible to add a test case?
David
On Mon, Jul 8, 2013 at 5:55 PM, Dehao Chen wrote:
> In lookup_stmt_eh_lp, negative return value indicates a MUST_NOT_THROW
> region index. In this case, we should *not* add an EH edge during VPT.
>
> Bootstrapped and passed regression test.
>
> OK for tru
Hi Tobias,
** PING **
On July 01, Tobias Burnus wrote:
The following patches are pending to be reviewed:
* http://gcc.gnu.org/ml/fortran/2013-06/msg00142.html
OK if nobody else objects within 24 h.
* http://gcc.gnu.org/ml/fortran/2013-06/msg00132.html
This one is OK.
* http://gcc.gnu.
This PR isn't really a C++ issue; it affects C as well, and presumably
all other languages. A comment a few lines down says
/* Avoid returning a negative bitpos as this may wreak havoc later. */
but we were failing to avoid that in this case.
Tested x86_64-pc-linux-gnu. OK for trunk/4.8?
co
--
Paul Pluzhnikov
84 matches
Mail list logo