From: "Thibaud GUERIN" <thibaud@ploposor.com>
To: "Andrew Haley" <aph@gcc.gnu.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Fwd: error in variable dereferencing
Date: Fri, 21 Apr 2006 16:57:00 -0000 [thread overview]
Message-ID: <96d59a150604210957t4ba29204tc5c719c4db5e03a0@mail.gmail.com> (raw)
In-Reply-To: <17481.3358.9752.328996@zapata.pink>
On 4/22/06, Andrew Haley <aph@gcc.gnu.org> wrote:
> Thibaud GUERIN writes:
> > On 4/22/06, Andrew Haley <aph@redhat.com> wrote:
> > > Well, we've established that whetever is wrong, it's not the code gcc
> > > generates for this routine. It's correct, as you can see.
> > >
> > > > The only debug ways usable in the code right now are some things like :
> > > > i = (long)(fmt);
> > > > __asm__ volatile ("mov %0, %%eax\n":: "m"(i));
> > > > __asm__ volatile ("l1: jmp l1");
> > > >
> > > > which are really dirty i agree...
> > >
> > > Thay're also wrong, becasue they don't clobber eax.
> >
> > If you have any way to do it (or check with cleaner ways) i'm
> > listening .... it'll be helpfull....
>
> Just put "eax" in the clobber list of the asm. But really, we've gone
> as far down the read as we can with this: the gcc code you produced is
> correct. Time to look elsewhere.
>
Yeah, i think too,
i learned a lot (-S flag, ....)
thanks for everything and sorry for disturbance....
--
Thibaud
next prev parent reply other threads:[~2006-04-21 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96d59a150604200353h6249fa1fr8a93d20baff37fc5@mail.gmail.com>
[not found] ` <96d59a150604200657m53252a12t601302ec580f44b7@mail.gmail.com>
[not found] ` <17479.38716.774167.250676@zapata.pink>
2006-04-20 14:37 ` Thibaud GUERIN
[not found] ` <C06D08C8.E410%eljay@adobe.com>
2006-04-20 15:38 ` Thibaud GUERIN
2006-04-20 15:41 ` Fwd: " Andrew Haley
[not found] ` <96d59a150604200858sa31ac6brd5cf87387b452fc4@mail.gmail.com>
2006-04-20 16:01 ` Thibaud GUERIN
2006-04-20 16:13 ` Andrew Haley
2006-04-20 16:26 ` Thibaud GUERIN
2006-04-21 13:36 ` Andrew Haley
2006-04-21 15:17 ` Thibaud GUERIN
2006-04-21 15:26 ` Andrew Haley
2006-04-21 15:42 ` Thibaud GUERIN
2006-04-21 16:00 ` Andrew Haley
2006-04-21 16:17 ` Thibaud GUERIN
2006-04-21 16:29 ` Andrew Haley
2006-04-21 16:41 ` Thibaud GUERIN
2006-04-21 16:49 ` Andrew Haley
2006-04-21 16:57 ` Thibaud GUERIN [this message]
2006-04-21 17:03 ` Andrew Haley
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=96d59a150604210957t4ba29204tc5c719c4db5e03a0@mail.gmail.com \
--to=thibaud@ploposor.com \
--cc=aph@gcc.gnu.org \
--cc=gcc-help@gcc.gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).