Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Tom Tromey <tromey@redhat.com>, <dje@google.com>,
	<pierre.muller@ics-cnrs.unistra.fr>, <gdb-patches@sourceware.org>
Subject: Re: New ARI warning Wed May 23 01:55:03 UTC 2012
Date: Tue, 29 May 2012 13:29:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1205291419340.11227@tp.orcam.me.uk> (raw)
In-Reply-To: <201205282043.q4SKhksB010254@glazunov.sibelius.xs4all.nl>

On Mon, 28 May 2012, Mark Kettenis wrote:

> OpenBSD/vax, OpenBSD/m68k and OpenBSD/m88k are still stuck with GCC
> 2.95, which is almost, but not quite C99.  However, it's been ages
> since I've last built GDB on any of those platforms.  So it's probably
> time to stop caring about those platforms.  I fear that GDB has become
> too bloated to be able to build it a typical machine that runs these
> specific OpenBSD versions.  But even GCC 2.95 supports long long as an
> extension to C90.

 Interesting, I found GCC 4.1.2 working reasonably well for the VAX 
target, other versions are probably OK too -- why did OpenBSD stick to 
such an old version for that target?

 Anyway, I reckon GCC used to support long long even before that, although 
there might have been issues.

> So I'd have no objection to requiring C99, except for one
> style-related issue.  I really, really hate mixing declarations with
> code (something that C99 started to allow).  So if we switch to
> requiring C99, I think we should add a rule to the coding standards
> that variables may only be declared at the start of a block.

 FWIW, I concur.  I find them confusing and easy to avoid.

  Maciej


  parent reply	other threads:[~2012-05-29 13:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23  1:55 GDB Administrator
2012-05-23  4:18 ` Sergio Durigan Junior
2012-05-23  7:10   ` Doug Evans
2012-05-23  7:27     ` Doug Evans
2012-05-23  8:19       ` Pierre Muller
2012-05-23 14:45       ` Sergio Durigan Junior
     [not found]       ` <4fbc9d77.0853b40a.641e.ffff90dbSMTPIN_ADDED@mx.google.com>
2012-05-23 14:46         ` Doug Evans
2012-05-23 15:01           ` Doug Evans
2012-05-23 15:27             ` Pedro Alves
2012-05-24 18:55           ` Tom Tromey
2012-05-28 20:44             ` Mark Kettenis
2012-05-28 21:59               ` Joel Brobecker
2012-05-29 13:29               ` Maciej W. Rozycki [this message]
2012-06-22 16:05               ` Tom Tromey
2012-06-22 17:19                 ` Joel Brobecker
2012-06-22 17:31                   ` Joel Brobecker
2012-06-22 17:41                     ` Tom Tromey
2012-06-22 19:02                       ` Joel Brobecker
2012-06-25 19:59                         ` Doug Evans
2012-06-26 13:31                         ` Mark Kettenis
2012-06-26 13:15                   ` Mark Kettenis
2012-06-26 11:51                 ` Mark Kettenis
2012-05-23  7:10   ` Andreas Schwab

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=alpine.DEB.1.10.1205291419340.11227@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    --cc=tromey@redhat.com \
    /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