On 06/29/2011 02:12 PM, Torvald Riegel wrote:
> Patch contains more clean-up: the trycommit, rollback and
> registerThrownObject functions in the ABI are unnecessary for how we
> support exception handling.
>
> Ok for branch?
>
Looks good.
r~
Hi!
As discussed in the PR and can be seen on the first testcase,
the removal of repeat field for ctors resulted in huge memory consumption
of the fortran FE on some real-world testcases (the first testcase
needs several GB of memory to compile).
This patch reintroduces the repeat field and handl
Hi!
Mark has recently changed dwarf2out to not emit anything into .debug_abbrev
section if there are no abbreviations, but as Rainer has reported, some
vendor tools are upset about it. We were still emitting the .debug_abbrev
section, just with zero size, in order to emit the .Ldebug_abbrev0
symb
In preparation for the changes required to support shrink-wrapping,
it makes things Much Easier if we no longer have to handle seeing
new unwind states being introduced during pass_final, while emitting
the actual assembly. Thus we want to convert everything that used
the text-based interfaces to
Also pull out value insertion into a subroutine.
---
gcc/dwarf2out.c | 115 +++
1 files changed, 65 insertions(+), 50 deletions(-)
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index 3d63d7b..3ecdd94 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwar
---
gcc/dwarf2out.c | 18 ++
1 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index 3ecdd94..6fad7e9 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwarf2out.c
@@ -1982,6 +1982,7 @@ dwarf2out_frame_debug_cfa_offset (rtx set, const char
*l
---
gcc/config/ia64/ia64.c | 35 ++-
1 files changed, 2 insertions(+), 33 deletions(-)
diff --git a/gcc/config/ia64/ia64.c b/gcc/config/ia64/ia64.c
index b37919c..bdabe82 100644
--- a/gcc/config/ia64/ia64.c
+++ b/gcc/config/ia64/ia64.c
@@ -9620,29 +9620,6 @@ stat
When actually emitting dwarf2, this now produces proper results.
When emitting ia64 unwind info, this removes a hard-coded assumption.
---
gcc/config/ia64/ia64.c | 17 ++---
1 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/gcc/config/ia64/ia64.c b/gcc/config/ia64/ia64.
This defines nothing that we can't deduce already,
so remove it.
---
gcc/config/ia64/ia64.c | 24
1 files changed, 0 insertions(+), 24 deletions(-)
diff --git a/gcc/config/ia64/ia64.c b/gcc/config/ia64/ia64.c
index 0a6f2e6..bb3fc4d 100644
--- a/gcc/config/ia64/ia64.c
++
---
gcc/config/ia64/ia64.c |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/gcc/config/ia64/ia64.c b/gcc/config/ia64/ia64.c
index c06903d..0a6f2e6 100644
--- a/gcc/config/ia64/ia64.c
+++ b/gcc/config/ia64/ia64.c
@@ -3249,7 +3249,14 @@ ia64_expand_prologue (void)
From: Richard Henderson
This requires a bit of extra preparation in arm_unwind_emit, in
order to handle the change for ARM unwinding.
---
gcc/config/arm/arm.c | 114 ++--
gcc/config/arm/arm.md |2 -
2 files changed, 62 insertions(+), 54 deletions
While it could be possible to output_set_got such that we can
individually annotate the instructions, it's simpler to simply
admit that all processors currently being manufactured do want
deep branch prediction. At which point all of the complication
simply goes away.
---
gcc/config/i386/i386.c |
Use an empty REG_FRAME_RELATED_EXPR instead.
---
gcc/config/ia64/ia64.c | 23 +--
1 files changed, 9 insertions(+), 14 deletions(-)
diff --git a/gcc/config/ia64/ia64.c b/gcc/config/ia64/ia64.c
index bdabe82..2ebb225 100644
--- a/gcc/config/ia64/ia64.c
+++ b/gcc/config/ia64/i
The dwarf2out_cfi_label function is privatized, the
dwarf2out_def_cfa function is merged into its last user.
The others really are unused.
---
gcc/dwarf2out.c | 65 ++-
gcc/tree.h | 27 --
2 files changed, 7 insertion
Not that there's much rtl to emit, since the CALL instruction
interpreting the procedure entry mask does almost all the work.
However, it means we're no longer emitting dwarf2 via the
text-based entry points.
---
gcc/config/vax/vax-protos.h |1 +
gcc/config/vax/vax.c| 86
---
gcc/dwarf2out.c | 37 +
gcc/final.c |4 +++-
gcc/reg-notes.def | 11 +--
3 files changed, 37 insertions(+), 15 deletions(-)
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index 6fad7e9..904 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/
As reported, this still wasn't working properly for an array of scalar
type. We still need to handle {} in the case of iterating over all the
elements.
While I was poking at related code, I fixed a wrong-code bug with the
ancient and permerrored new T[n](init) extension because it was easy.
OK.
Jason
On 06/29/2011 05:07 PM, Jan Kratochvil wrote:
On Wed, 29 Jun 2011 22:56:26 +0200, Jason Merrill wrote:
On 06/29/2011 04:00 PM, Jan Kratochvil wrote:
On Mon, 27 Jun 2011 20:00:24 +0200, Jason Merrill wrote:
# decltype/fn call test
--format=gnu-v3
_Z4add3IidEDTclL_Z1gEfp_fp0_EET_T0_
-dec
On Jun 29, 2011, at 10:47 AM, Iain Sandoe wrote:
> The bug arises because of the use, by the ObjC FE, of two old target macros
> that emit efficient representations of class definitions and references.
> Mike has already given this a 'seems reasonable' in the PR thread, however, I
> need an appr
On the powerpc, switch statements can be expensive, and we would like to be
able to tune the threshold of when the compiler generates if statements
vs. using a table jump operation (and different processors within the powerpc
have different limits). This patch adds a powerpc tuning option to contr
On Jun 29, 2011, at 1:37 AM, Iain Sandoe wrote:
> On 28 Jun 2011, at 18:01, Iain Sandoe wrote:
>> On 28 Jun 2011, at 17:47, Rainer Orth wrote:
>>> objc.dg/torture/forward-1.m now seems to XPASS everywhere, creating an
>>> annoying amount of testsuite noise. Dominique provided the following
>>> pat
On 05/25/2011 02:10 PM, Torvald Riegel wrote:
> Here's the beginning of a refactoring aimed at being able to merge more
> TM algorithms later on.
>
> Patch 1: Just a straightfoward rename to make it clear that we're
> dispatching on the level of ABI calls, not internals.
Ok, I guess. I don't thi
On Wed, Jun 29, 2011 at 11:49 PM, Richard Henderson wrote:
> --- a/gcc/config/vax/vax.c
> +++ b/gcc/config/vax/vax.c
> @@ -70,9 +69,6 @@ static int vax_return_pops_args (tree, tree, int);
> #undef TARGET_ASM_ALIGNED_HI_OP
> #define TARGET_ASM_ALIGNED_HI_OP "\t.word\t"
>
> -#undef TARGET_ASM_FUNC
On 06/29/2011 04:01 PM, Steven Bosscher wrote:
> Can you please also update http://gcc.gnu.org/backends.html? I think
> VAX should have a 'g' after you commit this patch.
Sure.
> How many TARGET_ASM_FUNCTION_{PRO,EPI}LOGUE targets are left anyway?
It's difficult to tell at a glance, because quit
On 06/29/2011 12:35 PM, Sebastian Pop wrote:
2011-06-29 Sebastian Pop
* graphite-clast-to-gimple.c (precision_for_value): Removed.
(precision_for_interval): Removed.
(gcc_type_for_interval): Use mpz_sizeinbase.
-/* Return a type that could represent the integer value VAL
On 06/29/2011 12:35 PM, Sebastian Pop wrote:
Hi,
the following patch set fixes PR47654:
Correct typo.
Correct computation of max.
Fix PR47654: Loop blocking should strip-mine at least two loops.
Those three look OK.
Cheers
Tobi
On 06/29/2011 12:35 PM, Sebastian Pop wrote:
2011-06-29 Sebastian Pop
* graphite-clast-to-gimple.c (compute_bounds_for_level): Removed.
(compute_type_for_level): Removed.
(clast_get_body_of_loop): Removed.
(gcc_type_for_iv_of_clast_loop): Removed.
(graphi
On 06/29/2011 12:35 PM, Sebastian Pop wrote:
2011-06-29 Sebastian Pop
PR tree-optimization/47654
* graphite-clast-to-gimple.c (gcc_type_for_value): Removed.
(gcc_type_for_clast_term): Removed.
(gcc_type_for_clast_red): Removed.
(gcc_type_for_clast_bin): R
Some comments were wrong.
In particular, the strings read from the stream are placed in a data table, and
thus the strings returned DO NOT need to be freed by the caller, they belong to
the stream who handles them itself.
Also lto_output_string_with_length does handle NULL strings, removed the
On Fri, Jun 24, 2011 at 11:51 PM, Thomas Klein wrote:
>
> Hi
>
> This is a ping of (http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01226.html).
> Repeating my request.
>
> I would like to have a stack check for threads with small amount of stack
> space per thread.
> (I'm using a ARM Cortex-M3 micr
Fix dg-pph.exp to execute both normal and pph executable tests and to avoid
false new/disappeared reports.
Break x1dynarray1 into three levels of tests.
Remove ICE failure in x1dynarray1. We now get bogus warnings, but we cannot
seem to mark them with dg-bogus without also getting xfails.
Inde
101 - 132 of 132 matches
Mail list logo
