stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <>
Subject [jira] Resolved: (STDCXX-687) [gcc] use string __builtins
Date Mon, 11 Feb 2008 21:34:08 GMT


Martin Sebor resolved STDCXX-687.

    Resolution: Fixed

Committed in [r620615|].
Will merge to 4.2.1 and close if nothing breaks in nightly builds.

> [gcc] use string __builtins
> ---------------------------
>                 Key: STDCXX-687
>                 URL:
>             Project: C++ Standard Library
>          Issue Type: Sub-task
>    Affects Versions: 4.1.2, 4.1.3, 4.1.4, 4.2.0
>            Reporter: Martin Sebor
>            Assignee: Martin Sebor
>             Fix For: 4.2.1
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> The following gcc builtin equivalents of the C string functions would be useful in the
implementation of std::char_traits:
> __builtin_memcpy: char_traits::copy()
> __builtin_memcmp: char_traits::compare()
> __builtin_memmove: char_traits::move()
> __builtin_memset: char_traits::assign()
> __builtin_strlen: char_traits::length()
> Unfortunately, as of gcc 4.2.2, there is no builtin equivalent of memchr() which is used
in char_traits::find(), so using the builtins won't let us get away from #including the <cstring>
header to bring in the declaration of the function (thus reducing namespace pollution caused
by all the other symbols declared in the header).
> There also are no builtins for the wide character counterparts of any of these functions
(such as wmemcmp or wcslen).
> See the following page for more details:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message