[Bug rust/22251] &str type should be built in

[Bug rust/22251] &str type should be built in

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=22251

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at sourceware dot org   |tromey at sourceware dot org

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
Have a patch.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/22251] &str type should be built in

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=22251

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=cd61a1453e685a763bd91b3795a58edd3d9b4f40

commit cd61a1453e685a763bd91b3795a58edd3d9b4f40
Author: Tom Tromey <tom@tromey.com>
Date:   Wed May 17 09:07:50 2023 -0600

    Special case "&str" in Rust parser

    "&str" is an important type in Rust -- it's the type of string
    literals.  However, the compiler puts it in the DWARF in a funny way.
    The slice itself is present and named "&str".  However, the Rust
    parser doesn't look for types with names like this, but instead tries
    to construct them from components.  In this case it tries to make a
    pointer-to-"str" -- but "str" isn't always available, and in any case
    that wouldn't yield the best result.

    This patch adds a special case for &str.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=22251
    Reviewed-By: Andrew Burgess <aburgess@redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug rust/22251] &str type should be built in

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=22251

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |14.1

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
Fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.