On Tue, Jun 21, 2011 at 8:33 PM, David Malcolm wrote:
> I've been working on a new plugin for GCC, which supports embedding
> Python within GCC, exposing GCC's internal data structures as Python
> objects and classes.
>
> The plugin links against libpython, and (I hope) allows you to invoke
> arbi
On 21/06/11 19:01, Ian Lance Taylor wrote:
CFLAGS.
CFLAGS_FOR_BUILD is for code compiled for the build system. CFLAGS is
for code compiled for the host system. CFLAGS_FOR_TARGET is for code
compiled for the target system. The driver and the compiler as a whole
run on the host system. The bu
Hello,
I have added a builtin __function_size that is supposed to receive a
pointer to a function and return the size, in words, that the function
takes.
We got it working until GCC4.5. In GCC4.5 became tricky for 2 reasons.
First, GCC 4.5 removes the function if the only reference to the
f
"Paulo J. Matos" writes:
> My thought was to fold __function_size still to a special label
> (unique for each function) that would be then generates by as and set
> to the unrelaxed size of the function. Once the linker performs the
> required relaxation it also modifies the label value according
Well, the basic issue is that the "linkage name" is produced by
libiberty/cp-demangle.c and the DW_AT_name is produced by
gcc/cp/error.c, and they don't always agree on the same pretty-printed
representation of a C++ expression.
For this case,
The function linkage name has prefix: K<&(S::m(i
On Wed, 22 Jun 2011 08:19:17 +0200
Jakub Jelinek wrote:
> You could just:
> #include "ggc.h"
>
> static void my_walker (void *arg ATTRIBUTE_UNUSED)
> {
> /* Ignore argument, as it is dummy */
> /* Walk all the still live python objects here and if they reference
> GCC GC objects, call
>
On 22/06/11 16:23, Ian Lance Taylor wrote:
You don't need to do that, you just need to tell the assembler to not
fully resolve the difference between two text symbols, but to leave it
to the linker as a PC-relative reloc. In gas you typically do this by
defining DIFF_EXPR_OK in your config/tc-CP
On 22/06/11 17:34, Paulo J. Matos wrote:
I thought this was the same as using __attribute__((used)) on a function
declaration (which works).
DECL_PRESERVE_P(node) = 1;
seems to be what I wanted. :)
On Wed, Jun 22, 2011 at 10:42 AM, Jason Merrill wrote:
> Well, the basic issue is that the "linkage name" is produced by
> libiberty/cp-demangle.c and the DW_AT_name is produced by gcc/cp/error.c,
> and they don't always agree on the same pretty-printed representation of a
> C++ expression.
>
> Fo
On Monday, June 20, 2011 03:01:47 PM Jakub Jelinek wrote:
> The first release candidate for GCC 4.6.1 is available from
>
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.1-RC-20110620
>
> and shortly its mirrors. It has been generated from SVN revision 175201.
>
> I have so far bootstrapped and tes
On Wed, Jun 22, 2011 at 11:21:16PM +0200, Paweł Sikora wrote:
> On Monday, June 20, 2011 03:01:47 PM Jakub Jelinek wrote:
> > The first release candidate for GCC 4.6.1 is available from
> >
> > ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.1-RC-20110620
> >
> > and shortly its mirrors. It has been g
"H.J. Lu" writes:
> Apparently, there is no GCC maintainer for Linux/x86 platform. I have
> been working on GCC, as well as binutils and C libraries, for Linux/x86
> over 20 years. I ported GCC, binutils and the C library to Linux/x86. I
> like to be appointed as maintainer for Linux/x86 platfo
"Paulo J. Matos" writes:
> On 22/06/11 17:34, Paulo J. Matos wrote:
>> I thought this was the same as using __attribute__((used)) on a function
>> declaration (which works).
>>
>
> DECL_PRESERVE_P(node) = 1;
>
> seems to be what I wanted. :)
I always wondered what that was for.
Ian
On Tue, Jun 21, 2011 at 1:01 AM, Jakub Jelinek wrote:
> The first release candidate for GCC 4.6.1 is available from
>
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.1-RC-20110620
>
> and shortly its mirrors. It has been generated from SVN revision 175201.
>
> I have so far bootstrapped and tested the
On Wed, Jun 22, 2011 at 3:25 PM, Ian Lance Taylor wrote:
> "H.J. Lu" writes:
>
>> Apparently, there is no GCC maintainer for Linux/x86 platform. I have
>> been working on GCC, as well as binutils and C libraries, for Linux/x86
>> over 20 years. I ported GCC, binutils and the C library to Linux/
15 matches
Mail list logo
