History log of /freebsd-10.0-release/contrib/gcc/dwarf2out.c
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
# 259065 07-Dec-2013 gjb

- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

# 256281 10-Oct-2013 gjb

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation


# 244792 28-Dec-2012 pfg

gcc: avoid generating negative values to DW_AT_byte_size.

The previous change was actually a NOP because size is
unsigned and compilers are dumb.

Submitted by: Christoph Mallon
MFC after: 1 week


# 244776 28-Dec-2012 pfg

gcc: avoid generating negative values to DW_AT_byte_size.

There is a bug in gcc (GCC/35998) where dwarf reports
sizes of unsigned -1 (0xffffffff).

On NetBSD this generated a faulty CTF entry which then
caused a segfault in ctfmerge. The issue was worked
around in NetBSD's Dtrace but since the issue originated
in gcc, it seems reasonable to fix it here.

Upstream gcc has been slow to react to this issue and
the author that submitted the patch is not interested
in licensing the change to us, so I did an independent
workaround for the issue.

MFC after: 1 week


# 220150 29-Mar-2011 mm

Upgrade of base gcc and libstdc++ to the last GPLv2-licensed revision
(rev. 127959 of gcc-4_2-branch).

Resolved GCC bugs:
c++: 17763, 29365, 30535, 30917, 31337, 31941, 32108, 32112, 32346,
32898, 32992
debug: 32610, 32914
libstdc++: 33084, 33128
middle-end: 32563
rtl-optimization: 33148
tree-optimization: 25413, 32723
target: 32218

Tested by: pointyhat (miwi)
Obtained from: gcc (gcc-4_2-branch up to rev. 127959)
PR: gnu/153298, gnu/153959, gnu/154385
MFC after: 1 month


# 195815 21-Jul-2009 bms

Output DWARF debug information for global 'using' declarations, instead
of just blowing up. A very similar change to this exists which is
GPLv3 licensed, this is my own change.

This problem was triggered by running the Boost regression tests.

See also: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31899
Reviewed by: luigi
Approved by: re (kib)


# 171826 14-Aug-2007 kan

This commit was generated by cvs2svn to compensate for changes in r171825,
which included commits to RCS files with non-trunk default branches.


# 171825 14-Aug-2007 kan

GCC 4.2.1 release.


# 169689 18-May-2007 kan

GCC 4.2.0 release.


# 146895 03-Jun-2005 kan

Gcc 3.4.4 release.


# 132718 28-Jul-2004 kan

Gcc 3.4.2 20040728.


# 122180 07-Nov-2003 kan

Gcc 3.3.3 20031106.


# 119256 22-Aug-2003 kan

Gcc 3.3.1-release.


# 117395 11-Jul-2003 kan

Gcc 3.3.1-pre as of 2003-07-11.


# 102780 01-Sep-2002 kan

Gcc 3.2.1-prerelease from the FSF anoncvs repo gcc-3_2-branch on 1-Sep-2002 00:00:01 EDT.


# 96489 13-May-2002 obrien

Cause CVS to sync up checked out source bases with Gcc 3.1 bits after
the repo surgery to cut out the abortive Gcc 2.9[67] imports.


# 96263 09-May-2002 obrien

Gcc 3.1.0 pre-release from the FSF anoncvs repo on 9-May-2002 15:57:15 EDT.


# 90075 01-Feb-2002 obrien

Enlist the FreeBSD-CURRENT users as testers of what is to become Gcc 3.1.0.
These bits are taken from the FSF anoncvs repo on 1-Feb-2002 08:20 PST.


# 72562 17-Feb-2001 obrien

Enlist the FreeBSD-CURRENT users as testers of GCC 2.95.3 Release Candidate #3


# 70635 03-Jan-2001 obrien

Enlist the FreeBSD-CURRENT users as testers of GCC 2.95.3 Release Candidate #1


# 52284 16-Oct-1999 obrien

Virgin import of the GCC 2.95.1 compilers


# 50397 26-Aug-1999 obrien

Virgin import of gcc from EGCS 1.1.2