release-notes/FC4 package-notes.xml, 1.12, 1.13 development-tools.xml, 1.2, 1.3
Tommy Reynolds (jtr)
fedora-docs-commits at redhat.com
Tue May 31 01:09:57 UTC 2005
Author: jtr
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3752
Modified Files:
package-notes.xml development-tools.xml
Log Message:
Added desultory descriptions of some of the changes, here at the 11th hour ;-)
Index: package-notes.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/package-notes.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- package-notes.xml 30 May 2005 18:33:21 -0000 1.12
+++ package-notes.xml 31 May 2005 01:09:54 -0000 1.13
@@ -1,6 +1,33 @@
+<!-- $Id: -->
+<!--
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+
+ <!ENTITY BOILERPLATE "This header makes editing XML easier" >
+ <!ENTITY DISTRO "DISTRO">
+ <!ENTITY DISTROVER "DISTROVER">
+ <!ENTITY FEX "FEX">
+ <!ENTITY FP "FP">
+ <!ENTITY FC "FC" >
+ <!ENTITY LOCALVER "LOCALVER">
+ <!ENTITY RHL "RHL">
+ <!ENTITY SERVER-TOOLS SYSTEM "/dev/null">
+ <!ENTITY KERNEL SYSTEM "/dev/null">
+ <!ENTITY SECURITY SYSTEM "/dev/null">
+ <!ENTITY SEL SYSTEM "/dev/null">
+ <!ENTITY PRINTING SYSTEM "/dev/null">
+ <!ENTITY DATABASE-SERVERS SYSTEM "/dev/null">
+ <!ENTITY MULTIMEDIA SYSTEM "/dev/null">
+ <!ENTITY WEB-SERVERS SYSTEM "/dev/null">
+ <!ENTITY SAMBA SYSTEM "/dev/null">
+ <!ENTITY XORG SYSTEM "/dev/null">
+ <!ENTITY DEVELOPMENT-TOOLS SYSTEM "./development-tools.xml">
+
+]>
+-->
<section>
<title>Package-Specific Notes</title>
- <!--
+ <!--
FIXME
Needs updating of entire contents for FC4.
-->
@@ -20,193 +47,193 @@
<section>
<title>&FEX; Repository</title>
<para>
- &FEX; is part of the larger &FP; and is a
- volunteer-based community effort to create a repository of
- packages that compliment &FC;. The &FEX; repository
- is enabled by default from &FC; &LOCALVER; onwards.
+ &FEX; is part of the larger &FP; and is a
+ volunteer-based community effort to create a repository of
+ packages that compliment &FC;. The &FEX; repository
+ is enabled by default from &FC; &LOCALVER; onwards.
</para>
<para>
- You can lean more about &FEX; from:
+ You can lean more about &FEX; from:
</para>
<para>
- <ulink url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
+ <ulink url="http://fedoraproject.org/wiki/Extras">http://fedoraproject.org/wiki/Extras</ulink>
</para>
<para>If you would like to install any software available from Fedora extras you can
- use <command>yum</command>.
+ use <command>yum</command>.
</para>
<para>
- <command>yum install <replaceable><packagename></replaceable></command>
+ <command>yum install <replaceable><packagename></replaceable></command>
</para>
<para>
- Where <replaceable><packagename></replaceable> is the name
- of the package you want to install. For example, if you wanted
- to install the <filename>abiword</filename> package, the command
- <command>yum install abiword</command> automatically installs
- the package and all dependencies.
+ Where <replaceable><packagename></replaceable> is the name
+ of the package you want to install. For example, if you wanted
+ to install the <filename>abiword</filename> package, the command
+ <command>yum install abiword</command> automatically installs
+ the package and all dependencies.
</para>
</section>
<section id="sn-audit-daemon">
<title>Audit Daemon <command>auditd</command> and Log
- Files</title>
+ Files</title>
<para>
- The audit daemon, auditd, is now enabled by default. When
- auditd is running, the kernel directs audit messages to
- /var/log/audit/audit.log. The location of this file is
- specified in /etc/auditd.conf.
+ The audit daemon, auditd, is now enabled by default. When
+ auditd is running, the kernel directs audit messages to
+ /var/log/audit/audit.log. The location of this file is
+ specified in /etc/auditd.conf.
</para>
<para>
- AVC messages for SELinux are sent using the audit
- infrastructure. These messages are now in
- /var/log/audit/audit.log.
+ AVC messages for SELinux are sent using the audit
+ infrastructure. These messages are now in
+ /var/log/audit/audit.log.
</para>
<para>
- When auditd is not running, the kernel passes audit messages to
- syslog. These logs are typically kept in /var/log/messages and
- are viewable using dmesg.
+ When auditd is not running, the kernel passes audit messages to
+ syslog. These logs are typically kept in /var/log/messages and
+ are viewable using dmesg.
</para>
<para>
- Audit extensions are now compiled into PAM. All programs that
- do grant entry to the system or change user account attributes
- will generate an audit message.
+ Audit extensions are now compiled into PAM. All programs that
+ do grant entry to the system or change user account attributes
+ will generate an audit message.
</para>
<para>
- To enable auditing within the kernel, you must pass the
- parameter audit=1 to the kernel during boot. Otherwise, you can
- use this command to enable auditing during run time:
+ To enable auditing within the kernel, you must pass the
+ parameter audit=1 to the kernel during boot. Otherwise, you can
+ use this command to enable auditing during run time:
</para>
<para>
- <command>auditctl -e 1</command>
+ <command>auditctl -e 1</command>
</para>
</section>
<section id="sn-nptl">
<title>LinuxThreads versus NPTL</title>
<para>
- As the next step in removing support for the obsolete
- LinuxThreads library, code compiled and linked on &FC;
- &LOCALVER; now automatically uses the NPTL headers and
- libraries.
+ As the next step in removing support for the obsolete
+ LinuxThreads library, code compiled and linked on &FC;
+ &LOCALVER; now automatically uses the NPTL headers and
+ libraries.
</para>
<para>
- In previous releases since &RHL; 9, the default threading was
- LinuxThreads since the interface is mostly forward compatible.
- The advantages of the NPTL interface is that the cancellation
- handling is faster (when <parameter>-fexception</parameter> is
- used, even in C code) and that the additional interfaces are now
- available without special compiler and linker parameters. In
- other words, you do not need to use
- <option>-I/usr/include/nptl</option> and
- <option>-L/usr/lib{,64}/nptl</option> any longer. Note
- that <parameter>lib{,64}</parameter> is to be interpreted as
- lib64 on platforms which place DSOs in
- <filename>lib64/</filename> directories, and
- <filename>lib/</filename> otherwise.
+ In previous releases since &RHL; 9, the default threading was
+ LinuxThreads since the interface is mostly forward compatible.
+ The advantages of the NPTL interface is that the cancellation
+ handling is faster (when <parameter>-fexception</parameter> is
+ used, even in C code) and that the additional interfaces are now
+ available without special compiler and linker parameters. In
+ other words, you do not need to use
+ <option>-I/usr/include/nptl</option> and
+ <option>-L/usr/lib{,64}/nptl</option> any longer. Note
+ that <parameter>lib{,64}</parameter> is to be interpreted as
+ lib64 on platforms which place DSOs in
+ <filename>lib64/</filename> directories, and
+ <filename>lib/</filename> otherwise.
</para>
<para>
- In &FC; &LOCALVER; it is still possible to create code using the
- LinuxThreads definitions. For this the
- <filename>linuxthreads-devel</filename> package must be
- installed and
+ In &FC; &LOCALVER; it is still possible to create code using the
+ LinuxThreads definitions. For this the
+ <filename>linuxthreads-devel</filename> package must be
+ installed and
</para>
<para>
- <option>-I/usr/include/linuxthreads
- -L/usr/lib{,64}/linuxthreads</option>
+ <option>-I/usr/include/linuxthreads
+ -L/usr/lib{,64}/linuxthreads</option>
</para>
<para>
- must be passed to the compiler.
+ must be passed to the compiler.
</para>
<para>
- Previously, you could select the version of glibc and the
- libpgthread DSH using run time environment variables. You now
- need to also specify this variable in the environment:
+ Previously, you could select the version of glibc and the
+ libpgthread DSH using run time environment variables. You now
+ need to also specify this variable in the environment:
</para>
<para>
- <envar>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar>
+ <envar>LD_LIBRARY_PATH=/lib{,64}/obsolete/linuxthreads</envar>
</para>
<para>
- This additional variables is required because the run/time
- libraries have been moved out of the way. There might programs
- that will not work if the program uses an unfortunate DT_RPATH
- (which overwrites the LD_LIBRARY_PATH setting).
+ This additional variables is required because the run/time
+ libraries have been moved out of the way. There might programs
+ that will not work if the program uses an unfortunate DT_RPATH
+ (which overwrites the LD_LIBRARY_PATH setting).
</para>
<para>
- All this makes it more cumbersome to run programs which depend
- on LinuxThreads. But this is intentional.
+ All this makes it more cumbersome to run programs which depend
+ on LinuxThreads. But this is intentional.
</para>
<important>
- <title>Important</title>
- <para>
- FC5 will not have LinuxThreads support and all programs have
- to be converted to use NPTL by then.
- </para>
+ <title>Important</title>
+ <para>
+ FC5 will not have LinuxThreads support and all programs have
+ to be converted to use NPTL by then.
+ </para>
</important>
<para>
- In general, conversion to using NPTL has not been an issue.
+ In general, conversion to using NPTL has not been an issue.
</para>
</section>
<section>
<title>Enabling the <filename>slocate</filename> Database</title>
<para>
- The database needed by the locate utility is no longer created
- by default. Enable the database creation by setting
- <computeroutput>DAILY_UPDATE</computeroutput> to
- <option>yes</option> in <filename>/etc/updatedb.conf</filename>
- if you want to use locate.
+ The database needed by the locate utility is no longer created
+ by default. Enable the database creation by setting
+ <computeroutput>DAILY_UPDATE</computeroutput> to
+ <option>yes</option> in <filename>/etc/updatedb.conf</filename>
+ if you want to use locate.
</para>
</section>
<section>
<title>Stricter Controls in <filename>openssh</filename></title>
<para>
- The version of OpenSSH in &FC; &LOCALVER; is based on OpenSSH
- 3.9 and includes strict permission and ownership checks for the
- user configuration file <filename>~/.ssh/config</filename>. If
- this file does not have appropriate ownership and permissions,
- <command>ssh</command> will exit.
+ The version of OpenSSH in &FC; &LOCALVER; is based on OpenSSH
+ 3.9 and includes strict permission and ownership checks for the
+ user configuration file <filename>~/.ssh/config</filename>. If
+ this file does not have appropriate ownership and permissions,
+ <command>ssh</command> will exit.
</para>
<para>
- Check that <filename>~/.ssh/config</filename> is owned by the
- owner of <filename>~/</filename>, and that its permissions are
- set to mode 600.
+ Check that <filename>~/.ssh/config</filename> is owned by the
+ owner of <filename>~/</filename>, and that its permissions are
+ set to mode 600.
</para>
<screen>
ls -l ~/.ssh/config
-rw------- 1 username username 400 May 5 18:44 /home/username/.ssh/config
</screen>
<para>
- The directory <filename>~/</filename> is command-line shorthand
- for the logged in user's home directory, usually
- <filename>/home/username/</filename>.
- </para>
- <para>
- In addition, OpenSSH is no longer configured to request X11
- forwarding by default when connecting to servers. To enable X11
- forwarding, the <option>-X</option> or <option>-Y</option>
- option must be specified, or the <option>ForwardX11</option>
- option must be enabled in the <filename>~/.ssh/config</filename>
- file.
- </para>
- <para>
- The behavior of <command>ssh</command> clients that are invoked
- with the <option>-X</option> option has changed. In OpenSSH 3.8
- and later, X11 forwarding is performed in a way that
- applications run as untrusted clients by default. Previously,
- X11 forwarding was performed so that applications always ran as
- trusted clients. Some applications may not function properly
- when run as untrusted clients. To forward X11 so that
- applications are run as trusted clients, invoke ssh with the
- <option>-Y</option> option instead of the <option>-X</option>
- option, or set <option>ForwardX11Trusted</option> in the
- <option>~/.ssh/config</option> file.
+ The directory <filename>~/</filename> is command-line shorthand
+ for the logged in user's home directory, usually
+ <filename>/home/username/</filename>.
+ </para>
+ <para>
+ In addition, OpenSSH is no longer configured to request X11
+ forwarding by default when connecting to servers. To enable X11
+ forwarding, the <option>-X</option> or <option>-Y</option>
+ option must be specified, or the <option>ForwardX11</option>
+ option must be enabled in the <filename>~/.ssh/config</filename>
+ file.
+ </para>
+ <para>
+ The behavior of <command>ssh</command> clients that are invoked
+ with the <option>-X</option> option has changed. In OpenSSH 3.8
+ and later, X11 forwarding is performed in a way that
+ applications run as untrusted clients by default. Previously,
+ X11 forwarding was performed so that applications always ran as
+ trusted clients. Some applications may not function properly
+ when run as untrusted clients. To forward X11 so that
+ applications are run as trusted clients, invoke ssh with the
+ <option>-Y</option> option instead of the <option>-X</option>
+ option, or set <option>ForwardX11Trusted</option> in the
+ <option>~/.ssh/config</option> file.
</para>
</section>
<section id="sn-perl">
<title>Perl Binary Compat Symlinks</title>
<para>
- Binary compat symlinks for <filename>perl-5.8.0</filename>,
- <filename>perl-5.8.1</filename>, and
- <filename>perl-5.8.2</filename> have been removed. If you have
- perl modules built with those older versions of perl, you need
- to rebuild using the <filename>perl-5.8.6</filename> contained
- in &FC; &LOCALVER;.
+ Binary compat symlinks for <filename>perl-5.8.0</filename>,
+ <filename>perl-5.8.1</filename>, and
+ <filename>perl-5.8.2</filename> have been removed. If you have
+ perl modules built with those older versions of perl, you need
+ to rebuild using the <filename>perl-5.8.6</filename> contained
+ in &FC; &LOCALVER;.
</para>
</section>
&SERVER-TOOLS;
@@ -249,15 +276,15 @@
<section>
<title>yum</title>
<para>
- The sqllite database is now used by yum, and makes performance
- noticeably faster.
+ The sqllite database is now used by yum, and makes performance
+ noticeably faster.
</para>
<para>
- The Fedora Extras repository is now enabled by default.
+ The Fedora Extras repository is now enabled by default.
</para>
</section>
&KERNEL;
- &SECURITY;
+ &SECURITY;
</section>
<!--
<section>
@@ -443,14 +470,9 @@
<para>*** Enter group description here ***</para>
</section>
-
- <section os="bogus">
- <title>GNOME Software Development</title>
-
- <para>*** Enter group description here ***</para>
-
- </section>
-
+-->
+ &DEVELOPMENT-TOOLS;
+<!--
<section os="bogus">
<title>Games and Entertainment</title>
@@ -524,95 +546,95 @@
<section>
<title>The IIIMF Input System</title>
<para>
- IIIMF is the Internet/Intranet Input Method Framework. In &FC;
- &LOCALVER; the <filename>iiimf</filename> package is updated to
- version 12.2.
+ IIIMF is the Internet/Intranet Input Method Framework. In &FC;
+ &LOCALVER; the <filename>iiimf</filename> package is updated to
+ version 12.2.
</para>
<variablelist>
- <varlistentry>
- <term>Filepath Changes</term>
- <listitem>
- <para>
- The name and locations of some files in the
- <filename>iiimf</filename> packages have changed.
- </para>
- <para>
- The IIIMF server has been renamed from
- <filename>/usr/sbin/htt</filename> to
- <filename>/usr/bin/iiimd</filename>, and the XIM bridge
- client renamed from <filename>httx</filename> to
- <filename>iiimx</filename>. The
- <filename>init.d</filename> script name has not changed:
- it is still called <filename>iiim</filename>. All the
- global system configuration files are now located under
- <filename>/etc/iiim/</filename>.
- </para>
- <para>
- Language Engine (LE) developers should note that LE
- modules and their data now live under
- <filename>${libdir}/iiim/le/<filename><LE_NAME></filename>/</filename>,
- while runtime data is stored under
- <filename>/var/lib/iiim/le/<replaceable><LE_NAME></replaceable>/</filename>.
- </para>
- <para>
- For more information on the exact path and file location
- changes, please refer to Fedora IIIMF FAQ:
- </para>
- <para>
- <ulink
- url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Hotkeys</term>
- <listitem>
- <para>
- Trigger keys, such as
- <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
- used to activate Input Methods, are now configurable with
- the command-line tool <command>iiimf-le-tools</command>.
- This feature is only supported by GTK2 applications
- currently. For other applications using XIM the trigger
- key can be changed using an X resource. Refer to the
- IIIMF FAQ at <ulink
- url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>
- for more details on how to change trigger hotkeys.
- </para>
- <para>
- Note that the keyname refers to the X key symbol name. For
- example, if you want to activate with
- <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>,
- you
- need to specify '<Control>at' as the keyname not
- '<Control>@'.
- </para>
- <para>
- The per-user configuration of hotkeys does not work
- currently with &SEL; in enforcing mode due to lack of
- &SEL; policy. In this case, the hotkey can only be
- changed in the system-wide configuration.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Qt Support</term>
- <listitem>
- <para>
- A Qt immodule for <filename>iiimf</filename> is now
- included. This immodule works but lacks a status
- window and is considered experimental. Therefore, the default for Qt
- applications is to continue using XIM for IIMF input.
- </para>
- <para>
- If you wish to try the immodule in a Qt application, first
- install the <filename>iiimf-qt</filename> package, start
- the application, then click mouse button-3 in an input
- area and select <guimenuitem>iiimqcf</guimenuitem> from
- the <guisubmenu>Select Input Method</guisubmenu>' submenu.
- </para>
- </listitem>
- </varlistentry>
+ <varlistentry>
+ <term>Filepath Changes</term>
+ <listitem>
+ <para>
+ The name and locations of some files in the
+ <filename>iiimf</filename> packages have changed.
+ </para>
+ <para>
+ The IIIMF server has been renamed from
+ <filename>/usr/sbin/htt</filename> to
+ <filename>/usr/bin/iiimd</filename>, and the XIM bridge
+ client renamed from <filename>httx</filename> to
+ <filename>iiimx</filename>. The
+ <filename>init.d</filename> script name has not changed:
+ it is still called <filename>iiim</filename>. All the
+ global system configuration files are now located under
+ <filename>/etc/iiim/</filename>.
+ </para>
+ <para>
+ Language Engine (LE) developers should note that LE
+ modules and their data now live under
+ <filename>${libdir}/iiim/le/<filename><LE_NAME></filename>/</filename>,
+ while runtime data is stored under
+ <filename>/var/lib/iiim/le/<replaceable><LE_NAME></replaceable>/</filename>.
+ </para>
+ <para>
+ For more information on the exact path and file location
+ changes, please refer to Fedora IIIMF FAQ:
+ </para>
+ <para>
+ <ulink
+ url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Hotkeys</term>
+ <listitem>
+ <para>
+ Trigger keys, such as
+ <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>
+ used to activate Input Methods, are now configurable with
+ the command-line tool <command>iiimf-le-tools</command>.
+ This feature is only supported by GTK2 applications
+ currently. For other applications using XIM the trigger
+ key can be changed using an X resource. Refer to the
+ IIIMF FAQ at <ulink
+ url="http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html">http://www.fedora.redhat.com/projects/i18n/iiimf-faq.html</ulink>
+ for more details on how to change trigger hotkeys.
+ </para>
+ <para>
+ Note that the keyname refers to the X key symbol name. For
+ example, if you want to activate with
+ <keycombo><keycap>Ctrl</keycap><keycap>@</keycap></keycombo>,
+ you
+ need to specify '<Control>at' as the keyname not
+ '<Control>@'.
+ </para>
+ <para>
+ The per-user configuration of hotkeys does not work
+ currently with &SEL; in enforcing mode due to lack of
+ &SEL; policy. In this case, the hotkey can only be
+ changed in the system-wide configuration.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Qt Support</term>
+ <listitem>
+ <para>
+ A Qt immodule for <filename>iiimf</filename> is now
+ included. This immodule works but lacks a status
+ window and is considered experimental. Therefore, the default for Qt
+ applications is to continue using XIM for IIMF input.
+ </para>
+ <para>
+ If you wish to try the immodule in a Qt application, first
+ install the <filename>iiimf-qt</filename> package, start
+ the application, then click mouse button-3 in an input
+ area and select <guimenuitem>iiimqcf</guimenuitem> from
+ the <guisubmenu>Select Input Method</guisubmenu>' submenu.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
</section>
</section>
@@ -822,21 +844,21 @@
<!--
<section os="bogus">
<title>Supported Packages</title>
-
+
<para>*** Enter group description here ***</para>
-
+
</section>
-
+
<section os="bogus">
<title>System Tools</title>
-
+
<para>*** Enter group description here ***</para>
-
+
</section>
-
+
<section os="bogus">
<title>Text-based Internet</title>
-
+
<para>*** Enter group description here ***</para>
</section>
Index: development-tools.xml
===================================================================
RCS file: /cvs/docs/release-notes/FC4/development-tools.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- development-tools.xml 28 May 2005 16:10:31 -0000 1.2
+++ development-tools.xml 31 May 2005 01:09:54 -0000 1.3
@@ -1,3 +1,146 @@
+<!-- $Id: -->
+<!--
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+
+ <!ENTITY BOILERPLATE "This header makes editing XML easier" >
+ <!ENTITY DISTRO "DISTRO" >
+ <!ENTITY DISTROVER "DISTROVER" >
+
+]>
+-->
+<section id="sn-devel">
+ <title>
+ Development Tools
+ </title>
+ <section id="sn-devel-gcc">
+ <title>GCC Compiler Collection</title>
+ <para>
+ &DISTRO; &DISTROVER; has been built using <abbrev>GCC</abbrev> 4.0, which is included with the distribution.
+ </para>
+ <itemizedlist>
+ <title>Caveats</title>
+ <listitem>
+ <para>
+ <abbrev>GDB</abbrev> 6.1 or newer is needed to debug binaries unless compiled using the <parameter class="option">-fno-var-tracking</parameter> compilation option.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <parameter class="option">-fwritable-strings</parameter> option is no longer accepted.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ English-language diagnostic messages now use Unicode quotes; if you cannot read this, set your <envar>LC_CTYPE</envar> environment variable to "<filename>C</filename>" or change your terminal emulator.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <filename>specs</filename> file is no longer installed on most systems.
+ Ordinary users will not notice, but developers who need to alter the file can use the <parameter class="option">-dumpspecs</parameter> option to generate the file for editing.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Code Generation</title>
+ <listitem>
+ <para>
+ The <abbrev>SSA</abbrev> code optimizer is now included and brings with it better constant propagation; partial redundancy elimination; load and store code motion; strength reduction; dead storage elimination; better detection of unreachable code; and tail recursion by accumulation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Autovectorization is supported.
+ This technique achieves higher performance for repetitive loop code, in some circumstances.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Language Extentions</title>
+ <listitem>
+ <para>
+ A <computeroutput>sentinel</computeroutput> attribute has been added so that the compiler will now issue a warning if a function such as <function>execl(char *path, const char *arg, ...)</function>, which requires a <literal>NULL</literal> list terminator is missing the <literal>NULL</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <wordasword>cast-as-lvalue</wordasword>, <wordasword>conditional-expression-as-lvalue</wordasword>, and <wordasword>compund-expression-as-lvalue</wordasword> extentions have been removed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <computeroutput>#pragma pack()</computeroutput> semantics have been brought closer to those used by other compilers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Taking the address of a variable declared with the <computeroutput>register</computeroutput> modifier now generates an error instead of a warning.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Arrays of incomplete element types now generate an error.
+ This implies no forward reference to structure definitions.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The basic compiler, without any optimization (<parameter class="option">-O0</parameter>), has been measured as much as 25% faster in real-world code.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Libraries may now contain function-scope static variables in multi-threaded programs.
+ The <parameter class="option">-fno-threadsafe-statics</parameter> can be used by embedded developers to turn off this feature, but ordinary users should never do this.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Java</title>
+ <listitem>
+ <para>
+ To avoid naming conflicts: <filename>rmic</filename> is now <filename>grmic</filename>;
+ <filename>rmiregistry</filename> is now <filename>grmiregistry</filename>; and
+ <filename>jar</filename> is now <filename>fastjar</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <application>GCJ</application> compiler can now be used as a just-in-time (<abbrev>JIT</abbrev>) tool by using the <filename>gnu.jit</filename> facilities.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ More support of the <abbrev>AWT</abbrev> and <abbrev>SWING</abbrev> packages have been added.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>FORTRAN</title>
+ <listitem>
+ <para>
+ The <abbrev>GNU</abbrev> <application>FORTRAN 77</application> front end has been replaced by a new <application>FORTRAN 90/95</application> recognizer.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Eclipse Development Environment</title>
+ <listitem>
+ <para>
+ Eclipse 3.1M6 has been compiled as a native application.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The C Development Tool (<abbrev>CDT</abbrev>) has been included.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+
+
<!--
Local variables:
mode: xml
More information about the Fedora-docs-commits
mailing list