All of lore.kernel.org
 help / color / mirror / Atom feed
From: chambilkethakur@gmail.com (Anuz Pratap Singh Tomar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: gdtr value
Date: Mon, 18 Feb 2013 15:05:21 +0000	[thread overview]
Message-ID: <CAJnfX5u0cXyZpSWFXpo7yedXzMzBfJd+2tqNWrMNaR__g7o1Zg@mail.gmail.com> (raw)
In-Reply-To: <20130218050711.GB11240@debian.localdomain>

On Mon, Feb 18, 2013 at 5:07 AM, horseriver <horserivers@gmail.com> wrote:

> hi:)
>
>   I have compiled a .S file ,using command gcc -c x.S -o x.
>   Then I use objdump to look up its asm code, even find that some code is
> not the
>   same as that .S file , more important is , some code in origin  .S file
> has disappear .
>
>   what is about the reason ? If it is due to version , why some code
> chould get lost after compile?
>
> Couple of things
1. Please don't piggy back questions over the unrelated topic, that is
totally misdirecting the discussion.
2. You ask a lot of question related to compilation and stuff, which are
off-topic here, why not READ a little bit more or consult relevant
documentation?
3. You seem to do no homework before asking viz googling or reading basic
books on relevant topic for example in this case reading a book on assembly
language programming.

When you write any assembly code(or for that matter any code) your code is
written to be read by HUMANS and not machines. For machines a lot of that
code is redundant and has no use so machine code will be generated in such
a form that it is most optimized for the execution. For example take any
*.c code and do

#gcc -S *.c
you will see an equivalent assembly code. It may not exactly be similar to
the code which you will write in assembly for same logic. There are some
rules according to which compilers generate code, please read some book on
compilers and lex and yacc.




> thanks!
>



-- 
Thank you
Warm Regards
Anuz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130218/24a7645d/attachment-0001.html 

  reply	other threads:[~2013-02-18 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18  1:55 gdtr value horseriver
2013-02-18 12:25 ` Anuz Pratap Singh Tomar
2013-02-18  5:07   ` horseriver
2013-02-18 15:05     ` Anuz Pratap Singh Tomar [this message]
2013-02-18 15:50       ` Anuz Pratap Singh Tomar
     [not found]   ` <20130219221809.GB2447@debian.localdomain>
2013-02-20 10:50     ` Anuz Pratap Singh Tomar
  -- strict thread matches above, loose matches on Subject: below --
2013-02-18  1:53 horseriver

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=CAJnfX5u0cXyZpSWFXpo7yedXzMzBfJd+2tqNWrMNaR__g7o1Zg@mail.gmail.com \
    --to=chambilkethakur@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.