Lines Matching +refs:clang +refs:format +refs:fallback +refs:style
64 executable. But if ld is configured --enable-default-hash-style=gnu
68 "--hash-style=both" for these tests to cancel the effect of
69 --enable-default-hash-style=gnu, like [x86_64 mark-plt tests].
229 Pass --hash-style=both to ld for -z mark-plt tests to support linker
230 configured with --enable-default-hash-style=gnu.
232 * testsuite/ld-x86-64/mark-plt-1b-x32.d: Pass --hash-style=both
797 Note that, GAS instruction (ginsn) format does not support
1095 - gcc and clang (to trigger both the has_stderr_symbol true and false cases)
1167 input format is not recognized. This problem occurs in the function
1540 format; if the UnwindInfo references an invalid frame, then the
1852 Determine whether to output operands through the format
1853 of opcodes. When opc->format is an empty string, no extra
1905 While gcc propagates the printf attribute via the typedef, clang
2092 … gcc/gengtype-parse.cc:142:21: error: ‘%s’ directive argument is null [-Werror=format-overflow=]
2619 v3: Match file style for error-handling blocks, don't close
2923 sim: igen: fix format-zero-length warnings
3526 - there were two style violations.
3869 I did consider trying to have multi-line errors here, in the style
3902 gdb: don't try to style content in error calls
3915 I'm proposing to just remove the attempt to style error() output.
4248 options are supported on clang and gcc version 7 and newer.
4250 Patch has been tested on PowerPC with both gcc and clang.
4632 which uses some underlying c compiled code and adds some Fortran style DWARF
4701 and tls le insn format check.
5953 Fix build with clang 16
5954 clang 16 reports a missing declaration in new-op.cc. We believed
6198 Meanwhile, to unbreak the build, this commit switches from C99-style
6209 C99-style flexible array members are not standard C++ either.
6290 sim: iq2000: add fallback for exit syscall
6351 be four bytes in the DWARF 32-bit format and eight bytes in the DWARF
6352 64-bit format, while DWARF Version 2 specifies that such references have
6811 format, and instruction description.
6911 * format.c (io_reinit): Revert last change. Comment.
6967 However, clang doesn't use the CFA and instead relies on specifying when
6977 that handled this exact flaw in clang.
7701 * format.c (io_reinit): Free BFD_IN_MEMORY iostream.
9176 style commands. Just like with the previous commit, the COMPONENT can
9372 gdb.python/py-symtab.c with clang, I noticed that it was going wrong
9376 not true for clang compiled binaries.
9441 syslog (the format), so use %s as the static format instead since
10061 Fix this by running the test with --hash-style=sysv, and adjust
10066 * ld-aarch64/bti-far-3.d: Add --hash-style=sysv. Adjust
10314 output, will perform that output in a CLI style.
10803 format.
11098 standard approach that, presumably, clang supports.
11109 modified to support the GNU style long option syntax. Compatibility with
11318 The BPF assembler has been updated to follow the clang convention in
11325 The BPF assembler in clang uses semi-colon (;) to separate statements,
12273 i386: Use a fallback XSAVE layout for remote targets
12276 fallback XSAVE layout based on the included registers. This fallback
12280 This fallback layout is currently only used for remote targets since
12614 Fix building for the s390 target with clang
12697 * config/tc-s390.c: Add support to insert operand for format
12698 R_CP16_28, reusing existing logic for format V_CP16_12.
12733 wrong RR register format must be retained. Since the superfluous second
13726 gdbsupport/format.h:format_piece::format_piece.
14426 x86: conditionally hide object-format-specific functions
14610 and glibc, we also need to change it here to keep same style.
14620 and glibc, we also need to change it here to keep same style.
14927 where an older style declaration is converted to a newer
14928 initialization style. Add this change.
15359 * lexsup.c (ld_options): Ensure that the --format option is correctly recognised.
16933 supports the IBM double 128-bit floating point format and IEEE 128-bit
16934 format. The IBM double 128-bit floating point format uses two 64-bit
16936 floating point format stores the value in a single 128-bit vector-scalar
17855 gas: correct ignoring of C-style number suffixes
18147 immediate numbers as the last operand (ATT style).
18251 This matches clang's assembler behavior.
18407 [4] https://clang.llvm.org/cxx_status.html
18723 gdb/testsuite: add a clang XFAIL to gdb.python/py-watchpoint.exp
18733 gdb/testsuite: fix running gdb.python/py-explore-cc with clang
18735 failure. This was due to how clang mapped instructions to lines,
18739 add XFAILs for existing clang releases, if this gets solved in future
18838 Added format attribute to several gprofng functions.
18853 * libcollector/libcol_util.h: Added format attribute.
19094 the output -- should be styled using the "variable" style. This patch
19247 [gdb/symtab] Fix more style issues in v9 .gdb_index section support
19248 I noticed a few more style issues in commit 8b9c08eddac ("[gdb/symtab] Add
19285 This patch fixes the bug by applying the same style of fix that was
19504 therefore a vtable, use checked_static_cast instead of C-style cases to
19748 [gdb/symtab] Fix two style issues in gdb/dwarf2/index-write.c
19749 While reviewing gdb/dwarf2/index-write.c I noticed two style issues.
19759 [gdb/symtab] Fix style issues in v9 .gdb_index section support
19760 Post-commit review pointed out a few style issues in commit 8b9c08eddac
19831 don't attempt to style them again in case the file dropped out of the cache.
21967 styled_string (file_name_style.style (), filename));
22000 used, it would style the whole string. For these users I have
22001 switched to calling warning directly, this allows me to style the
22020 procfs.c, I noticed that we used a static errmsg buffer to format some
22025 message format that needed updating. In one case we gained an extra
23225 Also, while testing with CC_FOR_TARGET=clang, I found that
23226 'additional_flags=-Wl,-soname=${binsharedbase}' caused clang
23231 but I've done additional testing with CC_FOR_TARGET=clang as
23938 gdb.threads/pthreads.c, K&R -> ANSI function style
23939 gdb.threads/pthreads.c is declaring functions with old K&R style.
23940 This commit converts them to ANSI style.
24440 The new Synopsys ARCv3 ISA has a similar instruction format like
25426 compilers such as clang don't add debug information about stderr by
25686 a cumbersome repetition style. I noticed no other test-case uses gnateD, so
26105 UNSUPPORTED: gdb.dwarf2/dwzbuildid.exp: testname=fallback: compilation failed
26909 gdb/testsuite: Fix style.exp failures on targets without argc/argv support
26912 This causes problems for the regexps in the style.exp line-wrapping
27651 format." Tom further observed, "...it seems like it could result in an
28431 gdbserver: Fix style of struct declarations in i387-fp.cc
28564 standard format as queried from CPUID.
28618 "compact" format which uses an alternate layout, but existing OS's
28847 flavour may be incorrect. The format won't have changed but checking
28857 format.
28929 i386: warning: format ‘%u’ expects argument of type ‘unsigned int’,
28933 * i386-gen.c (process_i386_opcodes): Correct format string.
29279 testing with clang-15 from around 150 to 2, and correctly identifies
29290 anything, whereas clang assumes that the output is in %rax, and writes
29315 gdb/testsuite: fix testing gdb.reverse/step-reverse.exp with clang
29328 emitted when using clang.
29334 gdb/testsuite: fix gdb.reverse/solib-*.exp tests when using clang
29337 function. Not all compiles do this, one example being clang. To fix
29354 gdb/testsuite: Fix many errors in gdb.reverse with clang
29489 Regenerate target-delegates.c using this new style.
29577 style is to use explicit comparisons, so fix things up.
30089 uint64_t to match format string.
30091 use PRIx64 in format string.
30387 the entry count uleb is ridiculously large, and format attributes
31004 When building gdb with clang 15 and -std=c++20, I run into:
31021 When building gdb with clang 15 and -std=c++20, I run into:
31067 overflows the same way than the clang BPF assembler:
31987 * testsuite/lib/binutils-common.exp: Remove fallback prune_warnings.
31989 * testsuite/lib/gas-defs.exp: Remove fallback prune_warnings.
34084 [gdb/symtab] Fix data race on bfd::{cacheable,format}
34130 #0 bfd_check_format_matches bfd/format.c:323 (gdb+0x1492db4)
34131 #1 bfd_check_format bfd/format.c:94 (gdb+0x1492104)
34171 the process reading bfd::format, and
34175 The two bitfields bfd::cacheable and bfd::format share the same bitfield
34317 gdb/testsuite: Disable gdb.compile when testing with clang
34318 Attempting to test the gdb.compile with clang as the compiler results in
34695 Avoid the use of sprintf with a "%s" format string, replacing with
34742 * sysdep.h (stpcpy): Add fallback declaraion.
34799 /usr/include/bits/stdio2.h:30:10: error: null destination pointer [-Werror=format-overflow=]
35116 I also tend to think that the solib fallback behavior of
36220 mips64-openbsd -FAIL: Compact EH EB #7 with personality id and fallback FDE
36221 mips64-openbsd -FAIL: Compact EH EL #7 with personality id and fallback FDE
36222 mips64el-openbsd -FAIL: Compact EH EB #7 with personality id and fallback FDE
36223 mips64el-openbsd -FAIL: Compact EH EL #7 with personality id and fallback FDE
36609 comment character, which clang -S seems to use.
36938 bpf: format not a string literal
36980 instructions. The templates match the strings emitted by clang -S for
37552 bytes of the instruction in an implementation-defined format. This
37554 bytes as the format.
37780 and with gcc 7.5.0 and clang 13.0.1, for which we still consistently get:
38034 some more printf format problems when the host is 32-bit.
38038 * od-elf32_avr.c (elf32_avr_dump_mem_usage): Correct format
38045 * config/tc-d10v.c (find_opcode): Correct format specifier vs.
38731 first of any bss-style sections following. Most of the work here
38817 gdb: style filenames in separate debug file warnings
38833 std::vector, but now we tried to, when appropriate, style these
38842 The deferred_warnings class will style the deferred warnings only if
38844 so this should ensure we only style when expected.
39946 string, we're just constructing a printf format specifier for a hex
41307 * config/tc-riscv.c (validate_riscv_insn): Add 'l' as new format
41354 * riscv-dis.c (print_insn_args): Add 'l' as new format string
41424 (validate_riscv_insn): Add 'Wfv' as new format string directive.
41512 new format string directive 'Wfv'.
41533 LoongArch: gas: Fix code style issues
41616 it clutters the output, and the style is not regular assembly language
41621 style for immediates, like for example printing every immediate in
41651 opcodes/loongarch: style disassembled address offsets as such
41653 using the address offset style, and mark the memory access instructions'
41665 opcodes/loongarch: implement style support in the disassembler
41666 Update the LoongArch disassembler to supply style information to the
41764 Add details for the changes made from Version 1 to Version 2 of the format.
41766 Also add details about alignment in the SFrame format. A portion of the
41767 SFrame stack trace format has an unaligned on-disk representation. Add
41773 sframe: bfd: gas: ld: format bump to SFrame version 2
41775 in the format. Add information in the SFrame FDE to convey the size
41792 SFRAME_VERSION_2 format. If the input sections offered to the linker
41793 are not all in the SFRAME_VERSION_2 format, the linker issues an error
41797 section in SFRAME_VERSION_1 format is seen:
41803 format version, i.e., SFRAME_VERSION_2 is supported by the textual dump
41846 format is seen.
41865 format evolves.
41918 encoded in the format, as it may be different for each ABI.
41920 In SFrame Version 2 of the format, we will move towards encoding it
42023 format error when dynamic symbol table is used.
42326 Use uint8_t consistently for identifying ABI/arch in SFrame format.
42468 include/sframe.h (the SFrame binary format definition). This ties up
42813 format. However, my initial attempt at this did not work, because
42983 PR30536, ppc64el gold linker produces unusable clang-16 binary
43018 - the initial gdb prompt, and subsequent prompts generated by gdb_test-style
43624 Rewrite the paragraph to match the style of Tag_GNU_MIPS_ABI_FP text
43993 …$ clang-13: warning: argument unused during compilation: '-fdiagnostics-color=never' [-Wunused-com…
44454 bytes by libsframe. In next version of the SFrame format, we can encode
45169 (struct sframe_encoder_ctx): Likewise. Use same style of
45341 Within py-value.c we have a null-terminated C-style string. We then
45354 pushed to the inferior, and then read back as a C-style string, that
45518 We also add an extesion format of cftc2/cttc2/mftc2/mfthc2/mttc2/mtthc2:
45976 libsframe, and use it. Note that the SFrame format does not define such
46169 noticed that it implied that the format parameter is optional, which
46290 This commit adds a new format for the printf and dprintf commands:
46291 '%V'. This new format takes any GDB expression and formats it as a
46370 The new %V format solves all these problems: the string is computed
46372 actual arrays rather than pointers, and we can pass named format
46408 The use of '%V' will work just fine when dprintf-style is 'gdb'.
46410 When dprintf-style is 'call' the format string and arguments are
46416 any restrictions on the format string when operating in 'call' style.
46418 custom print format specifiers (maybe including '%V') so, I claim, it
46423 When dprintf-style is 'agent' then GDB does no support the use of
46425 process the format string and send the dprintf command to the remote,
46440 (gdb) set dprintf-style agent
46443 Unrecognized format specifier 'V' in printf
46447 This is exactly how GDB would handle any other invalid format
46462 (gdb) set dprintf-style agent
46465 Unrecognized format specifier 'Q' in printf
46900 (loongarch_elf_adjust_dynamic_symbol): Fix code format.
46903 (RELOCATE_CALC_PC32_HI20): Fix code format.
47224 Enhance objdump's --private option so that it can display the contents of PE format files.
47225 * od-pe.c: New file: Dumps fields in PE format headers.
47226 …c (od_vectors): Add objdump_private_desc_pe for PE format targets. (od_files): Add od-pe for PE fo…
48056 When testing gdb.arch/disp-step-insn-reloc.exp with clang in an x86_64
48100 The epilogue of set_point0 (11cf for clang, 401146 for gcc) is the main
48102 based on rbp, while clang adds the same constant to rsp that it
48530 I believe is the GDB style for warnings,
48555 Python Exception <class 'TypeError'>: function missing required argument 'style' (pos 1)
48559 Python Exception <class 'TypeError'>: Required argument 'style' (pos 1) not found
49237 the instruction fully styled. All of GDB's existing style
49254 the associated style that should be used to display the text. This
49282 instruction and gives this part the default text style. This is also
49288 libopcodes printing API (the API that doesn't pass style info), and
49289 GDB just prints everything using the default text style.
49373 parent. This lets us avoid a clang dependency in the test.
52037 target or object format.
52596 clang/llvm and is also used in inline asm templates in kernel code, so
54097 gdb: re-format Python code with black 23
54118 and format fields from the _Float128 typedef are copied to the long
54876 * format.c (struct bfd_preserve): Move some fields. Add
54898 * format.c (io_reinit): New function.
55083 older style, before SELF_CHECK was added. This patch switches them
55191 * format.c (struct bfd_preserve): Add iovec and iostream fields.
55263 Fix an attempt to allocate an overlarge amount of memory when decoding a corrupt ELF format file.
55399 build to fail. Use GDB's version which provides a fallback for this case.
55699 Clang with LTO (clang -flto) garbage collects unused global variables,
55705 RUNTESTFLAGS="CC_FOR_TARGET='clang -flto' CXX_FOR_TARGET='clang++ -flto'"
55733 format it with black:
55758 I'm now using 'O!' as the format specifier for the second argument,
55868 as the argument format for the function's value argument. This means
56115 gdb/testsuite: Default to assembler's preferred debug format in asm-source.exp
56116 The stabs debug format is obsolete and there's no reason to think that
56118 format wasn't set in asm-source.exp then leave it to the assembler to
57618 FRINT*, which share the same format.
57621 FCLAMP, SCLAMP and UCLAMP share the same format, although FCLAMP
57625 [BSU]MOP[AS] share the same format.
57640 BFDOT, FDOT and USDOT share the same instruction format.
57641 SDOT and UDOT share a different format. SUDOT does not
57646 SMLALL, SMLSLL, UMLALL and UMLSLL have the same format.
57678 from being treated as though they had an Advanced SIMD-style suffix
57748 SME2 adds a new format for the existing SVE predicate registers:
58169 a ZA-style index is missing the immediate offset.
59452 ld:watch.rs: file format not recognized; treating as linker script
59506 No functional change, just style fixes.
59907 casts are no longer needed, and where printf format strings or tests
60365 don't run into assertions or errors. If any of the checks fail, we fallback to
60649 relocated addresses again") changed the format of that command, but
63812 objdump's read_section is never used for bss-style sections, so to
64078 OBJF_REORDERED is set for nearly every object format. And, despite
64491 When building with clang 16, I see:
64519 When building with clang 16, we get:
64533 clang is right that the value -1 is invalid for the enum type we cast -1
65198 priority. By reading the format with the most detail last, we ensure it has
65888 …chew.c:1434:59: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 3 has type…
67397 opcodes: style m68k disassembler output
67831 style sections, because they typically don't occupy file space and
68287 opcodes: style m68k disassembler output
68342 more common format.
68367 - non-gcc producers (say, clang).
68415 - adding a fallback "amd64 epilogue" after the dwarf unwinders,
68532 - clang 4.0.1, 13.0.1
68593 This introduces a C++-style iterator that wraps the existing
69063 Therefore there shouldn't be any at the end of the format string.
69690 required "catstrif" (I considered adding FORTH-style if-else-then, but
69700 SYNOPSIS comes before DESCRIPTION. This is the more common style and
69786 I think this style of @node is a leftover from ancient times.
70023 These warnings come from clangd, so ultimately from one of the clang
70024 static analyzers (probably clang-tidy).
70843 fallback to "hipcc" so the compiler will be searched in the PATH. This
70844 removes the fallback to the hard-coded "/opt/rocm/bin" prefix.
71446 output in bss-style sections. I've updated all the msp430 tests that
71571 C-style [] array element/dimension accesses use history. For both Ada
71688 Use <climits> instead of <limits.h> and ditch local fallback definitions
72040 "Cause GDB to print structures in an indented format with one member per line"
72157 host pointer, so the test is better done in format-specific code.
72544 this code (the fallback loop -- the minsym lookup code is "ok") is
73096 The use of a narrow size to handle the mask CGEN in instruction format
73503 access it is to know whether it supports style escape code. We then
73637 SFrame format is meant for generating stack traces only.
73645 SFrame format is meant for generating stack traces only.
73659 SFrame format is meant for generating stack traces only.
73677 SFrame format is meant for generating stack traces only.
73685 SFrame format is meant for generating stack traces only.
73967 This is because the format of the "Cooked index in use" line changed
74101 …format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘std::__underly…
74112 The die_offset's underlying type is uint64, so use PRIx64 in the format
74299 instead of C-style casts, then the compiler won't let you cast
74775 descriptor for gdb_stderr, and, as a result, does not currently format
75354 either x86, x86_64, or aarch64, mainly by changing the comment style.
75930 When building GDB with clang 16, I got this,
75946 Tested by rebuilding on x86_64-linux with clang 16 and gcc 12.
76112 gcc 7.5.0 and clang 13.0.1.
78270 ctf: fix various dreadful typos in the ctf_archive format comments
78271 When defining a format it helps to a) get the endianness right when you
78338 HTML doc format is gdb/doc/gdb_html, rather than gdb/doc/gdb previously.
78493 style operand, resulting in the insertion of bogus (and otherwise
78566 https://learn.microsoft.com/en-us/windows/win32/debug/pe-format, and
79249 Also fix a memory leak, and make some style changes. I tend to read
79440 PR29972, inconsistent format specification in singular form
79442 * readelf.c (process_dynamic_section): Correct format string.
79549 output format.
79557 will print M::x, and using clang 16.0.0 prints N::x. Not only is this
79595 gdb/testsuite: Fix FAILs in gdb.linespec/cpcompletion.exp when using clang
79596 When using clang 16.0.0 to test gdb.linespec/cpcompletion.exp, I get 99
79599 overload3_function or anon_ns_function. This happens because clang is
80065 https://learn.microsoft.com/en-us/windows/win32/debug/pe-format, which
80163 because a call to the old-style method will not work with any
80164 converted architectures (whereas calling the new-style method is will
81234 (on-disk format). When the host is big-endian, the address of the
81895 Analogous to the above, in SFrame format V1, a bit is reserved in the SFrame
81950 XSAVES, unconditionally using compacted format, in turn effectively
82235 consistently using `%pA' and `%pB'. I'm no stickler for one style of
82239 format string to reduce translation work. elf64-ppc.c loses the
82246 * elf32-arm.c (arm_build_one_stub): Use consistent style in
82259 * ldlang.c (lang_add_section): Use consistent style in
82717 matches. It was quite limited in the style of message supported, only
82748 * format.c (print_warnmsg): New function.
82814 DW_CFA_GNU_window_save in the DWARF format.
82844 The behaviour of the mangled-RA info bit in SFrame format closely
83189 SFrame format is an unaligned on-disk format. As such, there are other blobs
83298 Tested on x86_64-linux, with gcc 4.8.5, 7.5.0 and clang 13.0.1.
83372 This commit changes the target_stack class from using a C style array
84682 future, when the format does evolve to make use of the currently unused
85558 commit objdump and GDB will style disassembler output.
85562 appropriate style through as needed. No additional tricks were
86065 double format, but the actual long double float format is:
86255 return format[0]->name;
87094 old style breakpoint based mechanism is still in place within glibc
87095 for that same event, then GDB will stop when using the old style
87100 probe, and the call to the old style breakpoint location were
88283 * objdump.c (load_specific_debug_section): Use PRIx64 format.
88285 Constify nm format array
88286 * nm.c (formats, format): Make const.
88528 * elfcomm.c (setup_archive): Update error format.
88580 gdb/testsuite: remove gcc restriction from gdb.dwarf2/clang-cli-macro.exp
88582 need to test for gcc in gdb.dwarf2/clang-cli-macro.exp and mark it as
88770 …20: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘ULONGEST’ {a…
88777 /vol/src/gnu/gdb/hg/master/local/gdb/sol-thread.c:416:40: note: format
89014 …rintf_chk’ may write a terminating nul past the end of the destination [-Werror=format-overflow=]
89055 clang, and should work on most, if not all, architectures.
89160 gdb/testsuite: fix gdb.compile/compile-ops.exp with clang
89176 # however, this isn't portable, because other compilers, such as clang,
89785 gdb: add "set style tui-current-position on|off", default to off
89907 * binutils/objdump.c: Add support for SFrame format.
90183 FDE are not representable in the SFrame unwind format.
90276 sframe.h: Add SFrame format definition
90277 The header sframe.h defines the SFrame format.
90279 The SFrame format is the Simple Frame format. It can be used to
90283 More details of the SFrame format are included in the documentation
91333 gdb/testsuite: allow for Clang style destructors on gdb.cp/m-static.exp
91368 gdb/testsuite: account for clang's nested destructor calls on gdb.cp/mb-ctor.exp
91390 gdb/testsuite: enable running gdb.cp/classes.exp with clang
91436 …Executing on host: clang++ -fdiagnostics-color=never -Wno-unknown-warning-option -c -g -o /hom…
91437 …builtin_spawn -ignore SIGHUP clang++ -fdiagnostics-color=never -Wno-unknown-warning-option -c -g -…
91680 Commit 041de3d73aa changed the output format of all error messages when
91961 if the function was printed using a C++ style mangled name. The current
92869 sim: adjust sim_hw options style
93228 we're able to read the /bin/sh format before failing at a diff
93313 running gdb.base/macro-source-path when using clang.
93688 introduced two places where a register name was passed as the format
93693 …utils-gdb/opcodes/arm-dis.c:6005:3: error: format not a string literal and no format arguments [-W…
93697 This commit fixes these by using "%s" as the format string.
93786 use register style or immediate style, and secondly, the 'r' and '#'
93794 well as the text style for things like ',' between the different
93812 the correct style.
93819 with the correct style. This will cover a large number of the
93828 then print using the base_style rather than using a fixed style.
93837 character changes to indicate a different style. In the first
93839 style, and in the second '%{I:...%}' changes base_style to
93840 immediate style.
93843 style group, this ensures that these characters are printed with
93844 the correct style rather than as text.
93846 The function decode_base_style maps from character to style. I've
93847 included a character for each style for completeness, though only
93899 The question then is how should the disassembler style the three cases
94077 gas/config/tc-i386.c:5039:16: error: too many arguments for format [-Werror=format-extra-args]
94153 gdb/testsuite: fix gdb.cp/converts.exp to run with clang
94164 gdb/testsuite: add XFAIL to gdb.cp/ptype-flags.exp when using clang
95449 both gcc and clang, so I've removed the SIM_WERROR_CFLAGS line from
95474 sim/ppc: fix for operator precedence warning from clang
95475 In the ppc simulator, clang was warning about some code like this:
95499 which silences the warning from clang, and is, I am guessing, what the
95718 When building GDB with clang and --enable-ubsan, I get:
95819 style fixes.
96240 RUNTESTFLAGS="CC_FOR_TARGET=clang" on all of the above expect for
96241 Fedora 28. The (old) version of clang available on F28 did not
96431 sim/ppc: fix warnings related to printf format strings
96437 sim/ppc: fixes for arguments to printf style functions
96439 where commit 182421c9d2ee addressed issues with printf format
96443 This commit is mostly either changing the format string to match the
96817 clang.
97125 When building with clang 15 on Ubuntu 20.04, I get:
97147 This is because clang 15 warns for something like this:
97516 set GDBFLAGS "${GDBFLAGS} -iex \"set style enabled off\""
97701 [gdb/testsuite] Fix gdb.base/infoline-reloc-main-from-zero.exp with clang
97702 With test-case gdb.base/infoline-reloc-main-from-zero.exp and clang I run into:
97704 gdb compile failed, clang-13.0: warning: -e main: 'linker' input unused \
97706 clang-13.0: warning: -Wl,-Ttext=0x00: 'linker' input unused \
97708 clang-13.0: warning: -Wl,-N: 'linker' input unused \
98232 implementation-defined manner, the result with format string containing
98241 sim/ppc: fixes for arguments to printf style functions
98246 arguments being the wrong size, or type, for the printf format being
98253 later on thinks the print format should change, please feel free to do
98514 Clang generates a warning if the format string of a printf-like function is
98518 To avoid this warning, this commit now uses vsnprintf to format error
98520 printf-style formatting.
98551 Clang generates a warning if the format string of a printf-like function is
98556 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98563 Clang generates a warning if the format string of a printf-like function is
98568 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98578 Clang generates a warning if the format string of a printf-like function is
98583 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98590 Clang generates a warning if the format string of a printf-like function is
98595 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98602 Clang generates a warning if the format string of a printf-like function is
98607 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98614 Clang generates a warning if the format string of a printf-like function is
98619 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98626 Clang generates a warning if the format string of a printf-like function is
98631 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
99090 Regression tested on x86_64, using both gcc and clang.
99487 This commit prints "Xl(...)" operand with dis_style_immediate style,
99504 The format string is changed accordingly.
99513 RISC-V: Print comma and tabs as the "text" style
99514 On the RISC-V disassembler, some separators have non-text style when
99515 printed with another word with another style.
99518 with the "text" style.
99541 "%x" format specifier requires unsigned type, not int. This commit
99547 the format specifier is "%x".
99551 RISC-V: Fix immediates to have "immediate" style
99558 "immediate" style. (riscv_disassemble_data): Likewise.
99748 opcodes/riscv: style csr names as registers
99750 given the text style, not the register style. This patch fixes this
99766 style. Add that support, which meant a rewrite of
99867 but that warning is only checked for clang, resulting in:
99944 inheritance is linked to the typedef, such as how clang does it,
100078 sum-file A test summary file with the format of those
100092 sum-file A test summary file with the format of those
100166 and the '+' is actually being marked in the error style. The error
100167 style is red and underlined.
100170 here is an x86-64 instruction in the 'intel' disassembly style, rather
100171 than the default att style. Clearly the Pygments module expects the
100196 error style, we instead give up on the styling attempt.
100199 text. First, Pygments is expecting att style disassembly, not the
100200 intel style that this example uses. Fortunately, Pygments also
100201 supports the intel style, all we need to do is use the 'nasm' lexer
100205 have '# COMMENT'. The "official" Intel disassembler style uses ';'
100232 that will format '#' and all other text on the line, as a comment,
100238 call into the Python code to style later instructions.
100242 correctly (with no underline). The existing style tests check that
100250 Clearly, the 'asm' lexer is OK with att style x86-64, but not OK with
100251 intel style x86-64, so who knows how well it will handle other random
100255 RISC-V, ARM, and X86-64 (att style) code, and it seemed fine, but I
100262 Pygments based styling code will just not style that one instruction.
100266 So, I think it is fine to keep using Pygments as a fallback mechanism
100338 This commit extends the gdb.base/style.exp test to cover disassembler
100344 using 'set style disassembler enabled off'. If libopcodes styling is
100683 opcode format, right?
100709 The --source option will enable the /s style source code display, this
100711 command options to get the now deprecated /m style source code
100785 This commit changes the format of 'disassemble /r' to match GNU
100901 gdb/testsuite: new test for -data-disassemble opcodes format
100903 new check validates the format of the 'opcodes' field, specifically,
100951 and reorganizes them, fixing coding style while improving coverage.
100971 C99's PRId64/PRIu64 format specifiers.
101046 While in some cases deriving an AT&T-style suffix from an Intel syntax
101178 [gdb/c++] Print destructor the same for gcc and clang
101191 and with clang++ (13.0.1):
101203 There's a difference in debug info between the two cases: in the clang case,
101229 - in the clang case, the loop is not entered and we print "void".
101237 such that we have the same for both gcc and clang:
101704 We were attempting to set a BSS style section contents.
101823 * format.c (clear_warnmsg): New function.
102034 Every format that might appear inside a generic archive needs to call
102041 be set up too, since pdb claims to be of format bfd_archive.
102045 (pdb_archive_p): Set up tdata for bfd_archive format.
102242 format specifier "Xs5@20".
102286 for Zicbom-style arguments in x-thead-cmo-fail.s.
102442 unfortunate, as clang does not emit epilogue information, so using clang
102445 this from other tests and have them working with clang.
102455 exit some functions. This caused some problems when using clang to test
102526 fix gdb.base/jit-elf.exp when testing with clang
102527 When using clang as the compiler for the target, gdb.base/jit-elf.exp
102570 When trying to test gdb.base/msym-bp-shl.exp using clang, it would have
102576 gdb/testsuite: fix testing gdb.base/skip-inline.exp with clang
102577 When testing gdb.base/skip-inline.exp using clang, we get failures
102578 when trying to step out of functions, since clang requires one fewer
102586 step 2 or step 3, so when we identify that clang is being used, those
102618 whereas clang links it to the last statement of the function. This
103097 that for all subsequent calls. (The object format has one set of
103232 I see this error when building with clang,
103235 gdb_bfd.c:1180:43: error: format string is not a string literal [-Werror,-Wformat-nonliteral]
103242 Tested on x86_64-linux with gcc 12 and clang 14.
103334 specific format specifiers. The BFD message strings that GDB stores
103356 Tested on x86_64-linux, with gcc 7.5.0 and clang 13.0.
103362 [gdb/tdep] Fix PowerPC IEEE 128-bit format arg passing
103592 Binutils: Readelf testcase failing with clang
103740 make clang tests fail like so:
103785 (gdb) PASS: gdb.base/dprintf.exp: call: fprintf: set dprintf style to call
103799 Add pdb archive format
103922 add xfails to gdb.base/complex-parts.exp when testing with clang
103923 clang doesn't add encoding to the name of complex variables, only says
103960 $ nm -A call-ar-st.clang | grep integer_
103971 fix gdb.base/access-mem-running.exp for clang testing
103975 update gdb.base/info-program.exp to not fail with clang
103977 stops, however it was still testing for a specific location. The clang
103980 patch the test works even with clang.
103984 gdb/testsuite: change gdb.base/nodebug.exp to not fail with clang
103992 clang:
104131 [gdb/testsuite] Fix gdb.dwarf2/dw2-dir-file-name.exp with clang
104132 When running test-case gdb.dwarf2/dw2-dir-file-name.exp with clang, we run
104148 to cause problem with clang, as documented in the comment for proc
104153 Tested on x86_64-linux, with both gcc 7.5.0 and clang 13.0.0.
104339 substitution must have a Makefile format but commit 171fba11ab27 used shell
104340 format "$srcdir/../bfd/development.sh".
104342 This commit fixes this issue by substituting "$srcdir" (shell format) to
104343 "$(srcdir)" (Makefile format). It preserves the dependency as Pedro
104629 In this commit, it adds following format:
104727 In this commit, it adds following format:
105385 names there is one for clang/icpx. Consider the following example
105399 'A' and 'C' makes clang emit a bunch of template tags without names:
105483 e.g. clang or gcc will make the disassemble command look like:
105485 >> clang --version
105486 clang version 10.0.0-4ubuntu1
105488 >> clang -O0 -g ./c.cpp
105522 >> clang -O0 -g ./c.c
105592 In practice, Microsoft style import libraries can contain
105597 considering it a Microsoft style import library, relax the criteria
105606 LLVM generates Microsoft style import libraries, and Rust builds
105645 clang in -std=c++17 mode (I did not test fully with clang in -std=c++11
106000 …declaration-after-statement -Wmissing-parameter-type -Wpointer-sign -Wold-style-declaration -Werro…
106098 This fixes the coding style of an old, preexisting function.
106268 bytes at the start of a file. If they are not the ELF format
106404 gdb, testsuite: Adapt gdb.base/callfuncs.exp for new clang warning.
106430 This patch adds the same option that already exists for clang for icx and
106518 As a fallback, I made a gdb.dwarf2 test with compiler-generated .S
106742 due to additional styling characters. Each style is encoded with 3
107324 Prefixed instruction format implementing SV. Funded by NLnet through EU
107537 a container format. This format has been added to elf based loongarch64 targets
107551 PASS: Check if efi app format is recognized
107554 tmpdir/loongarch64copy.o: file format pei-loongarch64
107564 [1] https://docs.microsoft.com/en-us/windows/win32/debug/pe-format
107640 converted to floating point format and stored in the register. Prior
107655 To fix this test I now print the float registers using the /f format
107806 ../../binutils-gdb/gdb/csky-linux-tdep.c:194:18: error: format ‘%ld’
107808 {aka ‘unsigned int’} [-Werror=format=]
108440 Following the same format as the implementation in ld:
108612 BFD_VMA_FMT can't be used in format strings that need to be
108649 with printing to a buffer in order to properly format output.
108719 …Fix a conflict between the linker's need to rename some PE format input libraries and the BFD libr…
108742 When building with clang 15, I got this,
108759 Tested by rebuilding on x86_64-linux with clang 15 and gcc 12.
109182 Write a direct configure test for the printf int64_t style instead.
109290 have observed some specific versions of gcc and clang generate. We want
109307 …$ make check TESTS="gdb.base/macro-source-path.exp" RUNTESTFLAGS="CC_FOR_TARGET=clang --target_boa…
109381 $ clang --version
109382 clang version 13.0.1
109383 $ clang test.c -gdwarf-5 -fdebug-macro
109449 we fail to do that, things still often work, because of a fallback: the
109533 $ clang --version
109534 clang version 13.0.1
109538 $ clang ./test.c -g3 -O0 -gdwarf-4
109570 $ clang ./test.c -g3 -O0 -gdwarf-5
109572 clang create two entries that refer to the same file but are of in a different
109594 producer clang version 13.0.1
109812 commit it is possible to have objdump style AArch64 disassembler
109814 patches are merged, GDB will also style the disassembler output.
109853 When aarch64_print_operand needs to format part of its output this can
109857 aarch64-dis.c we can spot these special style markers and use this to
109858 split the disassembler output up and apply the correct style to each
109863 functions formats a piece of text in a different style, 'register' and
109890 …Stop the linker from complaining about unrecognised DW_FORM-rnglistx and DW_FORM_loclistx format a…
110131 Refactored some code to use more c++-y style range for loops
110143 - Fixed non-gdb style conforming formatting
110295 then fallback to using ptrace to perform the operation.
110297 This is the specific hunk that removed the fallback:
110341 gdb: LoongArch: Fix code style issues
110342 Fix some code style issues suggested by Tom Tromey and Andrew Burgess,
110364 [gdb/testsuite] Fix gdb.opt/inline-small-func.exp with clang
110365 When running test-case gdb.opt/inline-small-func.exp with clang 12.0.1, I run
110370 clang-12.0: error: linker command failed with exit code 1 \
110631 gprofng: fix bug 29392 - Unexpected line format in summary file
110777 struct packed: Add fallback byte array implementation
110779 add a fallback standard-conforming implementation based on arrays.
110793 for mingw+clang. While adding that, I wrote some unit tests to make
110829 Attribute gcc_struct is not implemented in "clang -target
110905 gdb: handle dis_style_sub_mnemonic disassembler style
110911 opcodes: add new sub-mnemonic disassembler style
110913 I added a new disassembler style dis_style_sub_mnemonic, but forgot to
110914 add GDB support for this style. Fix this oversight in this commit.
110922 added an appropriate style.
110953 opcodes: add new sub-mnemonic disassembler style
110956 style. This will be used in cases like:
110966 This commit just adds the new style, and prepares objdump to handle
110967 the style. A later commit will add AArch64 styling, and will actually
110968 make use of the style.
110970 As this style is currently unused, there should be no user visible
111246 * sysdep.h (sbrk): Don't supply fallback declaration.
111864 …error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘bfd_vma…
112057 Re: opcodes/arc: Implement style support in the disassembler
112154 from the expected python code format.
112163 The format is documented in the Linux Kernel documentation [1].
112185 per mapped range. The format and documentation can be found in the Linux
112351 opcodes/arc: Implement style support in the disassembler
112352 Update the ARC disassembler to supply style information to the
112587 PowerPC: Add support for IEEE 128-bit format.
112595 made the default starting with GCC 12. The floating point format
112618 gdb.print_options. For the former, it lets Python code format values
112659 additional_flags-qtable=none and the clang optons
113045 When building with clang 15, I got this error:
113053 Tested by rebuilding on x86_64-linux with clang 15.
113574 mnemonics, etc, and can style these components differently.
113596 set/show style disassembler comment
113597 set/show style disassembler immediate
113598 set/show style disassembler mnemonic
113599 set/show style disassembler register
113602 styles to style some parts of the disassembler output. I have also
113605 set/show style disassembler address
113606 set/show style disassembler symbol
113610 set/show style address
113611 set/show style function
113614 disassembler related style settings. The 'address' style is used to
113615 style numeric addresses in the disassembler output, while the 'symbol'
113616 or 'function' style is used to style the names of symbols in
113681 gdb_disassembler::dis_asm_fprintf (void *stream, const char *format, ...)
113691 become an issue, how we style the output being written to STREAM will
114333 This commit adds disassembler style to the libopcodes s390
114336 added an appropriate style.
115012 opcodes/avr: Implement style support in the disassembler
115170 FAIL: gdb.base/early-init-file.exp: check startup version string has style \
116271 For clang compiled objects with dwarf-5, location list offset address dump
116730 I think these could all be replaced with a RAII style scoped_restore
116975 This commit fixes inconsistent error message format involving compressed
117243 (gdb) py print (gdb.Value (1230).format_string (format='t', nibbles=True))
117247 Note that the parameter nibbles is only useful if format='t' is also used.
117497 gprofng: fix build with -Werror=format-truncation
117501 * configure.ac: Remove -Wno-format-truncation.
117505 * common/hwctable.c: Fix -Werror=format-truncation errors.
117610 sim: fix BFD_VMA format arguments on 32-bit hosts [PR gdb/29184]
117611 Noticed format mismatch when attempted to build gdb on i686-linux-gnu
117615 error: format '%lx' expects argument of type 'long unsigned int',
117616 but argument 4 has type 'bfd_size_type' {aka 'long long unsigned int'} [-Werror=format=]
117624 While at it fixed format string for time-related types.
118019 gprofng: fix build with -Werror=format-security
118027 * src/Print.cc: Fix -Werror=format-security errors.
118453 (gdb) FAIL: gdb.base/style.exp: python import pygments
118480 operand displacements with inconsistent style, print_displacement() is
118482 for callers to pass in a style).
119227 part is some text and a style. Then, when we eventually print the
119229 correct style.
119238 As each operand is built up, piece be piece, we pass through style
119239 information. This style information is then encoded into the operand
119245 chunks at the style marker boundaries, with each chunk being printed
119246 with the correct style.
119248 For encoding the style information I use a single character, currently
119249 \002, followed by the style encoded as a single hex digit, followed
119302 The following commit changes the output format for the isel instruction on
119346 aarch64: Add fallback if ARM_CC_FOR_TARGET not set
119354 This commit adds a fallback. If ARM_CC_FOR_TARGET is not set, and
119501 format.
119926 Older gcc without __int128 support, as well as clang use an unsigned type, but with
119927 a warning. Interestingly, clang uses "unsigned long long" while gcc uses
119946 Test more interesting values, both in decimal and hex format, as well as
120699 failures in the test when running the test with CC_FOR_TARGET='clang'
120700 CXX_FOR_TARGET='clang' F90_FOR_TARGET='flang'"
121119 clang/flang ..). This commit enables GDB to detect C and Fortran
121199 format. Therefore, this needs adjustment to make more tests pass in the
122447 [gdb/testsuite] Fix gdb.opt/clobbered-registers-O2.exp with clang
122448 When running test-case gdb.opt/clobbered-registers-O2.exp with clang 12.0.1, I
122470 Adding the clang-specific attribute optnone in start_sequence does, but since
122472 test-case, and it would work only for clang and not other compilers that
122819 It should be fair to fallback to check DW_AT_linkage_name in case DW_AT_name
124344 - clang 8.0.1, 12.0.1
124373 There are assumptions in the test about the long double format
124382 Lastly, not every long double format has invalid values. Some formats
124396 - Use long double values appropriate for the long double format.
124685 gdb: LoongArch: Use GDB style to check readbuf and writebuf
124686 The GDB style is to write 'if (readbuf != nullptr)', and the same for
126715 Tested on x86_64-linux, with gcc 7.5.0, gcc 12.1 and clang 12.0.1.
126743 - GDB build with clang + glibc < 2.33.
126750 clang shows this error:
126752 make[2]: Entering directory '/home/smarchi/build/binutils-gdb-clang/gdbsupport'
127866 I noticed that these files failed to format with Black, because they use
127877 The format for printing the floating point values was changed by commit:
127897 the hexadecimal format for both big endian and little endian systems. The
127911 This fixes build breakage using clang with libc++ on FreeBSD where
128334 use the work around (two line) style output.
128764 gdb/testsuite: add binary testcases to py-format-string.exp
128767 binary format.
129347 …$ make check TESTS="gdb.base/jit-elf.exp" RUNTESTFLAGS="CC_FOR_TARGET=clang LDFLAGS_FOR_TARGET=-fu…
129349 …gdb compile failed, clang-13: warning: -Xlinker -Ttext-segment=0x7000000: 'linker' input unused [-…
129353 …$ make check TESTS="gdb.base/jit-elf.exp" RUNTESTFLAGS="CC_FOR_TARGET=clang LDFLAGS_FOR_TARGET=-fu…
129881 Building with clang++-14, I see:
130008 Fix this error when building with clang++-14:
130011 …/home/smarchi/src/binutils-gdb/gdb/complaints.c:130:65: error: format string is not a string liter…
130019 gdb: fix clang build failure in msymbol_is_mips
130020 Building with clang++-14, I see:
130044 * config.bfd (x86-haiku): Add i386_pei_vec as a selectable format.
131588 Right now it only handles clang specially (using -fdebug-macro) and
131593 gcc nor clang. After this patch, the tests will attempt to run (the -g3
131773 for loops instead of the old style look using reggroup_next. There
132134 its return type can only ever be one object format's type (and this
132608 I see there are lots of other cases of undocumented number format for error
133057 hipcc (i.e. clang). The problem is as follows: There's a function
133117 clang/clang++ (version 10.0.0) since at the time of writing GCC does not
133154 logging statements in auto-load.c to output style filenames. You can
133238 instead, the styled print routines just ignore the style and print the
133492 opcodes/i386: partially implement disassembler style support
133506 For now then, I think this commit should correctly style mnemonics,
133524 opcodes/riscv: implement style support in the disassembler
133525 Update the RISC-V disassembler to supply style information. This
133556 through an additional parameter indicating what style should be
134886 style, but there aren't many places to use this, so I just reused
135550 Add style-escape methods to ui_file
135772 gdb/testsuite: fix copy & paste error in gdb.python/py-format-address.exp
135773 The test gdb.python/py-format-address.exp, added in commit:
135996 multiple addresses, we change the code to use a callback style. Any
136820 This method takes an address, and returns a string with the format:
136847 In order to format an address for a different inferior.
137671 gdb: run black to format some Python files
138370 gprofng: Don't hardcode -Wno-format-truncation/-Wno-switch
138371 Use -Wno-format-truncation and -Wno-switch only if they are supported.
138375 AC_SUBST for -Wno-format-truncation.
138379 * src/Makefile.am (AM_CFLAGS): Replace -Wno-format-truncation
138452 of those notes. msgpack is a structured format, a bit like JSON, except
138517 the msgpack format.
138631 The ELF format for this architecture is documented here:
139355 Remove "auto-load:" from a format string passed to auto_load_debug_printf.
140193 bal.o: file format elf32-tradlittlemips
141587 Use target_pid_to_str to format the ptid and log the step and signo
141857 format, with only limited support in GDB.
141976 failure with clang that Simon pointed out.
142128 istarget * is used. This ends up being mostly style unindenting.
142608 set style disassembler enabled on|off
142609 show style disassembler enabled
142644 The only negative change with this commit is how we currently style
142657 using the `function` style, but instead, either GNU Source Highlight,
142665 However, if the user does `set style disassembler enabled off`, then
142932 would just behave as "next". This was noticeable in clang-compiled
142934 to this problem, as running gdb.base/watchpoint.exp with clang
143020 allow for the new output format.
143176 I have no info on the format of a "SUNPRO C++ Namespace" stab, so am
143247 in gdb.python/py-format-string.exp in an environment where styling
145057 gdb: fix some clang-tidy readability-misleading-indentation warnings
145059 thought I'd run clang-tidy with this diagnostic on all the files (that I
145297 FreeBSD x86: Remove fallback for detecting signal trampolines by address.
145302 December 2016. The fallback only works for native processes and would
145320 gdb/build: Fix Wpessimizing-move in clang build
145321 When building with clang, I run into an error:
145338 Build on x86_64-linux with clang 13.0.0.
146844 event_location uses the old C-style discriminated union approach.
146850 This patch removes the old-style EL_* macros from location.c. This
146953 bfd/elf64-ppc.c: fix clang -Wbitwise-instead-of-logical warning in ppc64_elf_check_init_fini
146954 I see this error with clang-14:
146999 This function has seen too many minimal change style edits.
147419 + * testsuite/d-demangle-expected: Add missing format for new test
147483 Because clang can provide helpful warnings with this flag.
147523 strict, is gcc check. As such, GCC is set to 'yes' for clang, which
147524 would mean the flag was not included for clang or gcc. The entire
147525 point of the original commit was to add this flag for clang, so
147530 GDB_COMPILER_TYPE to either 'gcc', 'clang', or 'unknown'. In future
147537 I've tested this with both gcc and clang and see the expected results,
147539 clang continues to use it.
148156 GNU linker for XCOFF format.
148186 ELF format.
148263 objdump, readelf: Emit "CU:" format only when wide output is requested
148271 changing options to get the wide format, so as to keep the name of the
148273 options for the gas test as I believe the "CU:" format is preferable.
148280 format only if wide output is requested.
148543 offset table) and data sections in a compact format:
149270 call is written in scheme, it's not the normal style throughout the
149272 wrote there declarations, and they use the first style too.
149274 The second style also has the drawback that index entries are added as
149279 make-parameter to use the first style.
149287 Finally, our current style for keyword arguments, appears to be:
149385 Fix a stack exhaustion bug parsing malicious STABS format debug information.
149444 which give a nice help style summary that lists all of the available
150373 sim: mips: clean up bad style/whitespace
151827 Documentation on the format will come in a subsequent patch.
151872 regardless a bad coding style. No functional change.
151997 …dwarf.c:11300:3: error: format not a string literal and no format arguments [-Werror=format-securi…
152232 gdb: re-format with black 21.12b0
152242 gdb: re-format with black 21.9b0
152445 bfd: fix -Wunused errors with clang 13+
152455 gcc won't warn, but clang will.
153085 Fix this, seen when building with clang 14:
153097 Fix these, seen when building with clang 14:
154085 errors and "FAIL: Check if efi app format is recognized". I also
154152 Tested on x86_64-linux, with both gcc and clang.
154157 When running test-case gdb.arch/i386-avx.exp with clang I ran into:
154183 Tested on x86_64-linux, with both gcc and clang.
154383 readability improvements") change the output format of "maint info
154435 - style filenames with the filename style
154766 gdb/testsuite: update tests looking for "DWARF 2" debug format
154768 debugformat field") changes the debug format string in "info source" to
155303 both gcc and clang.
155425 Compiled with DWARF 2 debugging format.
155437 Compiled with DWARF 5 debugging format.
155784 gdb/python: don't use the 'p' format for parsing args
155788 this method uses 'p' as an argument format specifier in a call to
155812 [gdb/testsuite] Fix gdb.base/style.exp with stub-termcap
155813 When running test-case gdb.base/style.exp with a gdb build using
155816 (gdb) PASS: gdb.base/style.exp: all styles enabled: frame when width=20
155818 (gdb) FAIL: gdb.base/style.exp: all styles enabled: set width 30
156066 https://github.com/riscv/riscv-v-spec/blob/master/vtype-format.adoc
156266 "/usr/src/debug/llvm13-13.0.0-1.2.x86_64/tools/clang/lib/AST/Decl.cpp"
156377 a single input & output format. ld is a bit better, but requires
156979 cli-style.c:set_style_enabled, and observed in tui-winsource.c,
157253 a container format. This format has been added to elf based aarch64 targets
157289 [1] https://docs.microsoft.com/en-us/windows/win32/debug/pe-format
158388 gdbsupport: make gdb_assert_not_reached accept a format string
158389 Change gdb_assert_not_reached to accept a format string plus
158392 Because the format string passed by the caller is prepended with a "%s:"
159051 …sprintf_chk' may write a terminating nul past the end of the destination [-Werror=format-overflow=]
159962 Fix demangle style usage info
160041 [gdb/build] Fix Wimplicit-exception-spec-mismatch in clang build
160042 When building with clang 13 (and -std=gnu++17 to work around an issue in
160061 Build on x86_64-linux, using gcc 7.5.0 and clang 13.0.0.
160125 temp.o: file format elf32-littleriscv
160147 temp.o: file format elf32-littleriscv
161044 libctf: add CTF format specification
161047 complete insofar as it goes: it documents format v3 (the current
161111 define already, so no need for the fallback here.
161254 readelf: Make DT_PREINIT_ARRAYSZ's output style match DT_INIT_ARRAYSZ
162138 sim: ppc: clean up printf format handling
162140 printf format specifier whether it be a 64-bit type or a pointer.
162155 printf format specifier whether it be a 64-bit type or a pointer.
162273 Tweak the if indentation & brace style to avoid ambiguous warnings.
162871 [gdb/testsuite] Fix assembly comments in gdb.dwarf2/clang-debug-names.exp.tcl
162874 clang-debug-names-debug.S:72: \
162883 Fix this by using the /* ... */ comment style instead:
162885 $ sed -i 's% #\([^"]*\)%/*\1 */%' clang-debug-names.exp.tcl
162949 clang compiler:
162961 initialized (or used), then clang emits the symbol "p_union" which
164210 ignoring the problem of mis-optimising old-style __tls_get_addr calls
165606 * format.c (bfd_reinit): Clear build_id.
165994 Following 2 test points are failing with clang compiler
166006 Tested on x86_64-linux with gcc and clang.
166617 sim: ppc: fallback when ln is not available [PR sim/18864]
166619 fallback logic to the run->psim build code to handle those.
166696 …:44: error: format '%lx' expects argument of type 'long unsigned int', but argument 4 has type 'ui…
166745 style option arguments, use one leading "option" parameters, used as a
167545 DWARF revision 5 changes .debug_line format quite extensively, and in
167645 I made a mistake in the previous patch. Adjust the format string to
167656 …/Users/smarchi/src/binutils-gdb/gdb/darwin-nat.c:1175:19: error: format specifies type 'unsigned l…
167720 Invalid format: [z|h|s|zvm|x][0-9a-z]+[0-9]+p
168240 format string.
168251 format never read by any extant libctf. We can detect such CTF dicts by
168273 function index symtypetab sections if this is an old-format
168336 original (Solaris ld requires #-style comments), and making another
168357 Libtool needs to get BSD-format (or MS-format) output out of the system
168368 BSD-format output, even though the test never actually got anything
168375 also flags forcing BSD-format output. Worse yet, one such "user" is
168377 nor specifies any BSD-format flags. So platforms needing BSD-format
169438 [gdb/testsuite] Use early-out style in gdb.base/break-probes.exp
169543 This patch changes gdb to use the 'highlight' style on the "XXX" text
169872 binary format. Before the patch, the disassembler output is invalid
169971 info section which now share the same format of their contents - an array
170416 but with clang, I run into:
170460 Tested on x86_64-linux with gcc and clang-7 and clang-12.
171039 Also fix indentation style and long lines, remove outdated question/answer
171231 Then I ran with clang and found another FAIL, fix by updating the regexp.
171233 Tested on x86_64-linux with gcc-4.8.5, gcc-7.5.0, gcc-11.2.1, clang-7.0.1 and
171234 clang-12.0.1.
171534 sim: ppc: align format string settings with common code
171536 build errors for mingw targets. Turning format warnings on triggers
172143 Compiler support for gcc and clang is in progress, see e.g.:
172708 Unrecognized format specifier 'j' in printf
172718 also reported by John Baldwin, using a clang that uses libc++.
172967 This style is somewhat annoying because if you want to specify the last
173194 this style of use fragile.
173326 [gdb] Fix 'not in executable format' error message
173330 "0x7ffc87bfc8d0s": not in executable format: \
173331 file format not recognized
174030 * testsuite/gas/csky/v2_float_part2.d: Following the new format.
174683 AMX-BF16 insns. While not part of the IEEE standard, the format is
174711 format (dec vs hex).
174737 (where output sizes currently differ depending on input format).
175171 This patch is more about the style of bounds checking we ought to use,
175359 Print it using the same format used for TARGET_WAITKIND_STOPPED and
175381 The ptid_t::to_string method was introduced recently, to format a ptid_t
176442 gdb/testsuite: fix gdb.base/info-macros.exp with clang
176449 The current state is problematic when testing with CC_FOR_TARGET=clang,
176454 compiler is clang.
176499 complaint by inverting the condition and using a clang-compiled binary,
176540 * s390-opc.c (INSTR_SIY_RD): New instruction format.
176542 * s390-opc.txt: Change instruction format of lpswey to SIY_RD.
176850 [gdb/testsuite] templates.exp to accept clang++ output
177500 code style.
178931 and with clang-10, I have instead:
178946 tree_check (lines 40-43) (so, with the clang trace we get that right).
178960 Tested on x86_64-linux, with gcc-8, gcc-9, gcc-10, gcc-11, clang-8, clang-10
178961 and clang-12.
179908 gas/write.c provides a fallback TC_VALIDATE_FIX_SUB define that can be
181011 Tested on x86_64-linux, with both gcc 7.5.0 and clang 12.0.1.
181650 libiberty.h can provide a fallback declaration, the necessary configure
181674 * testsuite/gas/all/overflow.l Change expected output format.
182251 clang" I see: