I am in the process of ending official maintainance for the GCC 4.3
branch. The GCC 4.3 branch is now considered closed and a final
release will be done from its head now.
Please do not apply any changes to the 4.3 branch from now on.
Status
==
GCC 4.6.1 release has been uploaded to ftp.gnu.org and gcc.gnu.org,
the branch is now open again under the normal rules, accepting regression
bugfixes and documentation fixes. The release will be announced
after mirrors get some time to grab the new release.
Tentatively, GCC 4.6.2 i
Dear all,
during the GCC Gathering I realized during the LTO debugging symbol
discussion that gfortran does not generate debug information for the OOP
features (cf. PR 49475).
The first issue to solve is which DWARF information one should generate.
I have only very limited knowledge of DWARF
Hi,
I put the scripts that we are using to test performance regressions of GCC on
git://repo.or.cz/gcc-perf-regression-tester.git and I've wrote a small
intro page
http://gcc.gnu.org/wiki/PerfRegressionTester in the hope that these scripts will
be useful to other people.
I've been thinking to ins
Joern Rennecke writes:
> - make INIT_CUMULATIVE_ARGS allocate using garbage-collected memory.
> That would require that each target provides appropriately
> typedefed / GTY-ed
> definitions. Multi-target operation would also require an index inside
> cumulative_args_t to decide during GC w
It's my pleasure to announce that, also based on the recommendation of
Eric Botcazou as the current maintainer in that area¹, the steering
committee is appointing Richard Sandiford as an additional RTL optimizers
maintainer.
Please adjust the MAINTAINERS file accordingly, and Happy Hacking,
Ri
Quoting Ian Lance Taylor :
Joern Rennecke writes:
- make INIT_CUMULATIVE_ARGS allocate using garbage-collected memory.
That would require that each target provides appropriately
typedefed / GTY-ed
definitions. Multi-target operation would also require an index inside
cumulative_args_t
