1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright 2013 David Malcolm <dmalcolm@redhat.com>
Copyright 2013 Red Hat, Inc.
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301
USA
-->
<analysis>
<!-- test of an instance document containing non-ASCII characters -->
<metadata>
<!-- a made-up generator name consisting of 8
"U+2620 SKULL AND CROSSBONES" characters: -->
<generator name="☠☠☠☠☠☠☠☠"/>
</metadata>
<results>
<!--
$ gcc -Wsign-compare -c non-ascii-example.c
non-ascii-example.c: In function ‘foo’:
non-ascii-example.c:50:9: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
The same, with LANG=ja_JP.UTF-8
$ LANG=ja_JP.UTF-8 gcc -Wsign-compare -c non-ascii-example.c
non-ascii-example.c: 関数 ‘foo’ 内:
non-ascii-example.c:50:9: 警告: 符号付きと符号無しの整数式の間での比較です [-Wsign-compare]
-->
<issue>
<!-- "comparison between signed and unsigned integer expressions" -->
<message>符号付きと符号無しの整数式の間での比較です</message>
<notes>This note embeds the substring "文字化け" (aka "mojibake")
Here are some Unicode "Box Drawing" characters:
first ─> n0 ─> n1 ─> ... ─> nN ┐
A │
└────────────────────────────┘
</notes>
<location>
<!--
In theory the filename could contain non-ASCII characters
However, doing it within our SCM repository opens us up to
dealing with filesystem encodings on all the different
filesystems that the code might be checked out on.
-->
<file given-path="examples/non-ascii-example.c"/>
<!--
(Python 3 supports full unicode for identifiers; can GCC do the
same for C?). For now, let's turn "foo" upside-down
(the "f" is actually a
"LATIN SMALL LETTER DOTLESS J WITH STROKE (U+025F)")
-->
<function name="ooɟ"/>
<point line="50" column="9"/>
</location>
</issue>
</results>
</analysis>
|
