All of lore.kernel.org
 help / color / mirror / Atom feed
From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH 2.6.11.10] arch/cris: fixes static strings declaration
Date: Thu, 26 May 2005 18:27:47 +0000	[thread overview]
Message-ID: <42961523.9050505@bfs.de> (raw)
In-Reply-To: <20050526122502.7aa13915.rnsanchez@terra.com.br>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

hi Alexey,
you ask for it :)

  cris-gcc -v
Reading specs from /usr/local/cris/lib/gcc-lib/cris/2.96/specs
gcc version 2.96 Axis release R46/1.25

testprogramm:

#include <stdio.h>
//char *foo = "blah";
char foo[]="blah";
int main()
{
printf("%s\n",foo);

}

  size test_string  (char [])
    text    data     bss     dec     hex filename
     769     252      36    1057     421 test_string


size test_string2  (char *)
    text    data     bss     dec     hex filename
     777     248      40    1065     429 test_string2


sorry, i could not resist :)

re,
	walter



Alexey Dobriyan wrote:
> On Thursday 26 May 2005 21:21, Ricardo Nabinger Sanchez wrote:
> 
>>Quoting  Alexey Dobriyan <adobriyan@gmail.com>
>>Sent on  Thu, 26 May 2005 20:35:55 +0400
>>
>>
>>>What's the difference in .text and .data sizes?
>>
>>It's small,
> 
> 
> I want to see size(1) output on cross-compiled .o
> 
> IIRC the difference depends on gcc version and can even be positive.
> 


[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2005-05-26 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 15:25 [KJ] [PATCH 2.6.11.10] arch/cris: fixes static strings declaration Ricardo Nabinger Sanchez
2005-05-26 16:35 ` Alexey Dobriyan
2005-05-26 17:21 ` Ricardo Nabinger Sanchez
2005-05-26 17:58 ` Alexey Dobriyan
2005-05-26 18:27 ` walter harms [this message]
2005-05-26 18:47 ` Alexey Dobriyan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42961523.9050505@bfs.de \
    --to=wharms@bfs.de \
    --cc=kernel-janitors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.