This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] porting to gcc-4.3 docs
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 10 Jan 2008 23:26:29 +0100 (CET)
- Subject: Re: [RFC] porting to gcc-4.3 docs
- References: <20080108184137.5ec72074@wabash.artheist.org>
On Tue, 8 Jan 2008, Benjamin Kosnik wrote:
> As such, I'd like to get a general indication from the greater GCC> community as to this plan. Does this document seem like a good idea?
> (Previously, we've left this kind of document to the user community.
> Often the passage of time has not been particularly kind to these
> links.) Is the suggested placement ok for everybody?
>
> If this is ok, some editing of duplicate info from changes.html should
> take place. I volunteer to do this.
Sweet, that's really a nice one. Thanks for stepping up with this,
Benjamin.
In addition to the link from the gcc-4.3/changes.html page I'd also like
this to become a News item on the main page and we probably also will want
to add a link from gcc-4.3/index.html itself. Don't be shy. :-)
> And, finally, we'd need an ok from the wwwdocs head dude, Gerald.
Looks good. I'll make a few comments below to avoid you getting hit by
the automatic web pages checker, and I hope the various maintainers will
also have a look at their respective domains but let's get this in!
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<link rev="made" href="mailto:gcc@gcc.gnu.org"; />
<link rel="shortcut icon" href="http://gcc.gnu.org/favicon.ico"; />
<link rel="stylesheet" type="text/css" href="/gnu.css" />
<link rel="stylesheet" type="text/css" href="http://gcc.gnu.org/gcc.css"; />
Most of this, and also the color settings in the <body> tag and the footer
you can omit. The wwwdocs machinery is taking care of it automagically.
compilation or runt-time performance. Some of these changes are not
^^^
Typo. And, yes, I did spot the reference to naked users. But heck,
we already knew those free software types all are old hippies, didn't
we? <lol>
<h3>C language issues</h3>
<h5>Semantic change of extern inline</h5>
I believe we'll want <h4> here?
When compiling with -std=c99 or -std=gnu99, the <code>extern
Usually we write <code>-std=c99</code>, as you did later on.
In addition, improvements to the GCC infrastructure allows several
existing warning flags new ability to spot problematic code.
Is this sentence okay? I'm not a native speaker, so I might miss a
nuance here.
trailing characters after a closing #endif are now hard errors.
<code>#endif</code>
<p>To get rid of this error, remove any trailing text after an #endif, like so.
<code>#endif</code>
I'd say, take the input from Joe and Andrew into account and shoot
ahead!
Gerald