OpenCores
URL https://opencores.org/ocsvn/openrisc_me/openrisc_me/trunk

Subversion Repositories openrisc_me

[/] [openrisc/] [trunk/] [gnu-src/] [gcc-4.2.2/] [NEWS] - Blame information for rev 486

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 38 julius
This file contains information about GCC releases which has been generated
2
automatically from the online release notes.  It covers releases of GCC
3
(and the former EGCS project) since EGCS 1.0, on the line of development
4
that led to GCC 3. For information on GCC 2.8.1 and older releases of GCC 2,
5
see ONEWS.
6
 
7
======================================================================
8
http://gcc.gnu.org/gcc-4.2/index.html
9
 
10
                           GCC 4.2 Release Series
11
 
12
   October 7, 2007
13
 
14
   The  [1]GNU project and the GCC developers are pleased to announce the
15
   release of GCC 4.2.2.
16
 
17
   This release is a bug-fix release, containing fixes for regressions in GCC
18
   4.2.1 relative to previous releases of GCC.
19
 
20
Release History
21
 
22
   GCC 4.2.2
23
          October 7, 2007 ([2]changes)
24
 
25
   GCC 4.2.1
26
          July 18, 2007 ([3]changes)
27
 
28
   GCC 4.2.0
29
          May 13, 2007 ([4]changes)
30
 
31
References and Acknowledgements
32
 
33
   GCC used to stand for the GNU C Compiler, but since the compiler supports
34
   several other languages aside from C, it now stands for the GNU Compiler
35
   Collection.
36
 
37
   A  list  of [5]successful builds is updated as new information becomes
38
   available.
39
 
40
   The  GCC  developers would like to thank the numerous people that have
41
   contributed new features, improvements, bug fixes, and other changes as well
42
   as test results to GCC. This [6]amazing group of volunteers is what makes
43
   GCC successful.
44
 
45
   For additional information about GCC please refer to the [7]GCC project web
46
   site or contact the [8]GCC development mailing list.
47
 
48
   To obtain GCC please use [9]our mirror sites, one of the [10]GNU mirror
49
   sites, or [11]our SVN server.
50
 
51
   Please send FSF & GNU inquiries & questions to [12]gnu@gnu.org. There are
52
   also [13]other ways to contact the FSF.
53
 
54
   These pages are maintained by [14]the GCC team.
55
 
56
 
57
    For questions related to the use of GCC, please consult these web pages and
58
    the [15]GCC manuals. If that fails, the [16]gcc-help@gcc.gnu.org mailing
59
    list might help.
60
    Please send comments on these web pages and the development of GCC to our
61
    developer mailing list at [17]gcc@gnu.org or [18]gcc@gcc.gnu.org. All of
62
    our lists have [19]public archives.
63
 
64
   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
65
   Boston, MA 02110, USA.
66
 
67
   Verbatim copying and distribution of this entire article is permitted in any
68
   medium, provided this notice is preserved.
69
   Last modified 2007-10-07 [20]Valid XHTML 1.0
70
 
71
References
72
 
73
   1. http://www.gnu.org/
74
   2. http://gcc.gnu.org/gcc-4.2/changes.html
75
   3. http://gcc.gnu.org/gcc-4.2/changes.html
76
   4. http://gcc.gnu.org/gcc-4.2/changes.html
77
   5. http://gcc.gnu.org/gcc-4.2/buildstat.html
78
   6. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
79
   7. http://gcc.gnu.org/index.html
80
   8. mailto:gcc@gcc.gnu.org
81
   9. http://gcc.gnu.org/mirrors.html
82
  10. http://www.gnu.org/order/ftp.html
83
  11. http://gcc.gnu.org/svn.html
84
  12. mailto:gnu@gnu.org
85
  13. http://www.gnu.org/home.html#ContactInfo
86
  14. http://gcc.gnu.org/about.html
87
  15. http://gcc.gnu.org/onlinedocs/
88
  16. mailto:gcc-help@gcc.gnu.org
89
  17. mailto:gcc@gnu.org
90
  18. mailto:gcc@gcc.gnu.org
91
  19. http://gcc.gnu.org/lists.html
92
  20. http://validator.w3.org/check/referer
93
======================================================================
94
http://gcc.gnu.org/gcc-4.2/changes.html
95
 
96
                           GCC 4.2 Release Series
97
                      Changes, New Features, and Fixes
98
 
99
Caveats
100
 
101
     * GCC no longer accepts the -fshared-data option. This option has had no
102
       effect in any GCC 4 release; the targets to which the option used to
103
       apply had been removed before GCC 4.0.
104
 
105
General Optimizer Improvements
106
 
107
     * New  command-line options specify the possible relationships among
108
       parameters  and  between  parameters and global data. For example,
109
       -fargument-noalias-anything specifies that arguments do not alias any
110
       other storage.
111
       Each language will automatically use whatever option is required by the
112
       language standard. You should not need to use these options yourself.
113
 
114
New Languages and Language specific improvements
115
 
116
     * [1]OpenMP is now supported for the C, C++ and Fortran compilers.
117
     * New command-line options -fstrict-overflow and -Wstrict-overflow have
118
       been added. -fstrict-overflow tells the compiler that it may assume that
119
       the program follows the strict signed overflow semantics permitted for
120
       the language: for C and C++ this means that the compiler may assume that
121
       signed overflow does not occur. For example, a loop like
122
      for (i = 1; i > 0; i *= 2)
123
 
124
       is presumably intended to continue looping until i overflows. With
125
       -fstrict-overflow, the compiler may assume that signed overflow will not
126
       occur, and transform this into an infinite loop. -fstrict-overflow is
127
       turned   on   by   default   at  -O2,  and  may  be  disabled  via
128
       -fno-strict-overflow. The -Wstrict-overflow option may be used to warn
129
       about cases where the compiler assumes that signed overflow will not
130
       occur. It takes five different levels: -Wstrict-overflow=1 to 5. See the
131
       [2]documentation for details. -Wstrict-overflow=1 is enabled by -Wall.
132
     * The new command-line option -fno-toplevel-reorder directs GCC to emit
133
       top-level functions, variables, and asm statements in the same order
134
       that they appear in the input file. This is intended to support existing
135
       code which relies on a particular ordering (for example, code which uses
136
       top-level  asm statements to switch sections). For new code, it is
137
       generally  better  to  use  function  and variable attributes. The
138
       -fno-toplevel-reorder option may be used for most cases which currently
139
       use -fno-unit-at-a-time. The -fno-unit-at-a-time option will be removed
140
       in some future version of GCC. If you know of a case which requires
141
       -fno-unit-at-a-time which is not fixed by -fno-toplevel-reorder, please
142
       [3]open a bug report.
143
 
144
  C family
145
 
146
     * The  pragma  redefine_extname will now macro expand its tokens for
147
       compatibility with SunPRO.
148
     * In the next release of GCC, 4.3, -std=c99 or -std=gnu99 will direct GCC
149
       to  handle  inline  functions as specified in the C99 standard. In
150
       preparation for this, GCC 4.2 will warn about any use of non-static
151
       inline functions in gnu99 or c99 mode. This new warning may be disabled
152
       with the new gnu_inline function attribute or the new -fgnu89-inline
153
       command-line option. Also, GCC 4.2 and later will define one of the
154
       preprocessor macros __GNUC_GNU_INLINE__ or __GNUC_STDC_INLINE__ to
155
       indicate the semantics of inline functions in the current compilation.
156
     * A  new  command-line option -Waddress has been added to warn about
157
       suspicious uses of memory addresses as, for example, using the address
158
       of a function in a conditional expression, and comparisons against the
159
       memory address of a string literal. This warning is enabled by -Wall.
160
 
161
  C++
162
 
163
     * C++ visibility handling has been overhauled.
164
       Restricted  visiblity  is propagated from classes to members, from
165
       functions to local statics, and from templates and template arguments to
166
       instantiations, unless the latter has explicitly declared visibility.
167
       The visibility attribute for a class must come between the class-key and
168
       the name, not after the closing brace.
169
       Attributes are now allowed for enums and elaborated-type-specifiers that
170
       only declare a type.
171
       Members  of  the anonymous namespace are now local to a particular
172
       translation unit, along with any other declarations which use them,
173
       though they are still treated as having external linkage for language
174
       semantics.
175
     * The (undocumented) extension which permitted templates with default
176
       arguments  to  be bound to template template parameters with fewer
177
       parameters has been removed. For example:
178
        template