On 06/26/2018 03:26 AM, Florian Weimer wrote:
> I'm looking at ways to speed up _Unwind_Find_FDE when libgcc is running
> on top of glibc. I have something (at the design level, with some of
> the code written) which allows me to get a pointer to the
> PT_GNU_EH_FRAME segment in memory in a lock-f
Snapshot gcc-6-20180627 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20180627/
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
On Wed, 27 Jun 2018 at 17:28, Eric Gallager wrote:
> At first I was going to wonder if it wasn't necessary to remain
> compatible with old versions of GCC that don't support -Wabi=11, but
> then I reread the part about this happening with the just-built GCC,
> so if that warning is only ever used w
On 6/27/18, Marek Polacek wrote:
> On Wed, Jun 27, 2018 at 08:53:48AM -0700, Steve Ellcey wrote:
>> Are other people building GCC seeing these messages during the build:
>>
>> cc1plus: warning: -Wabi won't warn about anything [-Wabi]
>> cc1plus: note: -Wabi warns about differences from the most up
On Wed, Jun 27, 2018 at 08:53:48AM -0700, Steve Ellcey wrote:
> Are other people building GCC seeing these messages during the build:
>
> cc1plus: warning: -Wabi won't warn about anything [-Wabi]
> cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
> which is also used by
Are other people building GCC seeing these messages during the build:
cc1plus: warning: -Wabi won't warn about anything [-Wabi]
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC
Your mail is off-topic on this list, it would be appropriate on the
gcc-help list, or in Bugzilla if you want to report a bug.
On Wed, 27 Jun 2018 at 11:27, Csaba Raduly wrote:
>
> #include
> #include
> #include
>
> using srange = boost::sub_range;
>
> void func(srange) // by value
> {}
>
> in
#include
#include
#include
using srange = boost::sub_range;
void func(srange) // by value
{}
int main()
{
std::string kitty{"meow"};
srange hello{kitty};
srange const& helref = hello;
func(hello);
func(helref); // line 17
return 0;
}
$ g++ -v
gcc version 9.0.0 2018
