mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Samium Gromoff <deepfire@ibe.miee.ru>
Cc: linux-kernel@vger.kernel.org, gcc-bugs@gcc.gnu.org
Subject: Re: [GCC] gcc vs. indentation
Date: Tue, 01 Jul 2003 09:12:06 -0400	[thread overview]
Message-ID: <200307011312.h61DC6F2002208@eeyore.valparaiso.cl> (raw)
In-Reply-To: Message from Samium Gromoff <deepfire@ibe.miee.ru>  of "Mon, 30 Jun 2003 09:20:15 +0400." <20030630092015.49dd6969.deepfire@ibe.miee.ru>

Samium Gromoff <deepfire@ibe.miee.ru> said:

[...]

> 	Surprisingly enough i`ve realised soon that indeed some indentation changes
>  give gcc a reason to produce different code.

[...]

> --- ./origDAC960.o.d    2003-06-29 21:02:55.000000000 +0400
> +++ ./newDAC960.o.d     2003-06-29 22:13:46.000000000 +0400
> -    52ae:      7d 0d                   jge    52bd <DAC960_V1_ProcessCompletedCommand+0x7d>
> +    52ae:      7c 0d                   jl     52bd <DAC960_V1_ProcessCompletedCommand+0x7d>

[...]

> -    542b:      8f 0d 27 00 00 00       popl   0x27
> +    542b:      8e 0d 27 00 00 00       movl   0x27,%cs

[...]

> -    6ba8:      bc 11 27 00 00          mov    $0x2711,%esp
> +    6ba8:      bb 11 27 00 00          mov    $0x2711,%ebx

This looks like 1-bit errors to my eye...
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

      parent reply	other threads:[~2003-07-01 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30  5:20 Samium Gromoff
2003-06-30  7:04 ` Hugh Dickins
2003-06-30  6:13   ` Samium Gromoff
2003-07-01 13:12 ` Horst von Brand [this message]

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=200307011312.h61DC6F2002208@eeyore.valparaiso.cl \
    --to=vonbrand@inf.utfsm.cl \
    --cc=deepfire@ibe.miee.ru \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®