Hi all,
I'd like to know if there is any way, even using gcc extensions,
to syntactically "catch" what is the return type (and the list
of formal arguments) of a function in which I am.
Also, in case there is no way, I'd like to know how difficult would
be to introduce a couple of keywords, like
Adam Nemet writes:
> struct s
> {
> char a:4;
> char b:8;
> char c:4;
> } __attribute__ ((packed))
>
> is 3 bytes long because b gets pushed to the next byte boundary.
Sounds like a bug.
> The reason for this behavior is that finish_struct does not propagate packed
> to fields whose type
On Fri, Jan 16, 2009 at 4:19 PM, Ian Lance Taylor wrote:
> Adam Nemet writes:
>
>> struct s
>> {
>> char a:4;
>> char b:8;
>> char c:4;
>> } __attribute__ ((packed))
>>
>> is 3 bytes long because b gets pushed to the next byte boundary.
>
> Sounds like a bug.
>
>
>> The reason for this beha
Hi,
I am working on a gcc-4.1.2 and I would like to know how the prologue
length from a function can be calculated.
Indeed I am trying to evaluate what needs to be done to implement SEH and
one requirement is to be able to
fill a structure holding information like function length and prologue
leng
"Vincent R." writes:
> I am working on a gcc-4.1.2 and I would like to know how the prologue
> length from a function can be calculated.
The question is not well formed. The instructions which are part of
the prologue (e.g., saving callee-saved registers onto the stack) can
be interspersed with
Hi,
I am trying to implement
unsigned long long __rdtsc (void);
for RDTSC as an intrinsic. It is easy to do it with asm statement.
But I am having a hard time to implement it as a gcc builtin.
The main problem is there is no input. It is impossible to write
a proper RTL for it. Any suggestions
Sent from my iPhone
On Jan 16, 2009, at 9:23 AM, "H.J. Lu" wrote:
Hi,
I am trying to implement
unsigned long long __rdtsc (void);
for RDTSC as an intrinsic. It is easy to do it with asm statement.
But I am having a hard time to implement it as a gcc builtin.
The main problem is there is
On Fri, Jan 16, 2009 at 09:35:33AM -0800, Andrew Thomas Pinski wrote:
> On Jan 16, 2009, at 9:23 AM, "H.J. Lu" wrote:
>
>> Hi,
>>
>> I am trying to implement
>>
>> unsigned long long __rdtsc (void);
>>
>> for RDTSC as an intrinsic. It is easy to do it with asm statement.
>> But I am having a hard
On Fri, Jan 16, 2009 at 11:35 AM, Jack Lloyd wrote:
> According to the info docs, the Alpha has __builtin_alpha_rpcc which
> doesn't take any inputs either, and should just call rpcc much as an
> rdtsc intrinsic would, so it may provide a more direct model.
(define_insn "builtin_rpcc"
[(set (ma
On Fri, 16 Jan 2009 08:37:20 -0800, Ian Lance Taylor
wrote:
> "Vincent R." writes:
>
>> I am working on a gcc-4.1.2 and I would like to know how the prologue
>> length from a function can be calculated.
>
> The question is not well formed. The instructions which are part of
> the prologue (e.g
On Fri, Jan 16, 2009 at 12:47 PM, Andrew Pinski wrote:
> On Fri, Jan 16, 2009 at 11:35 AM, Jack Lloyd wrote:
>> According to the info docs, the Alpha has __builtin_alpha_rpcc which
>> doesn't take any inputs either, and should just call rpcc much as an
>> rdtsc intrinsic would, so it may provide
On Fri, Jan 16, 2009 at 1:28 PM, H.J. Lu wrote:
> On Fri, Jan 16, 2009 at 12:47 PM, Andrew Pinski wrote:
>> On Fri, Jan 16, 2009 at 11:35 AM, Jack Lloyd wrote:
>>> According to the info docs, the Alpha has __builtin_alpha_rpcc which
>>> doesn't take any inputs either, and should just call rpcc m
"Vincent R." writes:
> To locate appropriate handlers when an exception occurs in Win32
> environments other than x86,
Note that as far as I know, gcc only supports win32 for ARM and x86
(and x86_64, I guess, or maybe that is win64). So I assume you are
talking about ARM.
> The portion of th
On Fri, 16 Jan 2009 14:13:58 -0800, Ian Lance Taylor
wrote:
> "Vincent R." writes:
>
>> To locate appropriate handlers when an exception occurs in Win32
>> environments other than x86,
>
> Note that as far as I know, gcc only supports win32 for ARM and x86
> (and x86_64, I guess, or maybe that
Snapshot gcc-4.4-20090116 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.4-20090116/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.4 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
It's not my turn to send a status report, but as I plan doing a release
candidate for GCC 4.3.3 soon I thought a status report for that would
be in order.
Status
==
The GCC 4.3 branch is now frozen in preparation for a release candidate
for the GCC 4.3.3 release. When the branch is unfrozen
On Fri, Jan 16, 2009 at 3:03 PM, Richard Guenther wrote:
>
> It's not my turn to send a status report, but as I plan doing a release
> candidate for GCC 4.3.3 soon I thought a status report for that would
> be in order.
>
> Status
> ==
>
> The GCC 4.3 branch is now frozen in preparation for a
On Fri, 16 Jan 2009, H.J. Lu wrote:
> On Fri, Jan 16, 2009 at 3:03 PM, Richard Guenther wrote:
> >
> > It's not my turn to send a status report, but as I plan doing a release
> > candidate for GCC 4.3.3 soon I thought a status report for that would
> > be in order.
> >
> > Status
> > ==
> >
>
"Vincent R." writes:
> No you are right, prologue definition in my context is :
> Typically, a prolog segment contains separate sequences of instructions
> that perform the following tasks:
>
> * Allocate a stack frame.
> * Save incoming argument registers.
> * Set up the frame pointe
19 matches
Mail list logo
