memory allocation are three types:
a. stack allocation.
b. dynamic heap-based - using api like malloc()and this happened
in the heap areadepending on ELF loading and
architecture-specific.
c. static memory - this is purely embedded inside the ELF file, so
during loading it just got m
I'm porting for a microcontroller with segmented
memory. And I want to see how memory are allocated for
variables with different directives such as NEAR, FAR
. So where can I find it in GCC source code ?
Your information is very helpful to me. Thanh you very
much.
--- Piotr Rak <[EMAIL PROTECTED]> wrote:
> Some of them are common, other are target specific.
> To add new attribute, you might want take a look at
> c_common_attribute_table in gcc/c-common.c,
> attribute_spec struct in
> gcc/tree.
Seongbae Park ??? ??? wrote:
David,
Just in case you haven't noticed this thread - I figured you may want
to comment on it.
Seongbae
-- Forwarded message --
From: Manuel López-Ibáñez <[EMAIL PROTECTED]>
Date: Wed, Oct 22, 2008 at 2:00 PM
Subject: Re: conditional assigments vs.
Snapshot gcc-4.2-20081022 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20081022/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.2 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
thanks.. mea culpa, I assumed that 'testing fixes' solely meant making
the fixincludes ready for release..
Ed
On Tue, Oct 21, 2008 at 9:49 PM, Eric Botcazou <[EMAIL PROTECTED]> wrote:
>> Yes, I got that from the README. What I was looking for was a
>> *shortcut*,
>
> "5. Testing fixes" precisely
2008/10/22 Hallvard B Furuseth <[EMAIL PROTECTED]>:
> Info node (gcc)Warning Options mentions that gcc warns about
>
>int save_y;
>if (change_y) save_y = y, y = new_y;
>...
>if (change_y) y = save_y;
>
> However that's not always true, so it looks lik
On Wed, Oct 22, 2008 at 12:57 PM, Hallvard B Furuseth
<[EMAIL PROTECTED]> wrote:
> Info node (gcc)Warning Options mentions that gcc warns about
>
>int save_y;
>if (change_y) save_y = y, y = new_y;
>...
>if (change_y) y = save_y;
>
> However that's not
Info node (gcc)Warning Options mentions that gcc warns about
int save_y;
if (change_y) save_y = y, y = new_y;
...
if (change_y) y = save_y;
However that's not always true, so it looks like gcc does have
the smarts to drop the warning. Could that be
Yes, things like near, far, .. are all that I need. I
think this is the right way for me.
I've glanced at the link you gave me. I see that the
M32R/D has the attribute "model" with value "small,
medium and target", I don't know whether this is the
standard atributes for all targets in GCC that I
2008/10/22 Dong Phuong <[EMAIL PROTECTED]>:
>
> I'm porting for a microcontroller. And now I want to
> add some features to the current language C int GCC
> (for example some directives such as near, far ,
> ). SO could you please tell me how I can do that
> ?
Hi,
I am not sure if it is solve
I'm porting for a microcontroller. And now I want to
add some features to the current language C int GCC
(for example some directives such as near, far ,
). SO could you please tell me how I can do that
?
Thank you very much.
`VL wrote:
> Hello, ALL.
>
> I recently started to actively program using C and found that tools like
> ctags or cscope do not work properly for big projects. Quite ofthen they
> can't find function or symbol definition. The problem here is that they don't
> use full code parsing, but just some s
On Tuesday 21 October 2008 20:07:10 `VL wrote:
> Hello, ALL.
>
> I recently started to actively program using C and found that tools like
> ctags or cscope do not work properly for big projects. Quite ofthen they
> can't find function or symbol definition. The problem here is that they
> don't use
14 matches
Mail list logo
