public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/65124] New: wstring_convert not recognised as a template class.
Date: Thu, 19 Feb 2015 17:14:00 -0000	[thread overview]
Message-ID: <bug-65124-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65124

            Bug ID: 65124
           Summary: wstring_convert not recognised as a template class.
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: iains at gcc dot gnu.org

the following code snippet:

#include <codecvt>

namespace lldb_private {

    class Editline
    {
    private:
     std::wstring_convert<std::codecvt_utf8<wchar_t>> m_utf8conv;

     };
}

g++ -std=c++11 -S 

gives:
wstring-convert.cpp:8:11: error: ‘wstring_convert’ in namespace ‘std’ does not
name a template type
      std::wstring_convert<std::codecvt_utf8<wchar_t>> m_utf8conv;

on both linux and darwin.
>From gcc-bugs-return-477817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 19 17:14:53 2015
Return-Path: <gcc-bugs-return-477817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15837 invoked by alias); 19 Feb 2015 17:14:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15745 invoked by uid 48); 19 Feb 2015 17:14:49 -0000
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65109] [5 Regression] r220674 causes FAIL: gcc.target/powerpc/ppc64-abi-1.c execution test
Date: Thu, 19 Feb 2015 17:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status
Message-ID: <bug-65109-4-4o3AkJrHIO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65109-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-02/txt/msg02150.txt.bz2
Content-length: 1386

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide109

Richard Henderson <rth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P2
             Status|ASSIGNED                    |NEW

--- Comment #2 from Richard Henderson <rth at gcc dot gnu.org> ---
The testcase is simply buggy.

The beginning of fididisdsid contains a volatile asm (inside save_parms),
which is assumed to be scheduled immediately after the prologue.  Except
that didn't happen, and there's nothing in the testcase to make sure that
it must happen.

.L.fididisdsid:
        mflr 0
        std 31,-8(1)
        std 30,-16(1)
        std 0,16(1)
        stdu 1,-144(1)
        mr 31,1
        std 9,112(31)             <-- s.dd spilled to stack
        ld 6,264(31)              <-- load t.a
        ld 9,256(31)              <-- load t.dd
        ori 2,2,0
        lfd 0,112(31)
#APP
 # 294 "z.c" 1                    <-- Start of save_parms
        ld 11,gparms@got(2)

I have no idea why the compiler should choose to spill s.dd in favor
of t.dd, but certainly it is within it's rights to do so.

In my opinion, this sort of testing can only be done via dedicated
assembly entry points, and not asm within the function body.

Not mine, and not P1 either.


             reply	other threads:[~2015-02-19 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 17:14 iains at gcc dot gnu.org [this message]
2015-02-19 17:15 ` [Bug libstdc++/65124] " iains at gcc dot gnu.org
2015-02-19 18:47 ` redi at gcc dot gnu.org

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=bug-65124-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).