mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>,
	Mitchell Blank Jr <mitch@sfgoth.com>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: sparse segfaults
Date: Mon, 22 Nov 2004 21:30:45 +0100	[thread overview]
Message-ID: <200411222130.46247.duncan.sands@math.u-psud.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0411221047140.20993@ppc970.osdl.org>

> I suspect (but don't have any real argument to back that up) is that the
> gcc "extended lvalues" fell out as a side effect from how gcc ended up
> doing some random semantic tree parsing, and it wasn't really "designed"
> per se, as much as just a random implementation detail. Then somebody 
> noticed it, and said "cool" and documented it.

Generalized lvalues have been removed.  Check out
http://gcc.gnu.org/ml/gcc/2004-11/msg00604.html

All the best,

Duncan.

  reply	other threads:[~2004-11-22 20:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-20 14:37 Russell King
2004-11-20 16:58 ` Linus Torvalds
2004-11-20 17:23   ` Russell King
2004-11-21 22:10 ` linux-os
2004-11-21 22:29   ` Nikita Danilov
2004-11-21 22:37   ` Linus Torvalds
2004-11-21 22:44     ` Jan Engelhardt
2004-11-21 23:43       ` Mitchell Blank Jr
2004-11-22  1:02       ` Linus Torvalds
2004-11-22 10:33         ` Jan Engelhardt
2004-11-22 16:22           ` Linus Torvalds
2004-11-22 18:21             ` Jan Engelhardt
2004-11-22 18:39             ` Mitchell Blank Jr
2004-11-22 18:54               ` Linus Torvalds
2004-11-22 20:30                 ` Duncan Sands [this message]
2004-11-23 13:59                   ` Nix
2004-11-22 19:16               ` Linus Torvalds
2005-03-26 22:48 Jan Engelhardt

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=200411222130.46247.duncan.sands@math.u-psud.fr \
    --to=duncan.sands@math.u-psud.fr \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitch@sfgoth.com \
    --cc=torvalds@osdl.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®