public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Jason Merrill <jason@redhat.com>,
	       "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
	       gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: RFA (libstdc++): PATCH to implement C++17 over-aligned new
Date: Sun, 11 Sep 2016 09:56:00 -0000	[thread overview]
Message-ID: <20160911095520.GB29332@redhat.com> (raw)
In-Reply-To: <20160911093847.GA29332@redhat.com>

On 11/09/16 10:38 +0100, Jonathan Wakely wrote:
>On 11/09/16 09:08 +0200, Christophe Lyon wrote:
>>On 10 September 2016 at 08:59, Christophe Lyon
>><christophe.lyon@linaro.org> wrote:
>>>On 9 September 2016 at 23:20, Jason Merrill <jason@redhat.com> wrote:
>>>>On Thu, Sep 8, 2016 at 7:06 AM, Jonathan Wakely <jwakely@redhat.com> wrote:
>>>>>On 08/09/16 09:10 +0200, Marc Glisse wrote:
>>>>>>
>>>>>>Do we want a generic fallback implementation (similar to
>>>>>>gcc/config/i386/gmm_malloc.h)? A windows version with _aligned_malloc /
>>>>>>_aligned_free would also be possible.
>>>>>
>>>>>Making it work for MinGW would be nice.
>>>>
>>>>OK, this is what I'm checking in; could someone test it on MinGW?
>>>>
>>>>Jason
>>>
>>>Hi Jason,
>>>
>>>I'm seeing problems on arm*linux: the tests aligned-new[1235].C fail to link:
>>>aligned-new5.C:(.text+0x14): undefined reference to `operator
>>>new(unsigned int, std::align_val_t)'
>>>
>>>
>>>On aarch64*-elf and arm-eabi (using newlib), I'm seeing:
>>>/gccsrc/libstdc++-v3/libsupc++/new_opa.cc:66: undefined reference to
>>>`aligned_alloc'
>>>
>>>Am I missing something in my setup?
>>>
>>
>>I'm seeing an additional problem: to GCC build is broken after this
>>commit for target arm-none-eabi (using default cpu):
>>/home/christophe.lyon/src/GCC/sources/gcc-fsf/reg-240062/libstdc++-v3/libsupc++/new_opant.cc:
>>In function 'void* operator new(std::size_t, std::align_val_t, const
>>std::nothrow_t&)':
>>/home/christophe.lyon/src/GCC/sources/gcc-fsf/reg-240062/libstdc++-v3/libsupc++/new_opant.cc:33:3:
>>error: '__try' was not declared in this scope
>>  __try
>>  ^~~~~
>>/home/christophe.lyon/src/GCC/sources/gcc-fsf/reg-240062/libstdc++-v3/libsupc++/new_opant.cc:37:11:
>>error: expected primary-expression before '...' token
>>  __catch(...)
>>          ^~~
>>/home/christophe.lyon/src/GCC/sources/gcc-fsf/reg-240062/libstdc++-v3/libsupc++/new_opant.cc:37:3:
>>error: '__catch' was not declared in this scope
>>  __catch(...)
>>  ^~~~~~~
>>/home/christophe.lyon/src/GCC/sources/gcc-fsf/reg-240062/libstdc++-v3/libsupc++/new_opant.cc:41:1:
>>warning: no return statement in function returning non-void
>>[-Wreturn-type]
>>}
>>^
>>/home/christophe.lyon/src/GCC/sources/gcc-fsf/reg-240062/libstdc++-v3/libsupc++/new_opant.cc:30:26:
>>warning: unused parameter 'sz' [-Wunused-parameter]
>>operator new(std::size_t sz, std::align_val_t al, const std::nothrow_t&)
>>                         ^~
>>/home/christophe.lyon/src/GCC/sources/gcc-fsf/reg-240062/libstdc++-v3/libsupc++/new_opant.cc:30:47:
>>warning: unused parameter 'al' [-Wunused-parameter]
>>operator new(std::size_t sz, std::align_val_t al, const std::nothrow_t&)
>>                                              ^~
>>make[4]: *** [new_opant.lo] Error 1
>>make[4]: Leaving directory
>>`/home/christophe.lyon/src/GCC/builds/gcc-fsf-reg-240062/obj-arm-none-eabi/gcc3/arm-none-eabi/libstdc++-v3/libsupc++'
>
>Hmm, I'm not sure why it's not failing on all targets, [...]

OK, I see why. <bits/exception_defines.h> gets included indirectly at
the end of <exception> via

#if (__cplusplus >= 201103L) && (ATOMIC_INT_LOCK_FREE > 1)
#include <bits/exception_ptr.h>
#include <bits/nested_exception.h>
#endif

The condition isn't true for all targets.

So including it explicitly in new_opant.cc is the right fix.

  reply	other threads:[~2016-09-11  9:55 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08  7:10 Jason Merrill
2016-09-08  8:32 ` Marc Glisse
2016-09-08 11:18   ` Jonathan Wakely
2016-09-09 21:40     ` Jason Merrill
2016-09-10  7:03       ` Christophe Lyon
2016-09-10 10:14         ` Marc Glisse
2016-09-10 10:35           ` Jonathan Wakely
2016-09-11  9:14         ` Christophe Lyon
2016-09-11  9:55           ` Jonathan Wakely
2016-09-11  9:56             ` Jonathan Wakely [this message]
2016-09-11 10:20             ` Christophe Lyon
2016-09-11 12:09               ` Jonathan Wakely
2016-09-13 13:04         ` Szabolcs Nagy
2016-09-10 10:14       ` Jonathan Wakely
2016-09-11  7:09       ` Andreas Schwab
2016-09-12 21:13         ` Jason Merrill
2016-09-13  8:41           ` Christophe Lyon
2016-09-13 12:37           ` Andreas Schwab
2016-09-13 12:54             ` Jason Merrill
2016-09-13 13:18               ` Andreas Schwab
2016-09-13 13:21                 ` Jason Merrill
2016-09-14 12:13                   ` Andreas Schwab
2016-09-14 16:11                     ` Christophe Lyon
2016-09-14 16:37                       ` Jason Merrill
2016-09-15 10:00                         ` Rainer Orth
2016-09-15 12:23                           ` Christophe Lyon
2016-09-15 20:09                             ` Jason Merrill
2016-09-16  7:12                               ` Rainer Orth
2016-09-16  8:15                                 ` Christophe Lyon
2016-09-16  9:14                                 ` Jonathan Wakely
2016-09-16  9:51                                   ` Marc Glisse
2016-09-16 11:12                                     ` Jonathan Wakely
2016-09-16 13:13                                       ` Jonathan Wakely
2016-09-16 13:17                                         ` Rainer Orth
2016-09-16 18:19                                         ` Jonathan Wakely
2016-09-12 14:15       ` Rainer Orth
2016-09-12 16:19         ` Jonathan Wakely
2016-09-12 18:57           ` Jason Merrill
2016-09-14 12:11           ` Rainer Orth
2016-09-08 11:00 ` Jonathan Wakely
2017-11-24 14:26 ` Marc Glisse
2017-11-29 21:23   ` Jason Merrill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160911095520.GB29332@redhat.com \
    --to=jwakely@redhat.com \
    --cc=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).