mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Redefine instances of sema_init() to use standard form.
Date: Fri, 13 Oct 2006 02:10:15 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610130156480.14713@localhost.localdomain> (raw)
In-Reply-To: <200610130047.58507.zippel@linux-m68k.org>


  i can't believe a simple cleanup patch has turned into such an
issue.

On Fri, 13 Oct 2006, Roman Zippel wrote:

> Hi,
>
> On Thursday 12 October 2006 09:44, Robert P. J. Day wrote:
>
> > Since there seems to be no compelling reason *not* to do this,
> [..]
> > -	/*
> > -	 * Logically,
> > -	 *   *sem = (struct semaphore)__SEMAPHORE_INITIALIZER((*sem),val);
> > -	 * except that gcc produces better initializing by parts yet.
> > -	 */
>
> You've seen this?

in fact, i did, and i admit that i have no idea what it means to say
that "gcc produces better initializing by parts yet."

there were a number of semaphore.h files whose comments made it clear
that GCC 2.7.2.3 was the *only* reason that the shorter, more direct
form wasn't being used, so it should be clear that those could be
changed.

there was only *one* of those header files (asm-alpha/semaphore.h)
that had the caution above, but i have no idea what "better
initializing" means?

"better" as in faster?  "better" as in more compact?  "better" as in
correct?  i mean, either the shorter, more direct initialization
*works* and produces the same result in this case, or it *doesn't*.
which is it?  or is that note perhaps a holdover from an old version
of gcc as well?

can you clarify what that comment means in the context of the alpha
architecture, and why simplifying the call would actually be a
mistake?

rday

      reply	other threads:[~2006-10-13  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12  7:44 Robert P. J. Day
2006-10-12 22:47 ` Roman Zippel
2006-10-13  6:10   ` Robert P. J. Day [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=Pine.LNX.4.64.0610130156480.14713@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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®