From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: GCC switch to C11 causes many testsuite compiler diagnostics
Date: Thu, 30 Oct 2014 22:37:00 -0000 [thread overview]
Message-ID: <87h9ylb2w6.fsf@redhat.com> (raw)
In-Reply-To: <5452BB29.8090803@earthlink.net> (Stan Shebs's message of "Thu, 30 Oct 2014 15:26:49 -0700")
On Thursday, October 30 2014, Stan Shebs wrote:
> Perhaps the thing to do is pose this as a trivia quiz - what K&R sources
> are still being built and debugged on today's systems?
FWIW, I remember GDB itself has some K&R prototypes on some *-exp.y
files until a few years ago.
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2014-10-30 22:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 17:04 Sandra Loosemore
2014-10-25 17:28 ` Mark Kettenis
2014-10-30 16:23 ` Andreas Arnez
2014-10-31 19:02 ` Doug Evans
2014-10-31 19:23 ` Mark Kettenis
2014-10-31 19:29 ` Doug Evans
2014-11-03 11:02 ` Andreas Arnez
2014-10-30 16:07 ` Andreas Arnez
2014-10-30 22:26 ` Stan Shebs
2014-10-30 22:37 ` Sergio Durigan Junior [this message]
2014-11-23 7:27 ` Joel Brobecker
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=87h9ylb2w6.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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