.debug_frame not generated by ARC gas

2016-06-16 Thread Vineet Gupta
Hi,

ARC Linux has an in-kernel dwarf unwinder which has historically consumed
.debug_frame. The kernel is built with -gdwarf-2 and 
-fasynchronous-unwind-tables
toggles which until recently used to generate both .debug_frame and .eh_frame -
latter being discarded by the kernel linker script.

With a recent ARC gas change to support asm cfi psuedo-ops - dwarf info is now
generated by gas and NOT gcc. But more importantly, we no longer get 
.debug_frame
with above 2 toggles. If we drop -fasynchronous-unwind-tables then .debug_frame 
is
generated.

So here are the questions:
1. Is it OK to drop -fasynchronous-unwind-tables toggle and still assume that
"precise" unwind info will be generated (as mentioned in gnu documentation)
2. If not, how do we coax gas to generate .debug_frame even in presence of
-fasynchronous-unwind-tables

Thx,
-Vineet


gcc-6-20160616 is now available

2016-06-16 Thread gccadmin
Snapshot gcc-6-20160616 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160616/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6-branch 
revision 237543

You'll find:

 gcc-6-20160616.tar.bz2   Complete GCC

  MD5=b02e88d9e7cf1688332c2933e22510d5
  SHA1=fe33dd0ed4654dd27e9f8163f767905dc08a3d93

Diffs from 6-20160609 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-6
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.