DJ Delorie writes:
> The m32c-elf with -mcpu=m32c has a word-aligned stack and uses pushes
> for arguments (i.e. not accumulate_outgoing_args). In this test case,
> one of the arguments is memcpy'd into place, and an assert fails:
m68k has a similar configuration, and I've never seen this asser
Hi,
we set up a new GCC mirror for the community.
URL: http://mirrors.concertpass.com/gcc/
Organization/Contact: ConcertPass (ad...@mirrors.concertpass.com)
Location: United States, Michigan
Please, add it to your mirror list page.
Thanks
Hi,
record_component_aliases only handle fields of a record type, and
would ignore the base of this record if the base has no field
declaration.
Is this a bug or on purpose?
Thanks.
--
Lin Zuojian
On Fri, Aug 29, 2014 at 11:50 AM, lin zuojian wrote:
> Hi,
> record_component_aliases only handle fields of a record type, and
> would ignore the base of this record if the base has no field
> declaration.
> Is this a bug or on purpose?
It's on purpose as you can't "access" that b
Thanks Richard.
---
Lin Zuojian
On 08/29/2014 12:04 AM, Thomas Preud'homme wrote:
>> So are you saying you are stuck with printf_float?
>
> It's not printf_float but _printf_float. I was told double underscore is only
> necessary with old toolchain as they might add a leading underscore. So
> _printf_float should not pose any k
Hello All,
[[I know that this is a sensitive issue, and I also know that I am in
the minority believing that a garbage collection is useful inside the
GCC compiler]]
How should plugins deal with data that is explicitly gcc_free-d outside
of ggc_collect?
In particular, plugins are apparently allo
On 08/29/2014 09:51 AM, Grissiom wrote:
>> Yes, it does. The namespace reserved for the implementation is _[_A-Z].
>> The namespace _[a-z] is still available for the user. Which means the
>> user can declare their own _printf_float, and WE (as the implementation)
>> MUST NOT INTERFERE with it.
On 08/29/2014 10:03 AM, Eric Blake wrote:
> On 08/29/2014 09:51 AM, Grissiom wrote:
>>> Yes, it does. The namespace reserved for the implementation is _[_A-Z].
>>> The namespace _[a-z] is still available for the user. Which means the
>>> user can declare their own _printf_float, and WE (as the i
On August 29, 2014 5:29:43 PM CEST, Basile Starynkevitch
wrote:
>Hello All,
>
>[[I know that this is a sensitive issue, and I also know that I am in
>the minority believing that a garbage collection is useful inside the
>GCC compiler]]
>
>How should plugins deal with data that is explicitly gcc_f
On Fri, 2014-08-29 at 19:58 +0200, Richard Biener wrote:
>
> You are in the same situation as any other pass would be. Don't hang on
> things that can get stale.
>
> There is no point in keeping a pointer to a deleted edge.
Yes there is. The use case is to make some statistics on edges and to
On 08/28/14 12:58, Uros Bizjak wrote:
On Fri, Aug 22, 2014 at 2:21 PM, Ilya Enkovich wrote:
On Cauldron 2014 we had a couple of talks about relaxation of ebx usage in
32bit PIC mode. It was decided that the best approach would be to not fix ebx
register, use speudo register for GOT base add
On 08/28/14 07:01, Uros Bizjak wrote:
On Fri, Aug 22, 2014 at 2:21 PM, Ilya Enkovich wrote:
Hi,
On Cauldron 2014 we had a couple of talks about relaxation of ebx usage in
32bit PIC mode. It was decided that the best approach would be to not fix ebx
register, use speudo register for GOT base
On 08/28/14 02:37, Ilya Enkovich wrote:
2014-08-28 1:39 GMT+04:00 Jeff Law :
On 08/26/14 15:42, Ilya Enkovich wrote:
diff --git a/gcc/calls.c b/gcc/calls.c
index 4285ec1..85dae6b 100644
--- a/gcc/calls.c
+++ b/gcc/calls.c
@@ -1122,6 +1122,14 @@ initialize_argument_information (int num_actuals
On Fri, Aug 29, 2014 at 07:58:14PM +0200, Richard Biener wrote:
> On August 29, 2014 5:29:43 PM CEST, Basile Starynkevitch
> wrote:
> >Hello All,
> >
> >[[I know that this is a sensitive issue, and I also know that I am in
> >the minority believing that a garbage collection is useful inside the
>
On Sat, Aug 30, 2014 at 12:23 AM, Trevor Saunders wrote:
>> Of course we should make things more explicit here and move all data
>> structures out of GC that are explicitly freed. Work in that direction is
>> welcome. The CFG is in GC memory because it indirectly refers to trees (the
>> sing
On Sat, Aug 30, 2014 at 12:54:16AM +0200, Steven Bosscher wrote:
> On Sat, Aug 30, 2014 at 12:23 AM, Trevor Saunders
> wrote:
>
> >> Of course we should make things more explicit here and move all data
> >> structures out of GC that are explicitly freed. Work in that direction is
> >> welcome
> From: Grissiom [mailto:chaos.pro...@gmail.com]
> Sent: Friday, August 29, 2014 11:51 PM
>
> Yes, it does. The namespace reserved for the implementation is _[_A-Z].
> The namespace _[a-z] is still available for the user. Which means the
> user can declare their own _printf_float, and WE (as th
> -Original Message-
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf
> Of Thomas Preud'homme
> Sent: Saturday, August 30, 2014 12:27 PM
> Mmmh indeed. I checked C99 and section 7.1.3 paragraph 1 third clause
> states:
>
> "All identifiers that begin with an underscor
19 matches
Mail list logo
