unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: gcc 2.95 inline scm_is_pair workaround
Date: Sun, 28 May 2006 09:44:45 +1000	[thread overview]
Message-ID: <873bev118y.fsf@zip.com.au> (raw)
In-Reply-To: <87wtcgnu12.fsf@zagadka.de> (Marius Vollmer's message of "Sun, 21 May 2006 02:41:45 +0300")

[delayed by a mail bounce]

Marius Vollmer <mvo@zagadka.de> writes:
>
> Should we still support GCC 2.95?

It's still in current debian unstable, so it's not totally dead.
Using it guards against some c99-isms (local variables in the middle
of functions) so it has some use for development.

> 	* throw.c (scm_ithrow): Remove "asm volatile" hack.  It used to
> 	work around a bug in GCC 2.95.2 but is now a bug in itself.

Doesn't look so evil as to cause a bug itself ...

I put mine conditionalized precisely to gcc==2.95, so as to restrict
its effect.  All this sort of thing is pretty ugly, but at least if
it's tightly delimited then it's clear what you can rip out in 10
years time.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      parent reply	other threads:[~2006-05-27 23:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19 23:51 gcc 2.95 inline scm_is_pair workaround Kevin Ryde
2006-05-20 23:41 ` Marius Vollmer
     [not found]   ` <87y7wwus6o.fsf@zip.com.au>
2006-05-21 23:38     ` Marius Vollmer
2006-05-22  6:49   ` Ludovic Courtès
2006-05-27 23:44   ` Kevin Ryde [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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873bev118y.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).