Lines Matching +refs:clang +refs:rename +refs:binary
1095 - gcc and clang (to trigger both the has_stderr_symbol true and false cases)
1905 While gcc propagates the printf attribute via the typedef, clang
3997 sim: ppc: rename local ALU SIGNED64 macros
4248 options are supported on clang and gcc version 7 and newer.
4250 Patch has been tested on PowerPC with both gcc and clang.
4411 sim: ppc: rename igen max_insn_bit_size
5825 Easiest way around it is to rename the per-substep vars as needed as
5836 Delete redundant decls, and rename conflicting vars.
5889 Remove duplicate nested variable declarations, rename some to avoid
5953 Fix build with clang 16
5954 clang 16 reports a missing declaration in new-op.cc. We believed
6299 rename syscall since we can't rename files that have been removed.
6967 However, clang doesn't use the CFA and instead relies on specifying when
6977 that handled this exact flaw in clang.
7868 gdb: rename gdbarch_pseudo_register_write to gdbarch_deprecated_pseudo_register_write
9005 Naturally my first thought was to sort the table and use a binary search to
9372 gdb.python/py-symtab.c with clang, I noticed that it was going wrong
9376 not true for clang compiled binaries.
10482 --rename-section.
11009 and rename to riscv_is_valid_mapping_symbol.
11098 standard approach that, presumably, clang supports.
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,
11487 binary. And we do .... except for the index.
11505 a smaller binary, which is quicker to load, and for which we could
11551 With a patched GDB, generating a gdb-index for the _same_ GDB binary,
12614 Fix building for the s390 target with clang
13854 Consider a binary with an erroneous size of the .dynamic section:
13862 This binary causes a segfault in GDB. GDB is trying to write the .dynamic
14288 - in particular, remove get_thread_arch_regcache, and rename
15216 I've tested this with a simple test binary compiled with the mingw
15217 toolchain on a Linux host. After compiling the binary and splitting
15365 changed gas/config.in to rename USE_E_MIPS_ABI_O32 to USE_EF_MIPS_ABI_O32
17456 dev machine other than ARM, after acquiring the test binary.
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
19325 gdb: rename struct so_list to shobj
19527 gdb: rename lm_info_base to lm_info
19814 The issue was discovered while building a 64 bit ld binary to be
20295 (nto_create_output_section_statements): rename nto_after_open
20589 Make remote_async_inferior_event_token private (rename to
20800 In my testing (a binary with about 1.8GB worth of DWARF data) this change brings
22618 In preparation to the SME support patches, rename the SVE-specific files to
22654 such as binary search when validating register names.
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
24016 and c-exp.c.tmp. Just include it in the list of symbols we rename.
25426 compilers such as clang don't add debug information about stderr by
25549 up when debugging a particular i686 built binary, which just happened
25551 debugging the same binary built for x86-64 appeared to work just fine.
25553 Using valgrind on the failing GDB binary pointed straight to the cause
26071 gdb/doc: rename "x86 Architecture-specific Issues" section to "x86"
27359 x86: rename CpuPCLMUL
27481 Add these two methods, rename the field to m_bitsize to make it pseudo
27506 Add these two methods, rename the field to m_artificial to make it
29109 expectations adjusted (the generated binary doesn't change).
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
29908 exit_inferior_silent are all equivalent, so rename exit_inferior_1 to
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:
32875 binary shrinks by almost a third (the generated source code shrinks by
34317 gdb/testsuite: Disable gdb.compile when testing with clang
34318 Attempting to test the gdb.compile with clang as the compiler results in
36609 comment character, which clang -S seems to use.
36707 The change to use -nostdlib and rename main to _start was originally added
36980 instructions. The templates match the strings emitted by clang -S for
37331 change the name of the binary that was created. Should be easy, I
37337 generated binary, and the test still works.
37691 application binary and shared library binaries. GDB currently opens the
37780 and with gcc 7.5.0 and clang 13.0.1, for which we still consistently get:
38019 binary. Help out the user, and only warn about debug overflows.
39221 Merge and rename to tui_border_kind_translate_corner.
40066 "rename" conflicts with a function of that name, which gcc from that
40259 of course those tests that run a target binary. Compiling and linking
40572 and, when these are found, should rename these sections using some
42468 include/sframe.h (the SFrame binary format definition). This ties up
42641 Since the test binary is compiled with debug information, fix by changing
42983 PR30536, ppc64el gold linker produces unusable clang-16 binary
43766 * bfd.c (_input_error_msg): Make global and rename to..
43993 …$ clang-13: warning: argument unused during compilation: '-fdiagnostics-color=never' [-Wunused-com…
44877 = bfd_openr (expanded_fname.get (), "binary");
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
48647 expressions to 32 bits - any involvement of binary expressions (which
48665 Give backends a chance to see these, just as they can see binary ones.
49373 parent. This lets us avoid a clang dependency in the test.
52171 since af31506c we only use the binary tree when section sorting is
52596 clang/llvm and is also used in inline asm templates in kernel code, so
53381 ld -r -b binary xx.dat -o xx.o
53478 - Remove auto_language, rename auto_or_unknown_language to
55699 Clang with LTO (clang -flto) garbage collects unused global variables,
55705 RUNTESTFLAGS="CC_FOR_TARGET='clang -flto' CXX_FOR_TARGET='clang++ -flto'"
57778 There is not a binary distinction between mnemonics that have
58990 gdb: move displaced_step_dump_bytes into gdbsupport (and rename)
60560 Insert two stubs in a BTI enabled binary when fixing long calls: The
62061 Convert this specific case to binary + (i.e. 0 + <register>). (An
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
64867 (get_relocs): Adjust for struct rename. Don't call bfd_fatal
67110 <syscall name="rename" groups="file"/>
68367 - non-gcc producers (say, clang).
68532 - clang 4.0.1, 13.0.1
70007 gdb/dwarf2: rename some things, index -> gdb_index
70023 These warnings come from clangd, so ultimately from one of the clang
70024 static analyzers (probably clang-tidy).
71939 x86: move (and rename) opcodespace attribute
73267 generates an ELF binary for the host architecture, containing another
73268 ELF binary with the device code. The ELF for the device can be
73845 replacing the build-id based .debug file with the stripped binary and
73865 gdb/dwarf: rename cooked_index_vector to cooked_index
73873 gdb/dwarf: rename cooked_index to cooked_index_shard
73874 I propose to rename cooked_index_vector and cooked_index such that the
75221 gdb/testsuite/dap: rename dap_read_event to dap_wait_for_event_and_check
75841 gdb/testsuite: rename test source file to match test script
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.
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
79726 rename it to the less collision-prone `xtensa_rmap` name.
79923 binary (especially in a non-optimized GDB) can take time. But then it
80557 gdb/copyright.py: Adjust following rename of sim/ppc/ppc-instructions...
81133 sim: mips: rename "igen" generation mode to "single"
81139 this generation mode. So rename the set of rules from "igen" to
81164 sim: mips: rename multi_flags to igen_itable_flags
81166 for merging the itable logic among all ports, rename "multi_flags" to a
81543 Also rename the file to standardize it a bit better with other ports.
81552 Also rename the file to standardize it a bit better with other ports.
81715 binary that supports many targets.
81830 binary that supports many targets.
82049 in a single binary.
82214 x86: rename CheckRegSize to CheckOperandSize
83298 Tested on x86_64-linux, with gcc 4.8.5, 7.5.0 and clang 13.0.1.
83359 not just rename decref_target to target_ops::decref?
83949 function, so first rename the static one in extension.c.
84648 libsframe: rename API sframe_fde_func_info to sframe_fde_create_func_info
85081 Only rename debug sections when decompressing for linker.
85323 * elf.c (_bfd_elf_make_section_from_shdr): Only rename zdebug
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
89055 clang, and should work on most, if not all, architectures.
89114 gdb/testsuite: rename source file gdb.debuginfod/main.c
89160 gdb/testsuite: fix gdb.compile/compile-ops.exp with clang
89176 # however, this isn't portable, because other compilers, such as clang,
90707 user application thus generating the DW_OP_entry_value in the binary. The
90708 DW_OP_entry_value entries in the binary file allows GDB to resolve the
90999 * testsuite/binutils-all/rename-section-01.d: xfail xcoff.
91014 * testsuite/binutils-all/rename-section-01.d: New test.
91278 so I removed the C++ compilation option. Alternatively we could rename
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 -…
91555 sim: v850: rename v850.dc to align with other ports
91570 sim: ppc: rename ppc-instructions to powerpc.igen
91571 To make it clear this is an input to the igen tool, rename it with an
92853 We still have to maintain custom install rules due to how we rename
93000 for each binary value in the file gdb.arch/powerpc-power10.c is updated
93313 running gdb.base/macro-source-path when using clang.
93950 gdb running on the binary for gdb.base/watchpoint.c.
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:
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
96757 FAIL: gdb.server/file-transfer.exp: compare intermediate binary file
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:
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 \
98278 gdb: rename target_read_auxv(target_ops *) to target_read_auxv_raw
99006 be dumped back out using 'dump binary memory'.
99090 Regression tested on x86_64, using both gcc and clang.
99867 but that warning is only checked for clang, resulting in:
99944 inheritance is linked to the typedef, such as how clang does it,
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:
101263 gdb: make target_auxv_parse static and rename
101670 gentestdlls might not be available, this binary being created by make
102335 Mechanically rename all_comp_units to all_units:
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
102768 gdbsupport: move fileio_errno_to_host to fileio.{h,cc} and rename
102823 When a GDB built with -D_GLIBCXX_DEBUG=1 reads a binary with a single
103171 Stop strip from complaining about empty note sections when stripping a binary for a second time.
103232 I see this error when building with clang,
103242 Tested on x86_64-linux with gcc 12 and clang 14.
103356 Tested on x86_64-linux, with gcc 7.5.0 and clang 13.0.
103592 Binutils: Readelf testcase failing with clang
103740 make clang tests fail like so:
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.
104789 binary, that is, the standalone simulator, and is not included in the
104798 Currently, the 'run' binary links fine, though I suspect this might be
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
105519 Now, let's rename the C++ file and compile it as C:
105522 >> clang -O0 -g ./c.c
105580 internally rename members of such libraries. At that point, the
105645 clang in -std=c++17 mode (I did not test fully with clang in -std=c++11
106390 position-independent. Fix this by regenerating the same binary on the
106392 for the amd64 binary, although this one was already position-independent
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
107233 then the main binary is reloaded in GDB (using the file command).
107235 During the load of the new binary, GDB tries to recreate the varobj to
107236 track the global in the new binary (varobj_invalidate_iter). At this
107245 read_value_memory can access the (old binary’s) value.
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.
108815 First of all rename the meanwhile misleading Opcode_SIMD_FloatD, as it
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
109397 When starting to investigate this (taking the gcc-compiled binary as an
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
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 \
110482 gdb: rename gdbarch_tdep struct to fix g++ 4.8 build
110499 'struct gdbarch_tdep' to 'struct gdbarch_tdep_base'. This rename
110793 for mingw+clang. While adding that, I wrote some unit tests to make
110829 Attribute gcc_struct is not implemented in "clang -target
111156 gdb/testsuite: rename get_maint_bp_addr and move it to gdb-utils.exp
111213 binaries, meaning the second run overwrites the binary of the first run.
111375 then (accidentally) passed GDB a RISC-V binary, and asked GDB to "run"
111376 the binary on the native target. I got this error:
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.
113751 member functions, and rename it to m_length.
113943 gas: rename md_end to md_finish
113946 and rename target implementation. The renaming of target functions
114248 In other words, this lto binary reading speed optimization only works in the
115158 functions, and rename it to m_dwarf_version.
115667 This patch ensures that the gcc binary called by windres is quoted if
116271 For clang compiled objects with dwarf-5, location list offset address dump
117240 displaying binary values in groups of every four bits.
117267 The new feature displays binary values by group, with four bits per
117269 binary values.
117278 new form of the binary values.
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
120699 failures in the test when running the test with CC_FOR_TARGET='clang'
120700 CXX_FOR_TARGET='clang' F90_FOR_TARGET='flang'"
120726 For the compiled binary the Intel/LLVM compilers both decide to move the
121091 gdb/testsuite: rename intel next gen c/cpp compilers
121119 clang/flang ..). This commit enables GDB to detect C and Fortran
122057 Note that not having the debug info on the main binary is not strictly
122059 If the main binary has debug information, GDB shows some source form the
122060 main binary, unrelated to where we stopped.
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
123359 in particular (the content_shell binary), this entails going through
123368 There is a modest RAM increase of 180 MB in this binary (the existing
123532 Otherwise the string table may grow and hence e.g. change a final binary
123582 anymore, and hence a binary could change in that 2nd step for no actual
123583 reason. (Similarly stripping a binary linked with a linker pre-dating
123584 that commit would change the binary again when stripping it a 2nd time.)
124212 core binary, you'll notice something odd -- the write seems to
124344 - clang 8.0.1, 12.0.1
125915 using `ld -r -b binary` or `objcopy`, with no elf header flags set. But
126336 Dwarf: rename yet another instance of "index"
126678 execute the binary (the test binary is set non-executable), and so we
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'
126845 (the "binary" BFD, for example). Fix that.
127911 This fixes build breakage using clang with libc++ on FreeBSD where
128600 up in the binary for the correct or incorrect library on Intel or PowerPC.
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…
129641 /* Determine whether the remote target supports binary downloading.
129881 Building with clang++-14, I see:
129936 rename the typedef to task_t to fix them.
130008 Fix this error when building with clang++-14:
130019 gdb: fix clang build failure in msymbol_is_mips
130020 Building with clang++-14, I see:
130841 gdb/fortran: rename f77_keywords to f_keywords
130889 compiler flags used at compile time of a debugged binary, this might be
130901 directly tell me what is going on. Note, that when debugging a binary
131340 Debug info for function in Windows PE binary on wrong instruction
131418 The test loads the binary in GDB, grabs the address of a symbol, strips
131419 the binary, reloads it in GDB, runs the program, and then tries to place
131420 a breakpoint at that address. The problem is that the binary is built
131424 Fix this by linking the binary as non-position-independent. The
131428 I was confused for a while, I was trying to load the binary in GDB
131431 is that GDB strips the binary in-place, so we don't have access to the
131432 intermediary binary with symbols. Change the test to output the
131433 stripped binary to a separate file instead.
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
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
133400 gdb: rename start_symtab/end_symtab to start_compunit_symtab/end_compunit_symtab
134458 gdb/tui: rename tui_layout_split:set_weights_from_heights
134479 gdb/tui: rename tui_layout_base::adjust_size to ::set_height
134572 gdb: rename floatformats_ia64_quad to floatformats_ieee_quad
134573 It is better to rename floatformats_ia64_quad to floatformats_ieee_quad
135436 happens is now up to the stream. So, rename it. (This function is
135443 happens is up to the stream. So, rename it.
137301 some other GDB binary by using:
138578 For a binary with the HSA OS ABI, the change looks like:
138866 gdb/testsuite: rename a proc and fix a typo
140053 but they are a bit more cumbersome to use (simplest is binary but
141892 weird stabs data for testing. The original binary from the bug report
141976 failure with clang that Simon pointed out.
142562 * microblaze-opc.h: Follow 'fsqrt' rename.
142698 * elf/loongarch.h: Replace binary literals with hex.
142932 would just behave as "next". This was noticeable in clang-compiled
142934 to this problem, as running gdb.base/watchpoint.exp with clang
143968 gdb: rename compunit_primary_filetab to compunit_symtab::primary_filetab
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
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.
145388 binary, and symbols on these expressions cannot be overridden. Make
145722 gdb, btrace: rename record_btrace_enable_warn()
146496 bfd: rename core.texi to corefile.texi
146922 this target, there is no binary file dfp-test, and also there is no
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:
147077 gdb/infrun: rename variable and move to more specific scope
147078 Move the "started" variable to the scope it's needed, and rename it to
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.
147983 --pack-dyn-relocs=relr, to implement a glibc binary lockout mechanism
148137 gdb: rename lin-lwp to linux-nat in set/show debug
148190 * testsuite/ld-elfvsb: rename as ld-vsb.
148191 * testsuite/ld-elfvsb/hidden0.d: move to ld-vsb and rename with
152445 bfd: fix -Wunused errors with clang 13+
152455 gcc won't warn, but clang will.
152473 gdb/mi: rename build_table to add_builtin_mi_commands
152479 gdb/mi: rename mi_cmd to mi_command
152529 gdb/mi: rename mi_lookup to mi_cmd_lookup
153085 Fix this, seen when building with clang 14:
153097 Fix these, seen when building with clang 14:
153293 Update the gdb.threads/pending-fork-event.exp test (and rename it to
153802 gdb: rename "maint agent" functions
153804 maintenance commands, rename them accordingly (with the maint_ prefix),
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.
154550 target_waitstatus by value. Do that, and rename to
154625 included a large amount of binary data in the command sent to GDB. As
154626 this test didn't have a real test name the binary data was included in
154627 the gdb.sum file. The contents of the binary data could change
155303 both gcc and clang.
155994 that contain binary data. Before this commit, the code that printed
156000 data from a remote target, the auxv data is binary, so, before this
156019 The binary contents of the reply are now printed as escaped hex.
156266 "/usr/src/debug/llvm13-13.0.0-1.2.x86_64/tools/clang/lib/AST/Decl.cpp"
156636 sim: testsuite: rename global_sim_options to SIMFLAGS_FOR_TARGET
156638 the dejagnu settings of XXX_FOR_TARGET, rename global_sim_options to
156973 gdb: rename source_styling_changed observer
156981 seems unnecessary right now, so, in this commit, I plan to rename
157466 gdb: rename target_waitstatus_to_string to target_waitstatus::to_string
157780 uninitialized variable early as the same binary would sometimes work and
158321 gdb: rename rs6000-nat.c to rs6000-aix-nat.c
159631 To allow it, rename all gdbarch_tdep types to <arch>_gdbarch_tdep, and
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.
160239 Objcopy was used to create a binary file of just the executable code
160714 This little tweak terminates fuzzed binary readelf output a little
161030 gdb: remove bpstat typedef, rename bpstats to bpstat
161037 So, remove the bpstat typedef and rename struct bpstats to bpstat (since
161721 Currently for a binary compiled normally (without -fsanitize=address) but with
161977 binary. The main changes are:
162871 [gdb/testsuite] Fix assembly comments in gdb.dwarf2/clang-debug-names.exp.tcl
162874 clang-debug-names-debug.S:72: \
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
165994 Following 2 test points are failing with clang compiler
166006 Tested on x86_64-linux with gcc and clang.
168153 gdb.base/foll-fork.exp: rename variables
168819 PR28346, segfault attempting to disassemble raw binary
168854 the field private (rename to m_name) and add some accessors.
169872 binary format. Before the patch, the disassembler output is invalid
170309 gas/config/tc-riscv.c to here, and rename it to riscv_supported_std_ext.
170416 but with clang, I run into:
170460 Tested on x86_64-linux with gcc and clang-7 and clang-12.
171148 etc: rename configure.in to configure.ac
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.
171754 Fix an illegal memory access triggered by an atempt to disassemble a corrupt xtensa binary.
171772 Fix illegal memory access triggered by an attempt to disassemble a corrupt RISC-V binary.
171847 gdb: rename gdb/testsuite/gdb.arch/riscv64-unwind-prologue-with-ld-lw.c
172143 Compiler support for gcc and clang is in progress, see e.g.:
172718 also reported by John Baldwin, using a clang that uses libc++.
173531 Move this function to solib.c and rename it to gdb_bfd_scan_elf_dyntag.
173600 sim: rename ChangeLog files to ChangeLog-2021
174449 gdb: rename async_init_signals to gdb_init_signals
176442 gdb/testsuite: fix gdb.base/info-macros.exp with clang
176449 The current state is problematic when testing with CC_FOR_TARGET=clang,
176451 meaning we get a binary without any debug info, and the test fails.
176454 compiler is clang.
176478 The binary contains DWARF 4 debug info and includes a pre-standard
176499 complaint by inverting the condition and using a clang-compiled binary,
176693 PR28156, rename.c doesn't compile with MinGW
176697 * rename.c (get_stat_atime, get_stat_mtime): Don't compile
176850 [gdb/testsuite] templates.exp to accept clang++ output
176874 from the Clang++ compiled binary also.
178530 gdb: rename cfunc to simple_func
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.
181011 Tested on x86_64-linux, with both gcc 7.5.0 and clang 12.0.1.
181360 According to bug 28056, running an s390x binary gives:
182251 clang" I see: