std::type_info comes from the runtime. Someone needs to implement it for
our to be provided.

Having the compiler identify the ABI means that the runtime has a concrete
manner to determine what ABI is being requested. On certain platforms it
is not possible to determine the ABI without having the compiler indicate
to you which is in use.

Furthermore, this would allow verification that the user code and the
runtime agree on the ABI itself.

On Sun, Jan 8, 2017 at 11:24 AM Jens Maurer <Jens.Maurer_at_[hidden]> wrote:

> On 01/08/2017 05:19 PM, Saleem Abdulrasool wrote:
>
> > Although the differences in PMFs could require different behaviors, I
> think that encouraging users to use more portable code is preferable.
>
>
>
> Agreed on the latter part.
>
>
>
> > As to examples of the runtime changing would be the implementation of
> std::type_info.
>
>
>
> Ok, but that comes with your compiler or with your standard library,
> anyway, right?
>
>
>
> So, where's the point of having a standard-looking ABI macro?
>
>
>
> Jens
>
>