On Fri, 2011-10-21 at 21:25 +0200, Jakub Jelinek wrote:
> My guess would be
> http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=180194
> DEBUG_EXPR certainly shouldn't make it through into mem_loc_descriptor,
> var-tracking is supposed to resolve that.
>
> Jakub
You are right, the bug start
On 10/03/11 17:52, Paul Brook wrote:
> The C6XABI defined persoality routines ID 3 and 4 use a single 24-bit block
> word of unwinding data. Patch below makes sure this is preserved, rather
> than
> treating it as a set of unwinding opcode bytes.
>
> I seem to have lost this bit of code when I
On 10/03/11 17:57, Paul Brook wrote:
> 2011-10-03 Paul Brook
>
> * config/c6x/c6x.c (c6x_asm_emit_except_personality,
> c6x_asm_init_sections): New functions.
> (TARGET_ASM_EMIT_EXCEPT_PERSONALITY, TARGET_ASM_INIT_SECTIONS):
> Define.
This was also never applied. I've c
I think we're down to minor cosmetic issues:
On 10/21/2011 03:55 PM, Tom Tromey wrote:
There are a few spots like this that are missing a space before an open
paren.
+ if (DECL_LANGUAGE(decl) == lang_c)
Another one.
- if (warn_cxx0x_compat
- && C_RID_CODE (token
The calling convention with i?86 (32bits) is wrong for _ITM_free (and
_ITM_malloc/_ITM_calloc).
Here an example:
0x08049fd2 <+251>: mov-0x14(%ebp),%eax
0x08049fd5 <+254>: call 0x804b150 <_ITM_free(void*)>
Dump of assembler code for function _ITM_free(void*):
0x0804b150 <+0>:
On Oct 21, 2011, at 12:52 PM, Jason Merrill wrote:
> On 10/21/2011 03:11 PM, Marc Glisse wrote:
>> Note that at least clang now defines __cplusplus to its new C++11 value
>> (in experimental C++0X mode only). Apparently they switched around last
>> June and say they are not the only ones. So if you
In:
r37370 | bernds | 2000-11-10 09:10:29 -0800 (Fri, 10 Nov 2000) | 2 lines
Several fixes to make reload handle POST_MODIFY correctly.
We see:
-regno_clobbered_p (regno, insn, mode)
+regno_clobbered_p (regno, insn, mode, sets)
unsigned int regno;
rtx insn;
enum machine_mode m
I've committed the attached patch to address a
regression caused by my recent change to argument
checking in ISHFT[C]. Both my regression test
and Dominiq's regression test passed. Sorry
about the breakage.
2011-10-20 Steven G. Kargl
PR fortran/50821
* check.c (gfc_check_ish
Hello,
The following two patches fixes virtual locations handling to progress
toward bootstrapping the compiler with CFLAGS=-ftrack-macro-expansion
CXXFLAGS=-ftrack-macro-expansion
After these two patches I'll still need to update many c++ test cases
and probably exercise some dg-prune-fu to cope
Hello,
A virtual location can now "wrap" a reserved location. By reserved
location, I mean a location that is less than RESERVED_LOCATION_COUNT
(i.e UNKNOWN_LOCATION or BUILTINS_LOCATION).
When such a virtual location is passed to linemap_resolve_location,
that function returns the bare reserved
Hello,
I noticed that linemap_macro_map_lookup can yield the wrong map when
at the end of the lookup, we end up with a pair of maps whose indexes
are (mn,mx) with mx-mn == 1. In that case, if the map we want is mn,
we'd wrongly yield mx.
Fixed thus, bootstrapped and tested on x86_64-unknown-linu
This is the right patch that I bootstrapped and tested.
* line-map.c (linemap_macro_map_lookup): Make sure to always pick
the map with the highest MAP_START_LOCATION.
---
libcpp/line-map.c |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/libcpp/line
On Fri, Oct 21, 2011 at 12:52 PM, Paolo Carlini
wrote:
> Hi again,
>>>
>>> Another acceptable fix is to
>>> -- leave the current diagnostic as is if -fms-extensions
>>> -- suggest '()' is member function
>>> -- otherwise suggest '&'.
>>
>> Thanks for your help Gaby, in particular about the M
On Fri, Oct 21, 2011 at 5:22 PM, Mike Stump wrote:
> On Oct 21, 2011, at 12:52 PM, Jason Merrill wrote:
>> On 10/21/2011 03:11 PM, Marc Glisse wrote:
>>> Note that at least clang now defines __cplusplus to its new C++11 value
>>> (in experimental C++0X mode only). Apparently they switched around l
Committed. Thanks!
On 10/21/2011 06:22 PM, Mike Stump wrote:
Is there a plan on what the default language will be? C is stuck in 1980, and
will be forever. Personally, I'd rather have g++ move up language standards by
default, I'd rather make the move before 2023.
I think it makes sense to change the default
Marc Glisse writes:
>> _Z1aIFYviEEvPT_
>> void a(void (*)(int) extern "C")
Does g++ ever actually generate a symbol name like this? Is it worth
worrying about?
Personally if we are going to print this at all I think the extern "C"
should be in square brackets. E.g.,
void a(void (*)(int) [ex
From: Andi Kleen
This one place in ggc forgot to round page_entry->bytes to the
next page boundary, which lead to all the heuristics in freeing to
check for continuous memory failing. Round here too, like all other
allocators already do. The memory consumed should be the same
for MMAP because the
From: Andi Kleen
There were some concerns that the earlier munmap patch could lead
to address space being freed that cannot be allocated again
by ggc due to fragmentation. This patch adds a fragmentation
fallback to solve this: when a GGC_QUIRE_SIZE sized allocation fails,
try again with a page s
This version addresses all earlier review comments. Passes bootstrap
and testing on x86-64. Ok?
-Andi
From: Andi Kleen
Jakub had some concerns about the performance of page alignments in
ggc-page, which use a hardware division instructions currently.
This patch changes them all to use a new PAGE_ALIGN macro, which
exploits that pages are a power of two.
2011-10-21 Andi Kleen
* ggc-pa
From: Andi Kleen
This implements the freeing back of large chunks in the ggc madvise path
Richard Guenther asked for. This way on systems with limited
address space malloc() and other allocators still have
a chance to get back at some of the memory ggc freed. The
fragmented pages are still just
101 - 122 of 122 matches
Mail list logo
