[Bug preprocessor/60368] New: ICE on not unibyte character in execution character set

[Bug preprocessor/60368] New: ICE on not unibyte character in execution character set

[rmansfield at qnx dot com]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 5878 bytes --]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60368

            Bug ID: 60368
           Summary: ICE on not unibyte character in execution character
                    set
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: preprocessor
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rmansfield at qnx dot com

$ cat ~/ice.c
#include <stdio.h>

int main(int argc, char *argv[])
{
    printf("hello world\n");
}


$ ./xgcc -v
Using built-in specs.
COLLECT_GCC=./xgcc
Target: x86_64-unknown-linux-gnu
Configured with: ../configure --enable-languages=c++,lto
Thread model: posix
gcc version 4.9.0 20140228 (experimental) [trunk revision 208224] (GCC)

$ ./xgcc -B. -fexec-charset=UTF-16 ~/ice.c
/home/ryan/ice.c: In function ‘main’:
/home/ryan/ice.c:9:0: internal compiler error: character 0xa is not unibyte in
execution character set

 ^
0x5d0b64 c_cpp_error(cpp_reader*, int, int, unsigned int, unsigned int, char
const*, __va_list_tag (*) [1])
    ../../gcc/c-family/c-common.c:9713
0xf16cea cpp_diagnostic
    ../../libcpp/errors.c:63
0xf16e36 cpp_error(cpp_reader*, int, char const*, ...)
    ../../libcpp/errors.c:78
0xf0e15a cpp_host_to_exec_charset(cpp_reader*, unsigned int)
    ../../libcpp/charset.c:804
0x5d0c63 c_common_to_target_charset(long)
    ../../gcc/c-family/c-common.c:9731
0x618a8e init_target_chars
    ../../gcc/builtins.c:13529
0x63367c init_target_chars
    ../../gcc/builtins.c:13527
0x63367c fold_builtin_printf
    ../../gcc/builtins.c:13315
0x637a79 fold_builtin_1
    ../../gcc/builtins.c:10705
0x62d9a3 fold_builtin_n
    ../../gcc/builtins.c:11102
0x63b895 fold_call_expr(unsigned int, tree_node*, bool)
    ../../gcc/builtins.c:11233
0x7f8009 gimplify_call_expr
    ../../gcc/gimplify.c:2286
0x7ed947 gimplify_expr(tree_node**, gimple_statement_base**,
gimple_statement_base**, bool (*)(tree_node*), int)
    ../../gcc/gimplify.c:7419
0x7f2296 gimplify_stmt(tree_node**, gimple_statement_base**)
    ../../gcc/gimplify.c:5341
0x7f2f9f gimplify_bind_expr
    ../../gcc/gimplify.c:1079
0x7ede8e gimplify_expr(tree_node**, gimple_statement_base**,
gimple_statement_base**, bool (*)(tree_node*), int)
    ../../gcc/gimplify.c:7645
0x7f2296 gimplify_stmt(tree_node**, gimple_statement_base**)
    ../../gcc/gimplify.c:5341
0x7f3b09 gimplify_body(tree_node*, bool)
    ../../gcc/gimplify.c:8555
0x7f40e6 gimplify_function_tree(tree_node*)
    ../../gcc/gimplify.c:8708
0x6827b7 analyze_function
    ../../gcc/cgraphunit.c:649
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
>From gcc-bugs-return-445103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:10:27 2014
Return-Path: <gcc-bugs-return-445103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2757 invoked by alias); 28 Feb 2014 19:10:26 -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 2344 invoked by uid 48); 28 Feb 2014 19:10:22 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58678] [4.9 Regression] pykde4-4.11.2 link error (devirtualization too trigger happy)
Date: Fri, 28 Feb 2014 19:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58678-4-TQeZHRFs7s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58678-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: 2014-02/txt/msg02860.txt.bz2
Content-length: 1219

http://gcc.gnu.org/bugzilla/show_bug.cgi?idX678

--- Comment #19 from Jason Merrill <jason at gcc dot gnu.org> ---
I think it would make sense to suppress speculative devirtualization of a
DECL_ARTIFICIAL destructor, since that seems to be the problem here (and in
53808).  I think it's better to address this in devirtualization rather than
inlining so that an explicitly non-virtual call (e.g. from a destructor to a
base destructor) can still be inlined.

This doesn't address user-declared inline destructors, including those declared
as Þfault in the class body, but I'm comfortable saying that people who do
that should expect it to be inlined, whereas people who don't mention a
destructor at all can be forgiven for being surprised that we inline the
destructor they weren't thinking about.

I think I'm also inclined to allow non-speculative devirtualization, since in
cases where we know the type of the object we presumably have access to the
vtable in the current shared object.

Do you have an opinion about whether this restriction should apply to virtual
operator= as well?  I think that's much less likely to occur, but it probably
makes most sense to handle it the same way.

Testing a patch now.

[Bug preprocessor/60368] ICE on not unibyte character in execution character set

[rmansfield at qnx dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60368

--- Comment #1 from Ryan Mansfield <rmansfield at qnx dot com> ---
Maybe a WONTFIX. It's not clear to me why cpp_host_to_exec_charset is using 
CPP_DL_ICE for this instead of CPP_DL_ERROR

[Bug preprocessor/60368] ICE on not unibyte character in execution character set

[pinskia at gcc dot gnu.org]

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Dup of bug 81050.

*** This bug has been marked as a duplicate of bug 81050 ***