Lines Matching +refs:texi +refs:docstring +refs:magic +refs:texi +refs:for

7 	Updated French translations for GOLD and LD
25 …mmits 969f5c0e1 (LoongArch: gas: Add support for s9 register) and a0aa6f4ab (LoongArch: ld: Add su…
37 	Restructure the architecture extensions table, add a new table for architecture
56 	Use default s_align_ptwo for .align.
68 	   "--hash-style=both" for these tests to cancel the effect of
80 	LoongArch: Do not emit R_LARCH_RELAX for two register macros
127 	directories for SP_COLLECTOR_LIBRARY_PATH ($SP_COLLECTOR_LIBRARY_PATH is used
142 	Updated Serbian translations for th bfd, gold and opcodes directories
159 	Append "#pass" to APX tests for targets which pad text sections with NOPs.
197 	In LoongArch psABI v2.30, an offset (-8 for LO20 and -12 for HI12)
198 	should be applied on PC for these reloc types to avoid wrong relocation
201 	The lld linker has already adapted the change.  Make it for the bfd
210 	Updated translations for various sub-directories
229 	Pass --hash-style=both to ld for -z mark-plt tests to support linker
242 …Import gcc commit 65388b28656d65595bdaf191df85af81c35ca63 which adds support for explicit object m…
246 	x86-64: Skip SCFI tests for x32 targets
249 	Fatal error: SCFI is not supported for this ABI
251 	skip SCFI tests for x32 targets.
254 		* testsuite/gas/scfi/x86_64/scfi-x86-64.exp: Skip for x32
265 	Add markers for 2.42 branch
302 	regression tests, this adds support for the following novel rcpc3
324 	This patch adds the necessary macro for encoding FEAT_RCPC3-dependent
328 	Given the introduction of the new address operand types for rcpc3
336 	for RCPC3 instructions lead to the requirement of a new set of operand
339 	That is, for the integer load/stores, there is only a single valid
342 	operation and the offset is post-indexed for Load-Acquire RCpc, and
343 	pre-indexed with writeback for Store-Release insns.
355 	created the need for an operand type similar to
366 	the address base register for load/stores, it is necessary to specify
372 	value requires a novel function be written to accommodate this for
373 	address operand insertion in assembly and another for extraction in
374 	disassembly, along with the definition of two insn fields for use with
410 	support for the Release Consistency Model, the `+rcpc3' architectural
412 	Binutils, together with the necessary macro for encoding rcpc3
431 	but we were incorrectly using the same list for both.  Add the missing tlbi
437 	Additionally, fix two missing checks for AARCH64_OPND_SYSREG_TLBIP that were
443 	Add an aarch64_feature_set field to aarch64_sys_ins_reg, and use this for
455 	OK for master?
466 	This patch add support for SVE2.1 instructions ld1q,
469 	Regression testing for aarch64-none-elf target and found no regressions.
471 	Ok for binutils-master?
481 	This patch add support for SVE2.1 instruction faddqv,
484 	Regression testing for aarch64-none-elf target and found no regressions.
486 	Ok for binutils-master?
496 	This patch add support for SVE2.1 instruction dupq, eorqv and extq.
498 	Regression testing for aarch64-none-elf target and found no regressions.
500 	Ok for binutils-master?
507 	aarch64: Add support for FEAT_SVE2p1.
510 	This patch add support for FEAT_SVE2p1 (SVE2.1 Extension) feature
513 	Also support for following SVE2p1 instructions is added
516 	Regression testing for aarch64-none-elf target and found no regressions.
518 	Ok for binutils-master?
525 	aarch64: Add support for FEAT_SME2p1 instructions.
528 	This patch add support for FEAT_SME2p1 and "movaz" instructions
535 	Regression testing for aarch64-none-elf target and found no regressions.
537 	Ok for binutils-master?
544 	aarch64: Add support for FEAT_B16B16 instructions.
547 	This patch add support for SVE2.1 and SME2.1 non-widening BFloat16
556 	Regression testing for aarch64-none-elf target and found no regressions.
558 	Ok for binutils-master?
569 	gas: testsuite: add an x86 testsuite for SCFI
570 	The testsuite for SCFI contains target-specific tests.
574 	GAS for processing.  The CFI directives in the input assembly files are,
581 	  - Only System V AMD64 ABI is supported for now. Using either --32 or
601 	In case of (#2) and (#3), SCFI generation is skipped for the respective
748 	gas: doc: update documentation for the new listing option
757 		* as.texi: Add documentation for the new listing option, -i.
761 	gas: x86: synthesize CFI for hand-written asm
763 	(a.k.a., the ginsn) for the x86 backend (AMD64 ABI only at this time).
764 	Using this ginsn infrastructure, GAS can then synthesize CFI for
765 	hand-written asm for x86_64.
770 	This patch also adds skeleton support for printing ginsn in the listing
771 	output for debugging purposes.
774 	needs to generate ginsns necessary for the following machine
781 	   be used as the base register for CFA tracking.  For SCFI, the base
782 	   register for CFA tracking is limited to REG_SP and REG_FP only for
794 	  addtion to the list.  This can be used as a proxy for the static
811 	GAS, apart from the current use-case of synthesizing CFI for
814 	Support is added only for System V AMD64 ABI for ELF at this time.  If
817 	  "Fatal error: SCFI is not supported for this ABI"
820 	to adhere to some pre-requisites for their asm:
828 	   - The base register for CFA tracking may be either REG_SP or REG_FP.
829 	   - If the base register for CFA tracking is REG_SP, the precise amount of
842 	employed for all architectures/ABIs using SCFI in the future.
847 		* as.c (defined): Handle documentation and listing option for
867 		(i386_target_format): Add hard error for usage of SCFI with non AMD64 ABIs.
876 		* gas/listing.h (LISTING_GINSN_SCFI): New define for ginsn and
883 		(struct frchain): New member for ginsn data.
894 	opcodes: x86: new marker for insns that implicitly update stack pointer
896 	operand constraint to reflect this.  This will be useful for SCFI
912 	update the stack pointer.  An operand constraint enumerator for implicit
918 	may be added for IMPLICIT_STACK_OP.
922 		* opcodes/i386-gen.c: Add a new BITFIELD for Rex2.
929 	gas: scfidw2gen: new functionality to prepare for SCFI
930 	Define a new set of handlers for CFI directives for the purpose of SCFI.
951 	assembler, it will synthesize DWARF call frame information (CFI) for the
967 	The upcoming support for SCFI is inteded to be experimental, hence the
970 	mature and robust.  The offering may also see for example, an
971 	--scfi=inline option for dealing with inline asm may be added in the
973 	ignore) the compiler generated CFI for the code surrounding the inline
979 	        * as.c (show_usage): Add support for --scfi=experimental.
982 	        * doc/as.texi: Document the new option.
992 	gas: dw2gencfi: expose dot_cfi_sections for scfidw2gen
993 	scfidw2gen will use this for processing the .cfi_sections directive.
1041 	gas: dw2gencfi: minor rejig for cfi_sections_set and all_cfi_sections
1172 	noticeable impact on the performance for large applications.
1191 …binutils/sim/testsuite/common/bits-gen.c:26:1: error: no previous prototype for ‘gen_struct’ [-Wer…
1196 	there is no need for a prototype.
1232 	failures were reported for gdb.python/py-inferior.exp.
1252 	On my machine the ordering was as I expected, so the test passed for
1254 	that we ended up recording the gdb.InferiorThread for the main thread.
1267 	The test still passes for me, and I believe this should fix the issue
1268 	for everyone else too.
1304 	aarch64: Add +xs flag for existing instructions
1309 	aarch64: Add +wfxt flag for existing instructions
1311 	aarch64: Add +rcpc2 flag for existing instructions
1313 	aarch64: Add +flagm2 flag for existing instructions
1315 	aarch64: Add +frintts flag for existing instructions
1317 	aarch64: Add +jscvt flag for existing fjcvtzs instruction
1320 	Add "+rdm" as an explicit alias for "+rdma", to maintain existing compatibility
1323 	aarch64: Add +fcma alias for +compnum
1333 	  1. Use @value{GDBP} for the GDB prompt rather than
1350 	and gdb.InferiorThread, this is similar to the existing support for
1354 	on selecting good names for their custom attributes so they
1369 	I'm doing this as a separate commit as I've updated the docs for the
1388 	attribute, which is a dictionary.  A user can, for example, do this:
1413 	which is a dictionary.  A user can, for example, do this:
1430 	I noticed that it is possible for the user to create a new
1446 	sense to consume an invalid gdb.Progspace created in this way, for
1554 	But has been modified by me.  Credit for the original idea and
1588 	This patch pulls out just the fix for the trailing "/" problem, and
1604 	When writing the test for this patch I ran into two problems.
1607 	on the command being completed for the test name.  This is fine for
1616 	for my new tests.
1638 	possible match, including the last one, which accounts for the
1642 	within make_tab_completion_list_re, for the function completion
1643 	example I gave above the expected pattern is now 'f1 +f2 +', which for
1663 	Having access to this string from Python is useful for allowing
1809 	- during checkpoint creation, lseek is called in the inferior (process A) for
1810 	  all file descriptors, and it returns != -1 for at least one file descriptor.
1822 	correct for process B.
1825 	stop_pc, so fix this by adding similar fixups for the executing and resumed
1868 	The m32r trap code was written for a 32-bit Linux host (and really, one
1876 	is a bit ugly, but lets us enable warnings for the whole file.
1891 	if Linux/glibc & m32r had defined behavior, those aren't the host for
1895 	already has detection support for it, and it's been around since at
1907 	still keep it on the prototype for cases where it's used as a
1932 	Only check these decls once in case other m4 macros also look for them.
1941 	common sharing space for these projects.
1952 	This directory contains example programs for the user to experiment with.
1968 	Our HWC tables are absent for new machines.
1969 	I have added HWC tables for the following events: PERF_TYPE_HARDWARE,
2010 	    which doesn't work for me -- I have to use guile3.0.
2022 	    for targets. Disable target libgrust if we're not building target
2043 	    Config,Darwin: Allow for configuring Darwin to use embedded runpath.
2068 	    This facility is not available for Darwin 8 or earlier, however the
2071 	    We default this on for systems where the external DYLD_LIBRARY_PATH
2072 	    does not work and off for Darwin 8 or earlier.  For systems that can
2080 	    Makefile.tpl: disable -Werror for feedback stage [PR111663]
2082 	    Without the change profiled bootstrap fails for various warnings on
2102 	    ..., where we need to use it (separate commits) for build-tree testing, similar
2116 	gas: aarch64: Add system registers for Debug and PMU extensions
2117 …This patch adds support for the new AArch64 system registers that are part of the following extens…
2126 	[gdb] Fix assertion failure for checkpoint delete 0
2165 	But the pc address (as well as the file name and line number) is missing for
2168 	Fix this by sampling the pc value for the current process in
2188 	  for (const fork_info &fi : fork_list)
2275 	which doesn't work for me -- I have to use guile3.0.
2300 		(LDEMUL_BEFORE_PARSE): New.  Set to elf_x86_64_before_parse for
2315 	    x86-64: Ignore r_addend for R_X86_64_GLOB_DAT/R_X86_64_JUMP_SLOT
2317 	    According to x86-64 psABI, r_addend should be ignored for R_X86_64_GLOB_DAT
2325 	branches, it is safer to require glibc 2.36 for such binaries.
2327 	Extend the glibc version dependency of GLIBC_ABI_DT_RELR for DT_RELR to
2328 	also add GLIBC_2.36 version dependency for -z mark-plt on the shared C
2354 		* testsuite/ld-x86-64/x86-64.exp: Run -z mark-plt test for
2476 …/vol/gcc/src/hg/master/local/libiberty/pex-unix.c:326:3: note: (near initialization for 'funcs.wai…
2479 	    currently returns int.  However, on Solaris pid_t is long for 32-bit,
2480 	    but int for 64-bit.
2500 	    use the template parameter mangling previously specified for lambdas to also
2502 	    "natural" fit for it, such as when the parameter is constrained or deduced.
2504 	    I'm concerned about how the latter link changes the mangling for some C++98
2541 	    libiberty: Disable hwcaps for sha1.o
2558 	    disables hwcaps support for libiberty.
2571 	    Nick has approved this patch (+ small ld change to use it for --build-id=),
2581 	    would then have #elif defined (HAVE_WHATEVERELSE_SHA1_HW_SUPPORT) for
2582 	    the other arch support, similarly for any target attributes on
2619 	    v3: Match file style for error-handling blocks, don't close
2620 	    in/out/errdes on error, and check close() for errors.
2644 	    And we avoid mangling collisions by following the proposed mangling for
2655 	This patch adds support for FEAT_THE doubleword and quadword instructions.
2659 	Support for following sets of instructions is added in this patch.
2701 	optional register operands for the `tlbip' and `sysp' instructions,
2709 	  * The first operand for both insns should be either xzr or an
2716 	aarch64: Add support for 128-bit system register mrrs and msrr insns
2718 	starting with Armv9.4-a, a mechanism for manipulating their contents
2722 	contiguous general-purpose registers and vice-versa, as for example:
2727 	This patch adds the necessary support for these instructions, adding
2728 	checks for system-register width by defining a new operand type in the
2730 	predicate, responsible for checking whether the requested system
2750 	extension.  These are added to aarch64_sys_regs_tlbi[] for use
2759 	addition of 128-bit system registers for these means that special
2769 	name, tlbip operation).  This creates the need for adequate qualifiers
2778 	aarch64: Apply narrowing of allowed immediate values for SYSP
2781 	specifications for the SYSP instructions limit their ranges to 8-9 for
2787 	range of operand values for fields in the instruction tagged with the
2796 	aarch64: Add support for the SYSP 128-bit system instruction
2810 	aarch64: Add support for optional operand pairs
2817 	for any optional operands, while others allow for both to be optional.
2834 	it is impossible to mark both operands 1 and 2 as optional for an
2836 	optional.  This is not overly-problematic given that, for optional
2838 	the first.  Thus, it suffices for us to flag that there is a second
2858 	aarch64: Add support for xzr register in register pair operands
2859 	Analysis of the allowed operand values for `sysp' and `tlbip' reveals
2860 	a significant departure from the allowed behavior for operand register
2861 	pairs (hitherto labeled AARCH64_OPND_PAIRREG) observed for other
2881 	To allow for this departure from hitherto standard behavior, we
2908 	for encoding d128 instructions.
2913 	Add support for compiling build tools with various -Werror settings.
2918 	flags against the build compiler.  This should be good enough for our
2951 	remove some of the features that were added just for it: return values
2978 	is really looking for a certain kind of symbol (text or data) using a
3009 	DWARF reading, this means that gdb has to wait for a significant
3028 	removed.  This allows for other functions to be removed as well.
3083 	Change how cooked index waits for threads
3084 	This changes the cooked index code to wait for threads in its
3087 	it easier to wait for other events here as well.
3094 	setting for this purpose.
3124 	results of the computation.  This change is needed for a subsequent
3125 	patch, where installing a complaint interceptor around a parallel-for
3136 	for some DWARF scanning to be completed before returning.  The only
3141 	earlier, in the background.  This means there is the potential for the
3177 	This logic dates back to the original import, and seems to be for
3179 	None of that is relevant for us with current automake, so drop it.
3204 	are used to construct 64-bit values from 32-bit values (for the low
3230 	bpf: Added linker support for R_BPF_64_NODYLD32.
3249 	These failures don't happen for mipsisa32rN-mti-elf etc,
3257 	arm: Add support for Armv8.9-A and Armv9.4-A
3258 	This patch adds AArch32 support for -march=armv8.9-a and
3263 	The cpu_arch_ver entries for ARM_ARCH_V9_4A and ARM_ARCH_V8_9A
3264 	are technically redundant but it including them for macro code
3300 	Add support for the aarch64-gnu target (GNU/Hurd on AArch64)
3304 	The ld/emulparams/aarch64gnu.sh file is (for now) identical to aarch64fbsd.sh,
3381 	Since 0x66 is the opcode prefix for adcx, it is wrong to use the 'S'
3397 		* testsuite/gas/i386/suffix.s: Add tests for adcx and adox.
3410 	This brings us in sync with current set of gdb warnings (for C).
3441 	ld: Adjust x86 and x86-64 tests for -z mark-plt
3443 	non-zero r_addend for JUMP_SLOT relocation and pass -z nomark-plt to
3447 		r_addend for JUMP_SLOT relocation.
3487 	One item was too strict for PE/COFF, and there's really no need to check
3488 	for specific comment contents here.
3496 		* doc/c-i386.texi: Add znver5.
3513 	Arm/doc: separate @code from @item for older makeinfo
3525 	- cpu_flags_from_attr() wasn't ready for use on big-endian hosts,
3529 	Various targets have / had overrides for .text and/or .data. Make sure
3534 	Various targets have / had overrides for .bss. Make sure that in such
3541 	gas: correct .bss documentation for non-ELF
3558 	The override for .skip is simply pointless, for read.c having exactly
3579 	While there also fold the identical handlers for .text (there likely is
3580 	more room for such folding).
3599 	Just like obj_elf_section() is called for .section, obj_elf_{text,data}()
3600 	need calling for .text/.data.
3604 	for the non-ELF case as well. Don't override .bss for ELF - that's
3606 	specifier from being usable. Don't override .text and .data at all - for
3607 	.data and ELF for the same reason, while for .text and ELF obj-elf.c's is
3608 	all we need, and for (hypothetical) non-ELF read.c's identical handling
3627 	Just like obj_elf_section() is called for .section, obj_elf_{text,data}()
3628 	need calling for .text/.data.
3644 	for other section switching, so its original purpose was at best
3657 	Enforce C++11 as a minimum for building gold [PR30867]
3658 	The attempt in 5e9091dab885 to correct gold for modern LLVM has broken
3659 	gold for older compilers.  This commit introduced C++11 types without
3684 	In commit 83c79df86bf4 I removed configure tests for strtoull among
3688 		* bfd.c (bfd_scan_vma): Delete fall-back for strtoull.
3698 		* ldlex.l: Don't use bfd_scan_vma for integer conversion, use
3703 	RISC-V: T-HEAD: Fix wrong instruction encoding for th.vsetvli
3705 	initial support patches for XTheadVector, the program operation failed
3723 		* config/tc-riscv.c (validate_riscv_insn): Add handling for
3779 	a more readable form.  Likewise for the corresponding pat_end.
3809 …commit e4786449e1c26716e3f9ea182caf472e4dbc96e0    config.guess: invoke "uname -p" from PATH for n…
3812 	commit 2a7c4b64d4aec5c3a8a975625f0f8c369d365667    testsuite: add coverage for vendor-clobbering
3822 	LoongArch: Fix linker generate PLT entry for data symbol
3831 	The linker generates a "PLT entry" for data without any diagnostic.
3838 	For R_LARCH_PCALA_HI20 relocation, linker only generate PLT entry for STT_FUNC
3927 	target is skipped for some tests that require these options.
3938 	Due to the fact that the conditions for generating 32 abs
3942 	By modifying the conditions for macro expansion and adjusting
3991 	This is a bit redundant for most ports as they go through sim-basics.h
3999 	it's for declaring integer constants as 64-bit, not for casting them.
4012 	sim: drop support for recursive makes entirely
4019 	sim: drop support for automatic subdir recursion
4105 	 Dump of assembler code for function main:
4133 	 Dump of assembler code for function main:
4162 	 Dump of assembler code for function main:
4233 	The above issues were fixed by introducing a new function that looks for
4234 	adjacent PC ranges for the same line, until we notice a line change. Then
4235 	we take that as the start PC of the range.  The new start PC for the range
4236 	is used for the control.step_range_start when setting up a step range.
4239 	for the above reverse step issues.
4254 	gdb/dwarf2: Add support for DW_LNS_set_epilogue_begin in line-table
4255 	This commit adds a mechanism for GDB to detect the linetable opcode
4259 	While the standard allows for multiple points marked with epilogue_begin
4260 	in the same function, for performance reasons, the function that
4261 	searches for the epilogue address will only find the last address that
4262 	sets this flag for a given block.
4280 	Invoke ppc's igen from the top-level like we do for all other ports.
4288 	To prepare for moving these into the top-level configure, namespace
4296 	sim: ppc: switch to AS_HELP_STRING for automatic formatting
4336 	(like libiberty) seem to, so check for it in the top-level for all
4383 	AC_MSG_RESULT as the AC_CACHE_CHECK takes care of it for us.
4399 	common code switched to lf_printf for the same functionality, but
4401 	cleanup for now so we can merge the rest.
4405 	common igen version in preparation for merging the two implementations.
4413 	get migrated over to the common parsing logic, but for now, switch
4430 	This simplifies the build a bit (especially for deps in port subdirs),
4437 	to prepare for moving it to the local.mk code.
4497 	In the test-case, this pattern handles either the syscall name or number for
4502 	but the pattern for the pipe2 syscall mistakenly uses SYS_pipe instead of
4526 	[gdb/testsuite] Fix gdb.base/gdb-index-err.exp for root user
4543 	Fix this by making the test unsupported for the root user.
4578 	Append "#pass" to APX tests for targets which pad text sections with NOPs.
4590 	'/' starts a comment for some targets.  Use .byte instead of .insn with
4614 	dwarf, fortran: add support for DW_TAG_entry_point
4615 	Fortran provides additional entry points for subroutines and functions.
4620 	This commit adds support for parsing the DW_TAG_entry_point DWARF tag.
4624 	support.  Even so, some of the attached tests still fail for ifort, due
4625 	to some wrong line info generated for the entry points in ifort.
4636 	For gfortran there actually exists a bug on bugzilla, asking for the use
4662 	a second variation to retrieve the pc bounds for DIEs tagged with
4664 	we will call a separate method for entry points.  As the validity checks
4665 	at the endo f dwarf2_get_pc_bounds are the same for both variants,
4675 	LoongArch: ld: Add support for tls le relax.
4695 	LoongArch: gas: Add support for tls le relax.
4706 		(loongarch_args_parser_can_match_arg_helper): Add support for relax.
4714 	LoongArch: opcodes: Add support for tls le relax.
4715 	Add new opcode for tls le relax.
4723 	LoongArch: include: Add support for tls le relax.
4724 	Add new relocs number for tls le relax.
4735 	LoongArch: bfd: Add support for tls le relax.
4743 	1. Implement support for three new relocation items in bfd.
4777 	RISC-V: THEAD: Add 5 assembly pseudoinstructions for XTheadVector extension
4778 	In order to make it easier to complete the compiler's support for
4798 		* testsuite/gas/riscv/x-thead-vector.d: Add tests for new
4812 	ld: Mention support for Intel APX relocations in NEWS
4878 	and for
4975 		* testsuite/x86_64_mov_to_lea1.s: Add a test for
5028 		(output_disp): Set fixP->fx_tcbit3 for REX2 prefix.
5034 		* testsuite/gas/i386/x86-64-gotpcrel.s: Add tests for
5058 	gas: Mention initial support for Intel APX in NEWS
5063 	Define NT_X86_SHSTK which is the note for x86 Shadow Stack (SHSTK) to
5072 	Support APX JMPABS for disassembler
5085 		(print_insn): Add #UD exception for jmpabs.
5086 		(dis386): Modify a1 unit for support jmpabs.
5115 		* testsuite/gas/i386/x86-64.exp: Add new test for PUSHP/POPP.
5133 	PPX functionality for PUSH/POP is not implemented in this patch
5144 		(md_assemble): Add handler for unsupported_rsp_register and
5146 		(check_APX_operands): Add invalid check for push2/pop2.
5158 		testcases for POP2.
5166 		* i386-dis.c (PUSH2_POP2_Fixup): Add special handling for PUSH2/POP2.
5167 		(get_valid_dis386): Add handler for vector length and address_mode for
5169 		(nd): define nd as b for EVEX-promoted instrutions.
5170 		(OP_VEX): Add handler of 64-bit vvvv register for APX-Push2/Pop2 insn.
5180 		* opcodes/i386-dis-evex-reg.h: Handle for REG_EVEX_MAP4_80,
5187 		(get_valid_dis386): Change for NDD decode.
5201 		(build_apx_evex_prefix): Change for ndd encode.
5204 		(match_template): Support swap the first two operands for
5216 	Add tests for APX GPR32 with extend evex prefix
5264 		(need_evex_encoding): Adjusted for apx.
5271 		(check_register): Assign i.vec_encoding for APX evex instructions.
5286 		* i386-dis-evex.h: Add EVEX_MAP4_ for legacy insn
5315 	Created an empty EVEX_MAP4_ sub-table for EVEX instructions.
5318 		* i386-dis-evex.hi: Added an empty EVEX_MAP4_ sub-table for
5325 	APX uses the REX2 prefix to support EGPR for map0 and map1 of legacy
5326 	instructions. We added the NoEgpr flag in i386-gen.c for instructions
5339 		(struct _i386_insn): Add rex2 and rex2_encoding for
5343 		(register_number): Handle RegRex2 for gpr32.
5348 		(optimize_encoding): Handel add r16-r31 for registers.
5352 		are valid for the instruction
5359 		* doc/c-i386.texi: Document .apx.
5384 		* i386-dis.c (struct instr_info): Add erex for gpr32.
5385 		Add last_erex_prefix for rex2 prefix.
5386 		(REX2_M): Extend for gpr32.
5397 		(process_i386_opcode_modifier): Set NoEgpr for VEX and some special instructions.
5413 	The PRU architecture documentation [1] was used for the initial GNU
5422 	has not released official updates for the PRU documents.  And I wanted
5449 	Since the failed .reloc cases for ADD/SET/SUB/ULEB128 are rarely to use,
5481 	elfxx-loongarch.c:1844:32: runtime error: index 125 out of bounds for
5486 	be testing for r_type < ARRAY_SIZE (loongarch_howto_table).  I figure
5490 		LOONGARCH_EMPTY_HOWTO entries for 121..123.
5509 	sim: common: pull in newlib extensions for Linux compatibility
5528 	LoongArch: Add testsuit for DESC and tls transition and tls relaxation.
5532 	LoongArch: Add support for TLS LD/GD/DESC relaxation
5559 	LoongArch: Add support for TLSDESC in ld.
5560 	1.The linker for each DESC generates a R_LARCH_TLS_DESC64 dynamic
5570 	LoongArch: Add new relocs and macro for TLSDESC.
5584 	Re: LoongArch: Add support for <b ".L1"> and <beq, $t0, $t1, ".L1">
5617 	loops for the callers that did it.
5627 	function for struct value.
5637 	function for struct value.
5685 	the caller specify the type to use for the value.  The parameters
5696 	for it to be called during unwind, when "this frame"'s id is not yet
5698 	created without a valid next frame id.  I would much prefer for things
5707 	However, it's possible for the "this frame"'s next frame to be an
5710 	frame (which is actually the frame where registers for "this frame" are
5712 	value_of_register_lazy, for the same reason.  A later patch will factor
5778 	The -Wshadow=local is too new for some compilers, so move it to a var
5785 	Fixed by declaring these types for linux-musl.
5791 		* common/gp-defs.h: Define ino64_t, off64_t, fpos64_t for linux-musl.
5792 		* libcollector/unwind.c: Define __u64 for linux-musl.
5816 	type available for use.
5820 	type available for use.
5823 	These decoders declare a lot of common variables for use by substeps,
5833 	name & type for this exact use.
5871 	real bug is low, so leave it be.  The warning is suppressed for more code
5872 	that is hand written (e.g. the mloop logic), but disabling for the entire
5904 	Check for rogue DAP exceptions in test suite
5905 	This changes the test suite to look for rogue DAP exceptions in the
5933 	for a DAPException.
5971 	Step (b) was omitted for rs6000-tdep.c; this manifests as a regression on
5972 	PPC platforms for e.g. O2_float_param: instead of seeing…
5976 	… we get "optimized_out" for val.  Passing next_frame to
5984 	In many cases, it's not possible for gdb to discover the executable
6003 	Approved-By (ab) for some time, but there has been no information to be
6021 	Finally, for completeness sake, the trailers Co-Authored-By and Bug
6022 	were added, even though they have been in use for a long time already
6031 	Just like obj_elf_section() is called for .section, obj_elf_{text,data}()
6032 	need calling for .text/.data.
6039 	function for the remaining ELF targets.
6065 	the diagnostic to trigger when there was no other need for a REX prefix;
6070 	The latter requires splitting out code from md_assemble(), for it to
6072 	code then also needs generalizing to account for immediate operands, as
6083 	LoongArch: Add support for the third expression of .align for R_LARCH_ALIGN
6090 	The addend of R_LARCH_ALIGN for ".align 5, ,4" is 0x405.
6091 	The addend of R_LARCH_ALIGN for ".balign 32, ,4" is 0x405.
6105 	This emits #line 2 for the first line in the output when it should be 1.
6120 	support for line number tracking.  The $LINENO variable, even when
6153 	ld: Add lib32 directories for 32-bit emulation on FreeBSD/amd64
6182 	This is is not really a problem for our code, which allocates the
6190 	    for (int i = 0; i < cached_frame->reg_count; i++)
6270 	sim: add ATTRIBUTE_FALLTHROUGH for local code
6290 	sim: iq2000: add fallback for exit syscall
6294 	Doesn't seem to make sense for this to fall through
6347 	gprofng incorrectly reads the form of the DW_FORM_ref_addr attribute for DWARF
6358 		* src/DwarfLib.cc: Fix the reader for DW_FORM_ref_addr.
6378 	 *repeat for other waves*
6385 	thread to the GDB thread list, because it got an event for a thread
6391 	That shouldn't ever happen for the amd-dbgapi target, threads should
6394 	Note "New AMDGPU Wave ?:?:?:1" is for wave 1.  What happened was that
6400 	queues a WAVE_COMMAND_TERMINATED event for the exit.
6418 	sees that TARGET_WAITKIND_THREAD_EXITED event for a thread it doesn't
6434 	   * A command for a wave was not able to complete because the wave has
6451 	with one entry for each wave, that seems like the place to store that
6514 	prints the "exited" notification, we can't ask dbgapi for any info
6518 	sees the wave for the first time, and making
6539 	And for that, we need a new thread_deleted observable.
6618 	that happens to select the exiting thread for an unrelated reason.
6620 	This commit add the explict switch, fixing the latent problem for
6622 	testcase for this, but it can't be upstreamed yet, until more pieces
6659 	  event for the thread we care about, which would result in the
6750 		* testsuite/gas/s390/zarch-insndesc.s: Add test cases for
6766 	Since comments are not column aligned the output can enhanced for
6800 		* testsuite/gas/s390/zarch-insndesc.s: New test case for s390-
6810 	and use macros for string lengths, such as mnemonic, instruction
6838 	an error was detected for. Also continue processing for cases where
6850 	Provide descriptions for instructions introduced with commit ba2b480f103
6852 	69341966def ("IBM zSystems: Add support for z16 as CPU name."). Use
6860 		* s390-opc.txt: Add descriptions for IBM z16 (arch14)
6881 	EXEEXT_FOR_BUILD. Use pattern used for other architecture build
6897 	for this file.  Reading the data as signed and then returning it
6936 	This patch add support for FEAT_ITE "Instrumentation Extension" adding
6944 	This patch add support for FEAT_ECBHB "Exploitative control using
6953 	This patch add supports for FEAT_SPECRES2 "Enhanced speculation
6961 	gdb: register frame_destroyed function for amd64 gdbarch
6965 	anymore because GCC started using CFA for variable locations instead.
7035 	x86: Remove the restriction for size of the mask register in AVX10
7037 	remove the restriction for size of the mask register in AVX10.
7042 		(VEX_check_encoding): Remove opcode_modifier check for vsz.
7043 		* testsuite/gas/i386/avx10-vsz.l: Remove testcases for mask
7056 	LoongArch: Allow la.got -> la.pcrel relaxation for shared object
7058 	performed for symbols with hidden visibility. For example, if a.c is:
7082 	check is enough not to wrongly relax preemptable symbols (for e.g.
7099 	Yet another fix for mcore-sim (rotli)
7110 	The fix is the same.  Rather than using a "long", use a uint32_t for the
7168 	But I recently saw a test failure for that test, which looked like
7183 	This only crops up (for me) when running on a loaded machine, and
7185 	loop for 10+ minutes sometimes in order to see the failure.
7194 	any order, and we have a flag for each pattern.  Once both patterns
7214 	two parts, but in the alternative orders, thus, for a particular
7222 	LoongArch: Add call36 and tail36 pseudo instructions for medium code model
7237 	R_LARCH_CALL36 is used for medium code model function call pcaddu18i+jirl, and
7258 	AVR: Use __TEXT_REGION_ORIGIN__ as start for MEMORY region text.
7263 		(MEMORY): Use as start address for the text region.
7280 	Use function entry point record only for entry values
7284 	stored in the debug info for this location.
7291 	   for (; i < 8; i++)
7319 	This logic was introduced for showing the entry-values of
7320 	function arguments if they are available, but for some
7321 	reason this was added for non-entry-values as well.
7324 	problem for function arguments, if you "break stacktest"
7347 	explicitely looking for entry values.
7368 	Commit deb1ba4e38b ("[gdb/tui] Fix TUI resizing for TERM=ansi") introduced a
7371 	There is precedent for this, but it's something we want to get rid of
7472 	to the "=" function for packed boolean arrays.
7506 	   +crc: Enables CRC32 Extension. +simd: Enables VFP and NEON for Armv8-A. +crypto: Enables
7507 	   Cryptography Extensions for Armv8-A, implies +simd. +sb: Enables Speculation Barrier
7508 	   Instruction for Armv8-A. +predres: Enables Execution and Data Prediction Restriction
7509 	   Instruction for Armv8-A. +nofp: Disables all FPU, NEON and Cryptography Extensions.
7515 	    +simd: Enables VFP and NEON for Armv8-A.
7516 	    +crypto: Enables Cryptography Extensions for Armv8-A, implies +simd.
7517 	    +sb: Enables Speculation Barrier Instruction for Armv8-A.
7518 	    +predres: Enables Execution and Data Prediction Restriction Instruction for Armv8-A.
7522 	Ok for binutils-master? I don't have commit access so I need someone to commit on my behalf.
7532 	This patch adds support for the Cortex-X3 CPU to binutils.
7534 	Gas regression testing for aarch64-none-linux-gnu target and found no regressions.
7536 	Ok for binutils-master? I don't have commit access so I need someone to commit on my behalf.
7558 	only look at now_seg, for a few others it looks as if failing to do so
7563 	This primarily means for obj_elf_section() to pass the new subsection
7564 	into change_section(), for it to be set right away (ahead of invoking
7570 	are added. Presumably there is a reason for this difference in
7585 	ELF, COFF, and Mach-O all have custom handlers for .bss. Don't override
7586 	those; install a handler only for a.out.
7597 	not for long, seeing in-flight additions for APX).
7613 	Arm64: fix build for certain gcc versions
7620 	This is a small addendum to PR31124 "rodata in flash for
7646 	accidentally listed the deps for all mloop steps as mloop.in instead of the
7709 	with fuzzed objects.  Restore those checks.  Also, for dwo look at
7715 	This commit adds support for ratified extensions:
7744 	the code for string handling writes the address fetching callback
7758 	gdb/testsuite: add tests for unwinding of pseudo registers
7770 	the unwind information contains an entry for a register considered a
7783 	pseudo registers to non-current frames for that architecture.
7816 	target, for the portion of the raw register where we don't write the
7840 	fixes writing to pseudo registers in non-current frames for those
7861 	frame" for a more detailed explanation.
7870 	that takes a frame instead of a regcache for implementations to write
7890 	using the regcache is that it always provides raw register values for
7931 	 - In frame_unwind_register_value, when prev_register (for instance
7952 	   current frame will give the same behavior as before: for frame 0, raw
7963 	   unwind pseudo register values.  It's apparently possible for the
8027 	"this frame", for which we want to read or write the register values,
8030 	values for a frame that does not exist yet (usually when trying to
8037 	series).  You need to get the previous frame only for those functions to
8087 	for that ({get,put}_frame_register_bytes_consecutive or something like
8161 	3. In the gdb_asserts, it is unnecessary to check for:
8165 	   given that right after we check for:
8188 	Right now, gdbsupport/common-regcache.h contains two abstractons for a
8192 	These abstractions allow code to be written for both gdb and gdbserver,
8193 	for instance in the gdb/arch sub-directory.
8263 	used only for additional arguments of variadic functions, allowing
8352 	[gdb/tui] add SingleKey bindings for reverse execution commands
8353 	The bindings for the reverse execution commands are the same letters
8371 	user (GDB) supplied readline callback function, which for us is
8395 	gdb: improve error reporting for 'save gdb-index'
8406 	  Error while writing index for `/tmp/hello': mkstemp: No such file or directory.
8412 	Also, I find the 'mkstemp' in the error message confusing for a user
8419 	Similarly, for a directory that does exist, but can't be written to:
8422 	  Error while writing index for `/tmp/hello': mkstemp: Permission denied.
8430 	  Error while writing index for `/tmp/hello': `/non_existing_dir': No such file or directory.
8435 	  Error while writing index for `/tmp/hello': `/no_access_dir': Permission denied.
8440 	  Error while writing index for `/tmp/hello': `/tmp/not_a_directory': Is not a directory.
8495 	Clean base_reg and assign correct values to regs for input_output_operand (%dx).
8502 		clean i.base_reg for input output operand (%dx).
8522 	Please contact the application's support team for more information.
8583 	Support rodata in flash for more AVR devices
8592 	  * scripttempl/avr.sc: Add support for HAVE_FLMAP.
8600 	RISC-V: Emit R_RISCV_RELAX for the la/lga pseudo instruction
8605 	for RISC-V.
8619 	for la).
8622 	when the relocation is emitted for the la pseudo instruction.  The
8639 		Defined to record source_macro into fixups for riscv target.
8653 	just like what we did for the architecture parser.
8720 	This patch adds a new gdb.interrupt() function for this purpose.  It
8763 	constructed using more or less the same procedure as is done for MI.
8807 	in NEWS.  This patch adds a note for a fix that's already gone in.  I
8827 	$4 = (VirtualLeftRight *) 0x13fab89b0 <vtable for VirtualLeftRight+16>
8829 	$5 = (VirtualLeftRight *) 0x13fab89b0 <vtable for VirtualLeftRight+16>
8831 	$6 = (VirtualLeftRight *) 0x13fab89b0 <vtable for VirtualLeftRight+16>
8835 	$8 = (VirtualLeft *) 0x13fab89b0 <vtable for VirtualLeftRight+16>
8843 	$12 = (VirtualRight *) 0x13fab89b0 <vtable for VirtualLeftRight+16>
8847 	original type, it used the ARG value for the result, which in
8886 	LoongArch: Add support for <b ".L1"> and <beq, $t0, $t1, ".L1">
8903 	relaxations for some specific areas, so the value of `riscv_opts.relax'
8905 	of `riscv_opts.relax' for every relocation.  Therefore, set `relaxable' to
8906 	`riscv_opts.relax' will cause unexpected behavior for the following case,
8925 	This reloc is meant for the 16-bit LWGP instruction, 0x6400/0xfc00
8941 		* elfxx-mips.c (micromips_reloc_shuffle_p): Return false for
8944 		overflow calculation for R_MICROMIPS_GPREL7_S2.
8949 		Return false for R_MICROMIPS_GPREL7_S2.
8993 	disabled for various reasons.
8995 	To put that 1.5hr/multilib in perspective, that's roughly 3X the time for other
9010 	Another thought was to build a mapping to the right entry for all the
9012 	instruction data and a mapping for those which can be disambiguated based on
9024 	then find the index of the first instruction for each nibble. Decoding uses
9043 	In tui_layout_split::apply I noticed that for variable-size layouts we take
9050 	but not for fixed-size layouts:
9056 	Fix this by increasing available_size for fixed-size layouts with shared box.
9114 	Following on from the previous commit, I searched the testsuite for
9130 	All the tests are still passing for me after these changes.
9146 	single gdb_test_multiple pattern, for a completion command that
9151 	always found that option backward -- it checks for the \r\n at the
9169 	gdbserver: allow for general 'monitor set debug COMPONENT VALUE' use
9172 	command to allow for general:
9244 	to get debug for all components except the event-loop component.
9289 	Use pretty printers for struct member stubs
9290 	PR29079 shows that pretty printers can be used for an incomplete
9300 	The reason is simply that in common_val_print the check for stubs
9317 	- the source for the current frame,
9318 	- the source for main, or
9328 	Fix this by moving the responsibility for showing main from tui_enable to
9352 	Fix dynamic type resolution for LOC_CONST and LOC_CONST_BYTES symbols
9361 	Thanks to tpzker@thepuzzlemaker.info for a first version of this
9374 	always be right before statement in the line table. This is true for GCC
9376 	not true for clang compiled binaries.
9382 	behavior for the 'until' command. In this patch I propose a more general
9383 	solution, making it so every time we generate the SAL for a given pc, we
9446 	sim: m32r: include more glibc headers for the funcs we use [PR sim/29752]
9454 	sim: m32r: add more cgen prototypes for traps
9456 	and we can't safely include the relevant cpu*.h files for them.
9483 	gdb/record: Support for rdtscp in i386_process_record.
9484 	This patch adds support for process recording of the instruction rdtscp in
9626 	Specifically, calls like the one to look for a parallel "__XVZ"
9664 	And the test for hw watchpoints in gdb.reverse/watch-reverse.exp actually
9668 	The same is not done for gdb.reverse/watch-precsave.exp, since it's not
9720 	to a regression reported in PR29572, and implements a different fix for PR29453.
9740 	long when printing "negative" symbol values for 32-bit targets.
9751 		print_width is 32, set up print_format_string for an int32_t
9785 	symbols for __cxa_throw, in each module where a throw is done, but
9809 	The fix is to simply ignore other trampoline symbols when looking for
9856 …lute symbol into a relocation without a symbol if the symbol is being used for a complex relocatio…
9895 	Maybe we should delete this logic entirely, but for now,
9900 	Add basic support for RISC-V 64-bit EFI objects
9970 		contents for ALPHA_R_GPDISP, and simplify handling.  Rewrite
9996 	This adds the efi target name handling for riscv64 to objcopy.
10012 	sim: warnings: enable only for development builds
10015 	git) or a release build, and disable the warnings for releases.
10055 	emitted in a different order due to stub names for local symbols
10063 	the start of a group of stubs to not care about the symbol, for all
10100 	by replacing them with '@@'. This was already done for the
10118 	I think it is clearer for binutils to follow this, particularly
10152 	s390: Support for jump visualization in disassembly
10153 	Add support for jump visualization for the s390 architecture in
10159 	information required for jump visualization:
10172 	Provide instruction information required for jump visualization during
10176 	dis_nonbranch. No annotation is done for data reference instructions
10189 		  class information for jump visualization:
10193 		  Define opcode flags mask S390_INSTR_FLAG_CLASS_MASK for above
10195 		  Define helpers for common instruction class flag combinations:
10201 		  for jump visualization: jump, condjump, and jumpsr.
10203 		  instructions with information for jump visualization.
10205 		  Provide instruction information for jump visualization.
10254 	multithreading, but this does not allow for an already deployed gdb to
10290 	acceptable commands for use within an early initialisation file.
10300 	initialisation, and this would work fine except for the new DAP
10316 	I propose that we don't update the documentation for early
10426 	case which reliably reproduces the problem and tests for a few other
10450 	linux_fork_detach() won't be called for the wrong inferior when there
10466 	when a checkpoint (created via GDB's "checkpoint" command) exists for
10501 	files which should be avoided with -r option for linker tests.
10503 	Fix them by passing -m elf_x86_64 to linker and removing -nostdlib for
10508 		for tests with --64.  Remove -nostdlib for tests with -r.
10538 	re-computes it for a warning.  It is better to reuse the
10547 	arrays without a null terminator.  The null terminators are needed for
10600 	there is not enough buffer left for the current register,
10650 	regressions when testing using the READ1 mechanism. The reason for that
10652 	looks for GDB suggesting more than what the test inputted, but not the
10725 	gas: no md_cons_align() for .nop{,s}
10792 	RISC-V: Update gas/NEWS for RISC-V vendor extension news.
10801 	SiFive has define as set of flexible instruction for extending vector
10840 	RISC-V: Zv*: Add support for Zvkb ISA extension
10841 	Back then when the support for the RISC-V vector crypto extensions
10877 	configure:22024: checking compiler flags for python code
10899 	was done for gdbserver/configure.ac in commit db6878ac553.
10902 	fixing, and I'm not sure how to check for this.  Shellcheck doesn't detect
10912 	configure:25214: checking compiler flags for python code
10926 	This patch can fix these failures for r6 default triples:
10936 	and we believe that the multilib should be used for this case.
10963 	libiberty: Disable hwcaps for sha1.o
10979 	disables hwcaps support for libiberty.
11114 	Several bugs have been fixed, for example in the handling of directory names.
11125 	addressed.  In addition to fixes for typos, the texts have been expanded
11135 		* doc/gp-archive.texi: Expand the description of the options.
11136 		* doc/gp-collect-app.texi: Fix various typos and textual improvements.
11137 		* doc/gp-display-html.texi: Cover the new GNU long option syntax.
11138 		* doc/gp-display-src.texi: Fix various typos and textual improvements.
11139 		* doc/gp-display-text.texi: Fix typos fixed and textual improvements.
11140 		* doc/gp-macros.texi: Fix a bug in the vspace macro and add new macro.
11141 		* doc/gprofng.texi: Cover the GPROFNG_SYSCONFDIR environment variable.
11142 		* doc/gprofng_ug.texi: Fix various typos and textual improvements.
11143 		* doc/version.texi: Adapt the date and version number.
11201 	potential for breaking existing scripts, but also, is, I think, the
11204 	feedback about this breakage.  Now GDB will print the exception for
11265 …/Users/smarchi/src/binutils-gdb/gdb/darwin-nat.c:1169:7: error: no matching function for call to '…
11273 	gas: add NEWS entry for change of comment syntax in BPF assembler
11290 	[gdb/tui] Use const std::string for string literals in tui-stack.c
11344 		* doc/c-bpf.texi (BPF Special Characters): Update.
11352 	I believe AArch64 has similar HW acceleration for SHA1, perhaps it
11390 	for (and requires) a number of environment variables, so the target
11431 	and the test will be re-run for me.
11451 	The buckets within bucket_hash will always have the same ordering (for
11472 	index for GDB itself, like:
11478 	And then setting different values for NUM will change the generated
11485 	ideally like to have reproducible builds: for the same source,
11487 	binary.  And we do .... except for the index.
11505 	a smaller binary, which is quicker to load, and for which we could
11518 	seems like a good home for it.
11527 	I've also taken this opportunity to split out the logic for whether
11538 	I noticed in passing that out algorithm for generating the gdb-index
11547 	With an unmodified GDB, generating a gdb-index for GDB, I see a file
11551 	With a patched GDB, generating a gdb-index for the _same_ GDB binary,
11572 	check for the 1024 minimum size).
11579 	Split out the code that makes a copy of the GDB executable ready for
11581 	load the GDB executable into GDB (for creating an on-disk debug
11590 	gdb: option completion for 'save gdb-index' command
11591 	Add proper support for option completion to the 'save gdb-index'
11593 	new option_def data structures for parsing the '-dwarf-5' option.
11611 	New Romanian translation for ld
11619 	The root cause for the segmentation fault is that linux_is_uclinux gives an
11644 	  /* Check for 64-bit inferior process.	 This is the case when the host is
11721 	The root cause for the segmentation fault is that linux_is_uclinux gives an
11739 	We leave addressing the root cause for the following commit in this series.
12001 	testsuite: Clean up #as in dump file for i386 tests
12273 	i386: Use a fallback XSAVE layout for remote targets
12280 	This fallback layout is currently only used for remote targets since
12298 	This is not superfluous for two reasons:
12305 	  is for instance relevant because the index-cache is written by a worker
12306 	  thread in the background, so we can check more thoroughly for data races
12400 	I then tried writing a more obvious test case for this, involving an
12401 	inferior call -- and discovered that gdb.events.cont does not fire for
12404 	This patch installs a new event listener for gdb.events.inferior_call
12405 	and arranges for this to emit continue and stop events when
12419 	GDB's Python API documentation for gdb.Command.complete() says:
12504 	[gdb/testsuite] Use more %progbits for arm
12513 	Fix this by using %progbits instead of @progbits for arm.
12558 	for cmdline to contain \0s, so switch to target_fileio_read_alloc().
12572 	current_templates, in return for adding a level of indirection when
12573 	looking up mnemonics (commonly happening just once per insn). Plus for
12578 	x86: also prefer VEX encoding over EVEX one for VCVTNEPS2BF16 when possible
12580 	when possible") left out, for being slightly less straightforward.
12594 	While for some of the macro insns using x0 is kind of okay, as they
12600 	for macro insns: NULL is now allowed, indicating a match (which imo is
12602 	other matching functions now (also) used for macro insns need to avoid
12605 	Note that for LA the restriction is slightly too strict: In non-PIC mode
12607 	libopcodes doesn't know what mode gas is presently assembling for, so we
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.
12699 		* testsuite/gas/s390/esa-g5.s: Add test for extended mnemonic
12702 		* testsuite/gas/s390/zarch-z900.s: Add test for extended
12705 		* testsuite/gas/s390/zarch-z9-109.s: Add tests for extended
12708 		* testsuite/gas/s390/zarch-z10.s: Add tests for extended
12711 		* testsuite/gas/s390/zarch-z196.s: Add tests for extended
12714 		* testsuite/gas/s390/zarch-arch13.s: Add tests for extended
12745 		* zarch-z10.s: Add test cases for risbg, risbgz, rnsbg, rosbg,
12748 		* zarch-z196.s: Add test cases for risbhg and risblg.
12750 		* zarch-zEC12.s: Add test cases for risbgn and risbgnz.
12777 	The ESA opcode test cases for IBM z900 contain a few edge cases. They
12799 	Opcode test cases for z/Architecture instructions that use relative
12851 	for packing reasons in ancient times, but with m_accessibility not
12857 	need for this.
12864 	RISC-V: Add vector permutation instructions for T-Head VECTOR vendor extension
12869 	This patch adds permutation instructions for the "XTheadVector"
12871 	are documented in a PR for the RISC-V toolchain conventions ([1]).
12880 		* testsuite/gas/riscv/x-thead-vector.d: Add tests for
12894 	RISC-V: Add vector mask instructions for T-Head VECTOR vendor extension
12899 	This patch adds mask instructions for the "XTheadVector"
12901 	are documented in a PR for the RISC-V toolchain conventions ([1]).
12910 		* testsuite/gas/riscv/x-thead-vector.d: Add tests for
12924 	RISC-V: Add reductions instructions for T-Head VECTOR vendor extension
12929 	This patch adds reductions instructions for the "XTheadVector"
12931 	are documented in a PR for the RISC-V toolchain conventions ([1]).
12940 		* testsuite/gas/riscv/x-thead-vector.d: Add tests for
12950 	RISC-V: Add floating-point arithmetic instructions for T-Head VECTOR vendor extension
12955 	This patch adds floating-point arithmetic instructions for the
12957 	"XTheadVector" extension are documented in a PR for the
12967 		* testsuite/gas/riscv/x-thead-vector.d: Add tests for
12981 	RISC-V: Add fixed-point arithmetic instructions for T-Head VECTOR vendor extension
12986 	This patch adds fixed-point arithmetic instructions for the
12988 	"XTheadVector" extension are documented in a PR for the
12998 		* testsuite/gas/riscv/x-thead-vector.d: Add tests for
13012 	RISC-V: Add integer arithmetic instructions for T-Head VECTOR vendor extension
13017 	This patch adds integer arithmetic instructions for the
13019 	"XTheadVector" extension are documented in a PR for the
13029 		* testsuite/gas/riscv/x-thead-vector.d: Add tests for
13043 	RISC-V: Add sub-extension XTheadZvamo for T-Head VECTOR vendor extension
13048 	This patch adds the sub-extension "XTheadZvamo" for the
13050 	for T-Head VECTOR vendor extension. The 'th' prefix and the
13051 	"XTheadVector" extension are documented in a PR for the
13062 		for "XTheadZvamo" extension.
13067 		* doc/c-riscv.texi:
13082 	RISC-V: Add load/store segment instructions for T-Head VECTOR vendor extension
13087 	This patch adds provides load/store segment instructions for T-Head VECTOR
13090 	and the "XTheadVector" extension are documented in a PR for the
13113 	RISC-V: Add load/store instructions for T-Head VECTOR vendor extension
13118 	This patch adds load/store instructions for the "XTheadVector"
13120 	documented in a PR for the RISC-V toolchain conventions ([1]).
13129 		* testsuite/gas/riscv/x-thead-vector.d: Add tests for
13143 	RISC-V: Add configuration-setting instructions for T-Head VECTOR vendor extension
13148 	This patch adds configuration-setting instructions for the "XTheadVector"
13150 	in a PR for the RISC-V toolchain conventions ([1]).
13168 	RISC-V: Add CSRs for T-Head VECTOR vendor extension
13173 	This patch adds the CSRs for XTheadVector. Because of the
13176 	documented in a PR for the RISC-V toolchain conventions ([1]).
13185 		* config/tc-riscv.c (enum riscv_csr_class): Add the class for
13210 	"XTheadVector" extension are documented in a PR for the RISC-V
13237 		* doc/c-riscv.texi:
13255 …The reason for the same was GDB core trying to switch to a child thread with tid not set that does…
13262 …This patch is a fix for the same where pd_update () is called in the wait () or in update_thread_l…
13275 	The problem is that for the source window:
13304 	  there's no room for them.
13328 	The problem is that for the command window:
13347 	window to 1.  However, that would also change behaviour for the case that the
13389 	Apparently I have the curses module installed for 3.6, but not 3.11.
13394 	Fix this by only using the curses module when necessary, for python <= 3.7.
13441 	This is done for consistency, but it also lets us simplify some other
13532 	Also changed the regs-for-symbols-pseudo.s, adding some entries that
13571 	A couple of spots in the DAP code use the same workaround for the
13588 	similar to how that was fixed for arm in commit eb42bb14895 ("[gdb/tdep] Fix
13589 	catching syscall execve exit for arm").
13615 	Before recent commit 169fe7ab54b ("Change gdb.base/examine-backwards.exp for
13640 	and do likewise for TestStringsH and TestStringsW.
13662 	Given that C++17 is now a requirement for GDB, update gdb/disasm.h to
13724 	Two places are manually adjusted to account for this difference:
13783 	Fix: symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM
13789 	[gdb/tdep] Fix catching syscall execve exit for arm
13815 	The reason for the error is that we're stopped at the syscall exit of syscall
13837 	Fix: symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM
13840 …* ld.texi (Special Sections): New entry in the linker manual. Describes how the .gnu.warning and .…
13849 	handle it for us.
13867 	Stack allocation is a bad idea for something of variable size that GDB has
13885 	bogus base addresses") inadvertently removed support for displaying
13903 	function.  The test must be compiled with -fvar-tracking for the
13909 	The patch fixes the one regression error for the test on PowerPC.
13947 	(I plan to add support for CU-mapped links to GNU ld, mainly so that we can
13958 	gdb: fix reopen_exec_file for files with target: prefix
13968 	system 'stat' call, which obviously isn't going to work for files with
13989 	doesn't appear to trigger for our current test suite.
14004 	The problem is that the bfd library caches open FILE* handles for bfd
14005 	objects that it has accessed, which is great for short-lived, non
14007 	for GDB this caching causes us a problem.
14017 	If the on-disk file has changed then system stat will give results for
14019 	the file descriptor for the original on-disk file (from before the
14031 	would for sure solve the problem, but feels a little crude.
14072 	  waiting for further input from the user (or in async mode, for an
14084 	It turns out that there are existing observers for both of these
14101 	similar enter/exit object for Guile, though right now Guile doesn't
14106 	for the bfd_cache_close_all() calls.  Instead, I'll call
14143 	isn't a problem, the test was changed to allow for the new output.
14165 		* testsuite/gas/bpf/regs-for-symbols-pseudoc.d: New file.
14166 		* testsuite/gas/bpf/regs-for-symbols-pseudoc.s: Likewise.
14167 		* testsuite/gas/bpf/regs-for-symbols-pseudoc.l: Likewise.
14168 		* doc/c-bpf.texi (BPF Registers): Document that it is not possible
14179 	attempt multiple different templates for a single instruction. In some
14189 	This is a problem for BPF: generally the assembled object will be loaded
14200 	This approach is modeled directly after Jan Beulich's patch for RISC-V:
14205 	Many thanks to Jan for recognizing the problem as similar, and pointing
14253 	regcache::aspace) wasn't relevant for the regcache itself.  Callers of
14255 	way of getting the address space for a thread, if you already have the
14264 	The current get_thread_arch_regcache function gets an address_space for
14306 	Fix read_ranges for 32-bit long
14309 	(observed as "nm -l" being very slow for mingw64 host; probably causes
14327 	This patch implements this for gdb.  Most requests are assumed to
14332 	inherent -- unless the client waits for a stop event before sending a
14362 	The main motivation for this patch is that I thought it would be
14363 	helpful for cancellation.  I am still working on that, but meanwhile
14371 	Gold/MIPS: Add targ_extra_size=64 for mips32 triples
14418 	further requires that like for insns we fully check the CPU flags; till
14454 	suffix and having an operand which allows for Reg8 and Reg64, but
14488 	Remove uses of obstack in the code generating the libraries XML for
14502 	compile.exp generally does not work for me on Fedora 38.  However, I
14520 	      gdb: implement missing debug handler hook for Python
14527 	The same is true for str.isalnum(), which is replaced with
14534 	aarch64: Add support for VMSA feature enhancements.
14554 	This patch also adds support for:
14571 	This patch also adds support for two read only system registers
14582 	Also adds support for system register "pmsdsfr_el1".
14586 	aarch64: Add SLC target for PRFM instruction.
14587 	This patch adds support for FEAT_PRFMSLC feature which enables
14588 	SLC target for PRFM instructions.
14602 	Fix emit-relocs for aarch64 gold
14603 	Fix relocation offsets values for the relaxed input sections the same
14604 	way it was fixed for the sections in PR21430.
14679 	The testcase only has two threads, yet GDB presented the exec for
14687 	thread number, as the number is not important for what this test is
14732 	GAS/MIPS: add "--defsym r6=" for default when it's r6
14733 	  * testsuite/gas/mips/mips.exp (mips_arch_create): Add "--defsym r6=" to as_flags for r6 targets.
14749 …* testsuite/gas/elf/elf.exp (section2): Add -mpdr option to assembler command line for mips-irix t…
14755 	  * testsuite/gas/mips/call-nonpic-1.d: Adjust regexp to allow for mips-irix targets.
14757 	  * testsuite/gas/mips/mips.exp: Run new test for mips-irix targets.
14791 	seems important to generate correct XML for the <thread> response.
14794 	unplanned consequences.  This is needed, though, for nl_langinfo to
14811 	A co-worker requested that the DAP scope for a nested function's frame
14816 	I chose to do this only for DAP.  For CLI and MI, gdb currently does
14835 	This can be used to find the static link frame for a given frame.
14843 	for use elsewhere.  The API is changed slightly to make it more
14904 	limit the range of behaviours for subclasses.
14914 	to eliminate '.*' for better control on what is matched.  Also,
14915 	simplify the "E" match group, for which the optional SYMBOL becomes
14972 	The root cause for the difference is the presence of .debug_line info for
14988 	gdb: implement missing debug handler hook for Python
14990 	extension_language_ops::handle_missing_debuginfo function for Python.
15030 	By extending the __call__ method it is possible for the Python
15031 	extension to locate the debug information for objfile and return a
15040 	           for the objfile still couldn't be found.  GDB will not call
15042 		   information for objfile.
15046 		  should look again for the debug information.
15052 	When a handler returns True, GDB will look again for the debug
15054 	.gnu_debuglink based lookup strategies.  It is not possible for an
15060 	the handlers for the current program space first, and then all of the
15069 	gdb: add an extension language hook for missing debug info
15072 	information file for a particular objfile.
15074 	This commit doesn't actually implement the hook for any of GDB's
15076 	adds support for the hook to extension-priv.h and extension.[ch], and
15085 	Python implementation for this new hook, and gives a fuller
15088 	Currently, when looking for separate debug information GDB tries three
15093 	  2. Check for .gnu_debuglink section and use that to look up the
15104 	  debug information for this objfile.  This matches the current
15115 	  c. Return a filename for a file containing the required debug
15120 	for steps #1 and #2 to be repeated.
15143 	some separate helper functions.  My hope is that the steps for looking
15155 	this in place for now.
15164 	This commit merges the code that looks for and loads the separate
15173 	lookup for the missing debug information, assuming that GDB can find a
15179 	for GDB to ask a COFF file for a build-id.  If the COFF file doesn't
15184 	asking debuginfod for the debug file.  As build-ids should be unique,
15187 	not too worried about this for now.
15203 	the logic for when we try to load a separate debug file in elfread.c
15206 	itself a separate debug objfile for some other objfile.
15210 	I don't know if it's possible for the coffread code to get into the
15232 	  * doc/binutils.texi: Document the new feature.
15254 	the box_width is not used for that.
15319 	- use sminrow, smincol, smaxrow and smaxcol variables for the last
15352 	This patch fixes the single regression failure for the test on PowerPC.
15370 	Introduced two new help strings for --enable-error-execstack and
15379 	Add documentation for the MIPS assembler's -march=from-abi command line option
15383 	MIPS: Fix binutils-all tests for r6 triples
15392 	If your target has no support for TARGET_WAITKIND_NO_RESUMED events
15403 	it seems unnecessarily harsh.  If you started an execution command for
15440 	Testcases for stepping over thread exit syscall (PR gdb/27338)
15458 	for syscalls with up to 3 arguments, and, if the syscall doesn't
15462 	The following patch will want to use the macro to define a wrapper for
15470 	Report thread exit event for leader if reporting thread exit events
15473 	thread exit event for it.  See e.g., here, in
15492 …UNTESTFLAGS="--target_board=native-extended-gdbserver" TESTS="gdb.threads/no-unwaited-for-left.exp"
15494 	 Running src/gdb/testsuite/gdb.threads/no-unwaited-for-left.exp ...
15495 	 FAIL: gdb.threads/no-unwaited-for-left.exp: continue stops when the main thread exits (timeout)
15502 	 FAIL: gdb.threads/no-unwaited-for-left.exp: continue stops when the main thread exits (timeout)
15508 	 No unwaited-for children left.
15509 	 (gdb) PASS: gdb.threads/no-unwaited-for-left.exp: continue stops when the main thread exits
15518 …1163850 "no-unwaited-for" main () at /home/pedro/rocm/gdb/build/gdb/testsuite/../../../src/gdb/tes…
15519 	   3    Thread 1163850.1164130 "no-unwaited-for" [remote] Sending packet: $Hgp11c24a.11c362#39
15530 	     [infrun] target_set_thread_options: [options for Thread 1163850.1163850 are now 0x3]
15536 …  [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target extended-remote
15537 …  [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target extended-remote
15552 …ceived: l<threads>\n<thread id="p11c24a.11c362" core="0" name="no-unwaited-for" handle="0097d8f7ff…
15564 	exit event for the zombie leader too, i.e., making GDBserver respect
15607 	server sends a thread exit event for that thread instead.
15616 	sends a thread-exit event for the last resumed thread, the no-resumed
15626 	 - No unwaited-for children left.
15637 	stop_all_threads: (re-)enable async before waiting for stops
15657 	#2 - gdb picks one events, and it's for thread 1.  All other stops are
15659 	     stops all threads to start an inline step over for thread 1.
15666 	     gdbserver reports thread exit for thread 1
15677 	#5 - gdb processes the thread exit for thread 1, finishes the step
15692 	     Seeing this, wait_one disable target async, to stop listening for
15707 	that can async, before waiting for stops.
15763 	for its turn.
15784 	  No unwaited-for children left.
15801 	more resumed threads to be waited for, so returns
15805 	there's an in-line step in progress that we need to wait for to
15810 	target_set_thread_options mechanism which is optimal for only enabling
15812 	by using target_thread_events, which enables thread exit events for
15827 	is modified to account for the fact that it's possible that we
15855 	Implement GDB_THREAD_OPTION_EXIT support for native Linux
15856 	This implements support for the new GDB_THREAD_OPTION_EXIT thread
15857 	option for native Linux.
15865 	Implement GDB_THREAD_OPTION_EXIT support for Linux GDBserver
15866 	This implements support for the new GDB_THREAD_OPTION_EXIT thread
15867 	option for Linux GDBserver.
15879 	result in deadlock, with other threads waiting for their turn to
15886 	This commit makes it possible for GDB to ask the target to report
15887 	thread exit events for a given thread, using the new "thread options"
15957 	remote all-stop mode.  There's no good reason for this, it just
15960 	There is no need to add a qSupported feature for this, because the
15961 	server won't send a THREAD_EXITED event unless GDB explicitly asks for
15970 	Now that gdb/19675 is fixed for both native and gdbserver GNU/Linux,
16031 	disabled.  All we need to do is to report support for the option,
16047 	However, for remote debugging, it wouldn't be ideal for GDBserver to
16051 	events all the time for the same reason.  Instead we have the
16060 	more generic than just for clone events.  It lets you enable/disable a
16077 	and this clears options for all threads of process 1000, and then sets
16097 	Documentation for this new remote protocol feature is included in a
16132 	Documentation for this new remote protocol feature is included in a
16145 	Andrew's, adjusted for a different solution, and for covering
16237 	What is needed is for GDB to have more control over whether the new
16246 	When looking for solutions to this problem I considered how GDB
16253 	Note we have support for requesting thread creation events out of the
16255 	for the new/child thread.  That would be sufficient to address in-line
16256 	stepping (issue #1), but not for displaced-stepping (issue #3).  To
16261 	new child.  In fact, for some targets, like e.g., Windows, it would be
16274 	The infrun code that handles displaced stepping fixup for the child
16275 	after a fork/vfork event is thus reused for THREAD_CLONE, with some
16283 	target_follow_clone target method, which is responsible for making the
16376 	becoming the new leader.  There's no thread exit event for the execing
16396 	patch in question, that code will look for the corresponding
16397 	thread_info for each LWP.  For the pre-exec non-leader LWP still
16419 	load event for "libc.so.6", which leads to GDB trying to open
16420 	libthread_db for the post-exec inferior, and, on such systems that
16555 		* cpu-amdgcn.c (arch_info_struct): Add entries for
16580 	Gold/MIPS: Use EM_MIPS instead of EM_MIPS_RS3_LE for little endian
16582 	GAS/MIPS: Fix testcase module-defer-warn2 for r2+ triples
16610 	  * ld.texi: Document the new command line options.
16616 	  * testsuite/ld-elf/commonpage2.d: Disable errors for RWX segments and/or executable stacks.
16692 	Add support for ilp32 register alias.
16722 	boundary for that occurring somewhen into the future and
16750 	bfd: aarch64: Avoid BTI stub for a PLT that has BTI
16759 	already. An alternative is to never emit BTI stubs for PLTs, instead
16770 	for the stub.
16804 	useful but too much for this bug fix patch.)
16812 	implemented by this patch for the non-BTI case.
16838 	add a new test for the THE registers to pick up their illegal use,
16845 	codebase, a more natural place for these changes.
16857 		* testsuite/gas/aarch64/illegal-sysreg-8.l: Add tests for THE
16911 	only ISA extensions. Besides helping readability for several insn
16913 	added for APX (as all of the new templates would otherwise need to have
16932 	The test currently fails for IEEE 128-bit floating point types.  PowerPC
16943 	mapping for the vsrs from the fpr to the vsr registers so the value is
16948 	so it is only true for floating point values.
16960 	The primary issue this patch fixes is the DWARF register mapping for
16962 	issues.  The register mapping issue is responsible for two of the
16971 	  signal handler).  Many platforms use a trampoline for signal return, and
16973 	  uses a trampoline for signal handler calls is (recent kernels for)
16974 	  PowerPC.  I believe the rationale for using a trampoline here
16980 	  signal trampoline.  This is because the custom CFI for the
16993 	the common-code for platforms that use a trampoline to dispatch calls
16998 	The PowerPC DWARF register mapping is the same for the .eh_frame and
16999 	.debug_frame on Linux.  PowerPC uses different mapping for .eh_frame and
17000 	.debug_frame on other operating systems.  The current GDB support for
17002 	rs6000_adjust_frame_regnum file gdb/rs6000-tdep.c is not correct for Linux.
17003 	The files have some legacy mappings for spe_acc, spefscr, EV which was
17009 	rs6000_linux_dwarf2_reg_to_regnum is installed for both gdb_dwarf_to_regnum
17014 	rs6000_linux_dwarf2_reg_to_regnum for the architecture.  Similarly,
17020 	The specific sequence of events for handling a signal on most
17035 	the kernel.  This is the case for most platforms as the kernel puts a
17059 	then, if an inferior call caused a new thread to appear, or for an
17063 	The problem is that for these targets GDB relies on a call to
17076 	gdb: call update_thread_list for $_inferior_thread_count function
17094 	I ran into this issue when writing a test for the next commit which
17096 	inferior.  But for testing I've made use of non-stop mode and
17109 	gdb: add a custom command completer for disassemble command
17110 	Add a new command completer function for the disassemble command.
17129 	Which was my main motivation for working on this commit.
17138 	  So, for example, if you want to disassemble function 'bar' in file
17149 	  Dump of assembler code for function main:
17173 	expression_completer is out of scope for this commit.
17211 	compelling argument for why we should make the change beyond my
17225 	ld: print branch fixups into the map file for ppc elf targets
17235 		* ld.texi (--print-map): Add new item about fixups.
17246 	for BFD clients.
17263 		* doc/bfd.texi (BFD front end): Add Threading menu item.
17336 	aarch64: Add arch support for LSE128 extension
17363 	handling in the code to allow for the encoding of the LSE128 128-bit
17384 	In preparation for the implementation of 128-bit system register
17414 	Add Binutils support for system registers associated with the
17417 	In doing so, we also add core feature support for THE, enabling its
17426 		* doc/c-aarch64.texi (AArch64 Extensions): Update
17427 		documentation for `the' option.
17428 		* testsuite/gas/aarch64/sysreg-8.s: Add tests for `the'
17461 	a multiple of 2, so it's weird for this subtraction to result in 1.  In
17474 	to strip the thumb bit, like is done elsewhere (for instance for bpaddr
17478 	return an address that is suitable for arithmetic.  In any case, that
17479 	would be a change with a broad impact, so for now just fix the issue
17495 	Tests looking for certain .note-section recorded properties may not
17497 	compiler for linking): Such object files may themselves have similar
17513 	RISC-V: Add support for XCValu extension in CV32E40P
17536 	          operands for the extension.
17538 		* doc/c-riscv.texi: Noted XCValu as an additional ISA extension
17539 	          for CORE-V.
17578 	          for XCValu.
17580 	          for XCValu.
17585 	RISC-V: Add support for XCVmac extension in CV32E40P
17608 	          operands for the extension.
17610 		* doc/c-riscv.texi: Noted XCVmac as an additional ISA extension
17611 	          for CORE-V.
17631 	          for XCVmac.
17633 	          for uimm.
17653 	gdb: Update email address for Carl Love in gdb/MAINTAINERS
17697 	Change gdb.base/examine-backwards.exp for AIX.
17706 	ld: =fillexp different behaviors for hexidecimal literal
17708 	  * ld.texi: Update description of the FILL command.
17800 	I found a declaration in py-stopevent.h for which there is no
17860 	Finally respective tests were introduced for Sparc only.
17882 	When support for the Q extension was added, the libopcodes side of these
17954 	This patch adds support for 10 new AArch64 system registers
17960 	aarch64: Add support for GCSB DSYNC instruction.
17961 	This patch adds support for Guarded control stack data synchronization
17968 	aarch64: Add support for GCS extension.
17969 	This patch adds for Guarded Control Stack Extension (GCS) extension. GCS feature is
17973 	Also this patch adds support for GCS instructions gcspushx, gcspopcx, gcspopx,
17978 	aarch64: Add support for Check Feature Status Extension.
17979 	This patch adds support for Check Feature Status Extension (CHK) which
17985 	aarch64: Add support for Armv8.9-A and Armv9.4-A Architectures.
17986 	This patch adds AArch64 support for Armv8.9-A architecture (-march=armv8.9-a)
17992 	  * testsuite/ld-x86-64/property-3.r: Update regexp to allow for targets which support x86-64-v3.
18033 	  * ld.texi: Document the new feature.
18146 	support, this patch includes encoding and decoding support for MAP7 and
18157 		* doc/c-i386.texi: Document .user_msr.
18177 		and handle the map7_f8 for save space.
18200 		(mod_table): New entry for USER_MSR and
18232 	New Georgian translation for the ld sub-directory
18236 	gas: bpf: new test for MOV with C-like numbers ll suffix
18243 	to avoid ambiguity with the assembler's support for C-like numerical
18281 	Fix "finish" for vector types on ARM
18322 	and GCC, add instructions for keeping the file synchronized across the
18385 	    make it easy for users to easily build new GDB on currently
18387 	    sufficient for latest stable releases of distributions to include a
18388 	    compiler for the standard, and/or for new compilers to appear as
18448 	The GAS will generate a pair of ADD/SUB for this,
18471 	SET_ULEB128/SUB_ULEB128 relocations for it for now,
18529 	so that it can (for my use case) check the exact buffer length.
18531 	The restrictions for when the Value.bytes can or cannot be written too
18532 	are exactly the same as for Value.assign.
18551 	unexpected errors to be reported from GDB for both native and remote
18554 	This commit addresses this situation for native and remote targets.
18556 	to get this functionality working correct for native and remote
18563 	linux_nat_target::detach.  In here we call stop_wait_callback for each
18577 	the assert to allow for 0 or 1 lwps at this point.  As the 0 case can
18637 	best solution is for gdbserver just to report an error, which is what
18650 	detach and gets back an error, and if there's a pending exit event for
18654 	We could possibly check for a pending exit event before sending the
18656 	non-stop mode) for the stop notification to arrive after the detach is
18658 	case we would still need to check for pending stop events after seeing
18668 	opportunity for getting the exit to arrive is so small I've never
18677 	approach I've taken for testing this patch.
18684 	[gdb/testsuite] Add wait-for-index-cache in gdb.dwarf2/per-bfd-sharing.exp
18691 	       index_cache_debug ("writing index cache for objfile %s",
18705 	Fix this by using "maint wait-for-index-cache".
18724 	Clang doesn't use CFA information for variable locations. This makes it
18739 	add XFAILs for existing clang releases, if this gets solved in future
18802 	ready for posting yet.  I think what I have here would be fine if my
18864 		* elf.c (_bfd_elf_slurp_version_tables): See free_contents for
18920 	This value must be ignored if the value for the language of main is zero.
18965 	Like done earlier for files needing adjustment anyway, also do this for
18970 	this for us, to avoid wasting space and cache bandwidth/capacity.
18994 	cpu_arch[] had a wrong entry for i686.
19016 	Except for the shared 1- and 2-byte cases, the LEA uses corrupt %rsi
19034 	but the implementation is checking for ".". Having two numbers being
19041 		and <commit> for --heap and --stack.
19042 		* doc/binutils.texi: Add <commit> for --heap and --stack.
19059 	-done here - only used for relaxing  */
19062 	+     only used for relaxing.  */
19075 	usefully, they also add blank lines to libbfd.h separating relocs for
19117 	represent the possible owner kinds for a target_section.  Trying to pass
19147 	- making get_language_name return nullptr for language_c, and
19161 	index-write.c to make up for the absence.
19259 	There is currently a bug in the bit masking for the barrel shift
19286 	done for the ordinary (gdb) language.
19288 	I wonder if this code could be improved.  Requiring an atomic for the
19321 	ld: fix typo in ld.texi metdata->metadata
19327 	really make sense for the element type to be named "_list".  Rename to
19447 	Same rationale as the previous patch, but for solib-rocm.
19450 	   rocm_update_solib_list for that) and a unique_ptr to the
19478 	Change solib-svr4 to use its own data type for its internal lists.  The
19480 	irrelevant for this internal use.
19482 	 - Introduce svr4_so, which contains just an std::string for the name
19483 	   and a unique_ptr for the lm_info.
19485 	   seems like a good choice for this, we don't need to insert/remove
19515 	target_so_ops::free_so is responsible for freeing the specific lm_info
19558 	It seems to me like the code should used the defined type aliases, for
19592 …/home/simark/src/binutils-gdb/gdb/interps.c:378:18: error: no matching function for call to ‘inter…
19634 	RISC-V: Don't do undefweak relaxations for the linker_def symbols.
19643 	Therefore, it seems like we shouldn't do the undefweak relaxations for these
19648 		relaxations for the linker_def symbols.
19653 	This is for consistency and to prevent possible unnecessary errors due
19685 	This commit also improves testutils.inc for riscv; make use of
19693 	libctf: check for problems with error returns
19696 	for CTF linkage in the PE linker yet.
19774 	for rv32 since version 2.2.  Therefore, make sure the version of q is larger
19793 	This patch adds new gas tests for the
19809 	libctf: Sanitize error types for PR 30836
19811 	return value for functions setting the ctf_errno value.
19907 	This header is only suitable for use on x86 hosts and is only included
19931 	I noticed that this case did not work for DAP.  This patch fixes the
19943 	but mainly by implementing tp_str for LazyString.
19954 	This happens because gdb.Value.assign (which was recently added for
19978 	This patch adds a regression test for this, and adds a scope cache in
20014 	We can still use the workaround of casting to another function type for both
20035 	This also requires fixing producer_is_gcc to stop returning true for
20073 	is supposed to return a valid closure for us, so we can determine the
20163 	support for LP64E (LP64 with reduced GPRs).
20169 		* doc/c-riscv.texi: Update the documentation to allow "lp64e".
20199 	sim: add distclean dep for gnulib
20216 	this was unnecessary for adding the bsefi and bsifi instructions.
20236 	the system's headers, and this is not true for all systems.
20279 	Update the mechanism to first search through the input files for a .note
20285 	As part for this update, also allow to request an executable stack
20302 	RISC-V: Add support for numbered ISA mapping strings
20303 	The elf psabi allows for mapping symbols to be of the form $x<ISA>.<any>
20345 	As GDB runs for a potentially extended period of time, if the BFD
20346 	cache holds a file descriptor for an open on-disk file, this can, on
20349 	This might, for example, prevent a user from recompiling their
20353 	Another problem, relates to bfd_stat, for BFDs that are using the BFD
20360 	the 'struct stat' for the old file, not the new file.
20362 	Now, for this second problem, we might be tempted to make use of an
20366 	can have a single call that should work for both local files, and for
20396 	Within bfd/cache.c change the type for max_open_files and open_files
20398 	type for bfd_cache_max_open() is also changed from int to unsigned.
20419 	[RFA] Fix for mcore simulator
20420 	I was looking for cases where a GCC patch under evaluation would cause test
20432 	worked fine for hosts with a 32 bit wide long and failed miserably for hosts
20436 	temporary.  It includes a simple test for sextb and sexth.  I have _not_ done a
20437 	full audit of the mcore simulator for more 32->64 bit issues.
20471 	members as function argument or return value for a dummy call.
20559 	    /* Start by clearing the flag that asks for our wait method to be called,
20580 	remote_state method.  Add a helper method for that, and for "can async"
20581 	as well, for symmetry.
20590 	m_async_event_handler_token) and add methods for the various operations
20611 	process target, there should be no regcaches for that inferior, so no
20638 	set_target_gdbarch is basically a setter for the current inferior's
20711 	gdb/python: implement support for sending custom MI async notifications
20734 	This is a preparation for implementing Python support for sending custom
20741 	LoongArch/GAS: Add support for branch relaxation
20786 	`cooked_index::get_main`, if available. Currently, for lack of a better name,
20793 	The main use case for this patch is in improving startup times when dealing with
20826 	  * ldlex.l (yy_input): Check for YY_CURRENT_BUFFER being NULL.
20834 …* elf32-i386.c (elf_i386_convert_load_reloc): Check for elf_x86_hash_table returning a NULL pointe…
20838 …* elflink.c (elf_gc_mark_debug_section): Check for bfd_section_from_elf_index returning a NULL poi…
20866 	This commit a new section for the next release branch, and renames
20886 	Add testsuits for new assembler option of mthin-add-sub.
20890 	as: add option for generate R_LARCH_32/64_PCREL.
20928 	/tmp/cc2xydTG.s:50: Error: operand size mismatch for `push'^M
20932 	/tmp/cc2xydTG.s:50: Error: operand size mismatch for `push'^M
20935 	/tmp/cc2xydTG.s:50: Error: operand size mismatch for `push'
20956 	Make the test-case work by using pushq instead of push for the
21033 	This patch has been tested for years of AMD Xilinx Yocto
21047 	  - An entry for the $_shell convenience function which is currently
21062 	of target_desc::expedite_regs (for each architecture)  was not updated
21081 	    updating for newline handling, but I think this is nicer, the
21127 	that for the next commit.
21153 	When I posted the previous patch for review Andreas Schwab pointed out
21156 	The fix for this is in the same area of code as the previous patch,
21325 	If you want to install GDB in a custom prefix, have it look for debug info
21332 	looking for distro-installed debug info in /usr/lib/debug.  For regular GDB
21339 	value for 'debug-file-directory', but it accepts only one directory and not
21342 	for "relocatability".
21388 	- for v2, dot is used both as separator character and mangling character, and
21389 	- for v3, dot is used as separator character and underscore as mangling
21413 	one has simply changed for gcc-11, so it's equivalent to using:
21536 	      gdb: add Python events for program space addition and removal
21614 	and GDB is waiting for a stop reply.  The problem here then, is why
21623 	to add one, but for the remote target, this would return false if the
21624 	remote is in async mode and the remote is currently waiting for a stop
21630 	refill the auxv cache now when it didn't need to for GDB 13.  This is
21638 	important for this bug).
21642 	program_space::~program_space.  The new_objfile observer for auxv does
21653 	for the current inferior.
21670 	a2827364e2bf, GDB was sometimes clearing the auxv cache for a random
21680 	for all of the matching inferiors?
21684 	cache for all inferiors in the current_program_space, we can update
21689 	      for (inferior *inf : all_inferiors ())
21696 	With this change we now correctly clear the auxv cache for the correct
21711 	target for all inferiors.  But if we had a truly multi-connection
21714 	Problem #1 I'm just ignoring for now, I guess at some point we might
21738 	The solution for problem #2 I already hinted at above, we should have
21743 	sending packets to the remote, and if the remote is waiting for a stop
21747 	The solution for problem #3 is included in this commit.
21749 	And, for problem #4, I'm not sure what the right solution is.  Maybe
21791 	  * testsuite/ld-elf/pr28158.rd: Adjust regexp to allow for section indicies larger than 9.
21799 	  * testsuite/ld-elf/dt-relr.exp: Skip for MUSL targets.
21803 	  * testsuite/ld-shared/shared.exp: Add XFAILs for tests that fail with the MUSL library.
21807 	  * testsuite/ld-arm/thumb-plt-got.d: Skip test for configurations using the MUSL library.
21853 	a direct stat call, this adds support for target: files, and fixes the
21902 	We actually see the same output, for the same reasons, when using a
21921 	BFD, the filename for this BFD is literally the string
21932 	for the file size), see memory_bstat in bfd/bfdio.c.
21950 	As I'm not specifically checking for, and then skipping, in-memory
21990 	"warning" prefix, and then call print_sys_errmsg.  And so, for these
22033 	gdb: remove use of a static buffer for building error strings
22034 	I noticed in procfs.c that we use a static buffer for building error
22078 	archive, and so there's no tests for this commit...
22127 	These settings are not appropriate for all targets including
22147 	for ZT0 and also core file generation.
22153 	sme2: Core file support for ZT register set
22154 	This patch adds support for ZT register dumps/reads for core files.  The
22158 	Unlike the enablement for SME1 and the ZA register, support for SME2 is rather
22186 	Since most of the code used by gdbserver for SME2 is shared with gdb, this
22187 	is a rather small patch that reuses most of the code put in place for native
22196 	sme2: Enable SME2 for AArch64 gdb on Linux
22211 	Provide documentation for the SME feature and other information that
22212 	should be useful for users that need to debug a SME-capable target.
22223 	- Sanity check for SME: Gives a brief smoke test to make sure the most basic
22234 	correctly and that all state dumped/loaded is sane.  This is exercised for
22257 	sme: Core file support for Linux
22274 	for most targets, it doesn't work correctly for AArch64 with SVE or SME
22277 	The correct approach for AArch64/Linux is to either have per-thread target
22280 	description for a given thread based on the various available register notes.
22285 	This patch goes for the latter, and adds a new gdbarch hook to conditionalize
22293 	Otherwise it should be fine for AArch64 Linux to use the corefile target
22311 	This works fine for almost all architectures. But AArch64 has a few
22316 	at the time of attachment/startup.  If, for example, the SVE vector length
22346 	The Linux Kernel defines a separate context for the TPIDR2 register in a
22367 	created for set A, but it is really dealing with a frame that was using set
22374 	For AArch64 we really need to be able to use the correct gdbarch for each
22381 	it and making it reusable for our purposes of calculating the previous frame's
22391 	signal context and infers the gdbarch for the previous frame.
22422 	and don't do anything for the z registers.
22435 	sme: Add support for SME
22450 	for now this should do.
22452 	Please note we have the same limitation for SME that we have for SVE, and
22470 	Regression-tested for aarch64-linux Ubuntu 22.04/20.04.
22498 	SME vector length is called streaming vetor length. The total size for
22505 	should be validated by attempting a ptrace call for one of the new register
22518 	is based on the vector length register SVG (VG for SVE).
22520 	This patch enables SME register support for gdb.
22532 	vector length for the Z registers, as they overlap the V registers).
22536 	only updates the amount of bytes for the particular type we're returning.
22546 	overriding only the bytes that we need for the return value.
22565 	handling of ptrace get/set requests for SVE.
22569 	the ptrace calls.  This is not very flexible and assumes one size for the
22598 	FPSIMD-formatted data we get from ptrace for the NT_ARM_SVE register
22631 	Fix register fetch/store order for native AArch64 Linux
22632 	I noticed we don't handle register reads/writes in the best way for native
22695 	This patch adds a mechanism for system register name alias detection
22702 	Where this is used is, for example, in `aarch64_print_operand' where,
22743 	then we really need a separate NT_GDB_TDESC for each thread, however,
22762 	MIPS: Fix `readelf -S bintest' test for n64 targets
22763 	Add a 64-bit traditional MIPS dump variant for the `readelf -S bintest'
22797 	      gdb: add Python events for program space addition and removal
22803 	Add regression test for instructionReference change
22808 	This patch adds a test case for that regression.  This required
22858 	debuginfod servers for an individual ELF/DWARF section associated with
22886 	Debug info for pragma import seems to not have been supported before gcc 8, so
22890 	an xfail for these.
22898 	[gdb/testsuite] Add KFAIL for PR ada/30908
22912 	the debug info for the function, because the corresponding object is not
22916 	Add KFAILs for the PR.
22928 	gdb: add Python events for program space addition and removal
22929 	Initially I just wanted a Python event for when GDB removes a program
22930 	space, I'm writing a Python extension that caches information for each
22931 	program space, and need to know when I should discard entries for a
22934 	But, it seemed easy enough to also add an event for when GDB adds a
22937 	Of course, we don't currently have an observable for program space
22952 	First, it is not possible to catch the NewProgspaceEvent for the very
22961 	can't catch the event for the first program space.
22967 	particularly worried about this for my use case, I'm using the event
23009 	packet while the remote target is waiting for a stop reply, and the
23011 	remote.c for details.
23015 	account for these warning messages in one of my tests, and it all
23057 	... which lobbies for tools to recognize the NO_COLOR environment
23060 	This patch implements this for gdb.
23071 	tc-microblaze.c - int compare for X_add_number.
23072 	The range check should be checking for the range
23075 	This patch has been tested for years of AMD Xilinx Yocto
23086 	and it fails for Little endian. This patch allows support for both
23089 	This patch has been tested for years of AMD Xilinx Yocto
23139 		in PLT entry for -z mark-plt.
23141 		DT_X86_64_PLT, DT_X86_64_PLTSZ and DT_X86_64_PLTENT for
23145 		(_bfd_x86_elf_get_synthetic_symtab): Ignore addend for
23164 		* ld.texi: Document -z mark-plt and -z nomark-plt.
23215 	Testing on Fedora 38 (correctly) shows 1 unsupported test for
23216 	native-gdbserver and 5 PASSes for the native target as well as
23222 	used additional_flags=-std=c11 for compiling both the shared object
23230 	My testing for this v2 patch shows the same results as with v1,
23261 	Added support in gas for mlittle-endian and mbig-endian flags as options.
23262 	Updated show usage for MicroBlaze specific assembler options
23265 	This patch has been tested for years of AMD Xilinx Yocto
23274 	 - added documentation for MicroBlaze specific options
23279 	PR29040 describes a FAIL for test-case gdb.threads/next-fork-other-thread.exp
23308 	to) display the disassembly for address 0, which led to the gdb segfault.
23314 	a MEMORY_ERROR for the first insn in tui_disassemble, it returns an empty
23363 	Thanks to Lancelot Six for testing and fixing this patch.
23415 	for the previous commit.
23450 	iterate over the objfiles list, and for each of those we check the
23464 	already been recently reloaded, we will not reload it for a second
23494 	inferior.  However, the ExecutableChangedEvent object is identical for
23500 	this into a separate commit, so see the next commit for details.
23530 	needs updating.  In the next commit I'll add a listener for this
23557 	actually be listening for the new_objfile observable instead, so now
23606 	My goal for the next few commits is to expose the executable_changed
23648 	path to the executable for this program space, or None if no
23654 	Accessing this attribute for an invalid program space will raise an
23676 	Progspace.objfiles, and then search for the objfile with a name that
23685 	gdb/doc: extend the description for Progspace.filename
23686 	Extend the description for Progspace.filename in the documentation to
23688 	for (e.g. that it is the filename passed to the 'symbol-file' or
23730 	file note for the XSAVE state, it writes a note of size 896, even though
23760 	i387_guess_xsave_layout for that combination, since there is no
23770 	  for this guess earlier was just not the best guess.  In the case that
23772 	  have the same values, so this only matters for a system where the
23780 	Add support to readelf for the PT_OPENBSD_NOBTCFI segment type.
23800 	Fix this by hardcoding nopie in the test-case, and for good measure in the
23813 	config/debuginfod.m4: Add check for libdebuginfod 0.188
23814 	Add check for libdebuginfod 0.188 in AC_DEBUGINFOD and if found
23817 	This macro indicates support for downloading ELF sections from
23824 …* elfcode.h (elf_slurp_symbol_table): Compute the symcount for non dynamic symbols in the same way…
23855 	Adjust gdb.thread/pthreads.exp for Cygwin
23959 	AVX512F counterpart ones, do this for FMA ones as well, requiring one
23964 	AVX512F counterpart ones, do this for VAES and VPCLMULQDQ ones as well.
23975 	  the same in the templates (which often isn't the case, for VEX
23978 	  extensions (the same will then be required for APX - it'll need to be
23982 	this logic will need revisiting for APX anyway, I'd like to keep it that
23983 	way for now. (Similarly a couple of if()-s which could be folded are
24025 	Add support for "pcaddi rd, symbol"
24037 	gdb/testsuite: add xfail for gdb/29965 in gdb.threads/process-exit-status-is-leader-exit-status.exp
24066 	gcc 13.2.1, I run into (layout adapted for readability):
24107 	need for this.  I think this is leftover from when this code was
24115 	children.  The methods are implemented for the no-op array printer,
24128 	We've known about the need for printer extensibility for a while, but
24141 	Fix a snafu in the new tests for reproducible archives that assumed a umask of 22.
24193 	    aarch64_feature_set contents for that array index.
24199 	(3) Provide convenience macros for initialising an
24200 	    aarch64_feature_set for:
24209 	cannot be nested.  So if a macro wants to do something for N individual
24211 	needs to be a way of deriving N, as a preprocessor token suitable for
24216 	initialiser for three features A, B and C would be written:
24221 	synonym for SHA2+AES, so the patch expands the former to the latter.
24225 	[gdb/dap] Fix dap for python < 3.8
24267 	Allow the use of SOURCE_DATE_EPOCH in the timestamps for members of static archives.
24297 …* dwarf.c (fetch_indexed_offset): New function. (read_and_display_attr_value): Use it for DW_FORM_…
24301 	Revert "arc: Add new GAS tests for ARCv3."
24304 	Revert "arc: Add new LD tests for ARCv3."
24310 	Revert "arc: Add new linker emulation and scripts for ARCv3 ISA."
24313 	Revert "arc: Update opcode related include files for ARCv3."
24319 	Revert "arc: Add new opcode functions for ARCv3 ISA."
24338 	- an BFD ARC target for ARCv1 and ARCv2 CPU families. It also works
24339 	for big-endian variants.
24340 	- an BFD ARC64 target for ARCv3 64bit machines. It also allows working
24342 	- an BFD ARC32 target for ARCv4 32bit machines. It also allows working
24403 	arc: Add new opcode functions for ARCv3 ISA.
24429 	        (find_format): Handle extract function for flags.
24431 	        (print_insn_arc): Update printing for various ARC architectures.
24442 	whatever we have for old ARC processors plus some ARCv3 spcific mods.
24474 		(parse_opcode_flags): Update for the case when the flags needs
24477 		(autodetect_attributes): PLT34 only available for ARC64.
24490 		(assemble_insn): Update for ARC64.
24497 	arc: Update opcode related include files for ARCv3.
24524 		functions for flags.
24530 	arc: Add new linker emulation and scripts for ARCv3 ISA.
24554 	adds the necessary bits for the new architecture in a similar way as
24555 	it is done for RISCV backend.
24594 	arc: Add new LD tests for ARCv3.
24595 	Add new linker tests for ARCv3 ISA. All the new tests are added in a
24615 	arc: Add new GAS tests for ARCv3.
24616 	Add new assembler tests for ARCv3 ISA. All the new tests are added in
24642 	arc: Update binutils arc predicate for tests.
24679 	 1726 |       for (inferior *inf : all_non_exited_inferiors (this))
24719 	gprofng: 30834 improve disassembly output for call and branch instructions
24736 		* src/Elf.cc: Get function names for the .plt section.
24820 	gdb/dap: check for breakpoint source before unpacking
24846 	name to print, for example.
24886 	[gdb/symtab] Error out for .debug_types section in dwz file
24899 	no support for it.  Enhancement PR symtab/30838 is open about the lack of
24984 	pretty-printer for pointers and references is quite simple.
25015 	In one spot, it will be convenient for a subsequent patch if the CU is
25021 	type allocator.  However, for a later patch it is more convenient if
25026 	Use gdb::checked_static_cast for catchpoints
25034 	Use gdb::checked_static_cast for code_breakpoint
25042 	Use gdb::checked_static_cast for tracepoints
25044 	Some functions are changed to accept a 'tracepoint *' now, for better
25051 	Use gdb::checked_static_cast for watchpoints
25097 	More type safety for symbol_search
25136 	[gdb/symtab] Fix overly large gdb-index file check for 32-bit
25165 	The amd-dbgapi library exposes a setting called "memory precision" for
25173 	    Some architectures allow the hardware to be configured to always wait for
25195 	reporting, but the watchpoint support for AMD GPUs hasn't been
25202 	used for testing support that feature.
25212 	ROCm / HIP tests should only run on Linux for now, existing gdb.rocm
25264 	Lancelot has accepted to take the role of maintainer for the AMD GPU
25266 	is an umbrella term for everything needed to make this work: the amdgcn
25269 	Thanks for accepting the role, and congratulations!
25310 	The current code returns different TLS_TBSS values for .tdata and
25349 	function for both paths.
25364 	After this commit, but calling bfd_cache_close_all for both paths this
25410 	While update_code_flag() checks for LM / i386, set_cpu_arch() so far
25424 	gdb/testsuite: explicitly test for stderr in gdb.mi/mi-dprintf.exp
25431 	of the test gdb.mi/mi-dprintf.exp. It also fixes an incorrect name for a
25446 	2^32-1 which is currently unaccounted for by GDB's code for outputting
25502 …Error while writing index for `/mesquite2/fedora-bugs/1773651/libgraph_tool_inference.so': gdb-ind…
25548 	I'm not sure how to create a test for this problem, this issue cropped
25551 	debugging the same binary built for x86-64 appeared to work just fine.
25557 	If anyone has ideas for a test I'm happy to work on something.
25567 	not being able to spawn for a large number of test-cases afterwards.
25582 	for {set i 0} {$i < 100} {incr i} {
25591 	Space used: 478248960 (+469356544 for this command)^M
25594 	Space used: 486629376 (+8380416 for this command)^M
25597 	Space used: 495009792 (+8380416 for this command)^M
25601 	Space used: 1308721152 (+8380416 for this command)^M
25609 	history, but the usage for the initial print seems somewhat excessive.
25622 	Space used: 8892416 (+0 for this command)^M
25625 	Space used: 8892416 (+0 for this command)^M
25628 	Space used: 8892416 (+0 for this command)^M
25632 	Space used: 8892416 (+0 for this command)^M
25663 	Fix a similar problem for Fortran:
25671 	The problem also exists for Ada:
25677 	but is fixed by the fix for C.
25685 	I managed to apply the compilation loop for the Ada variant as well, but with
25727 	While for most insns we can suppress their use with too wide operands
25760 	to avoid reverse dependencies towards SSE (just like we already do for
25764 	AVX nor VAES (similarly for {,V}PCLMULQDQ) would better keep the 128-bit
25765 	VEX-encoded forms available. Note that for this the VAES insns are moved
25768 	Without the movement, YMM use would be correctly recorded for the
25771 	enabled. Nor would behavior here then be the same as for VPCLMUL* insns.
25889 	Specialize std::hash for ptid_t
25915 	testsuite, fortran: Fix regression due to fix for ifort's 'start' behavior
25960 	FXSAVE Area" (and equivalent sections for FSAVE and XSAVE) or in the AMD
26023 	second as is correct for other cases with split frags.  This would
26038 	Set insn_type for branch instructions on aarch64
26045 		* opcodes/aarch64-dis.c (print_insn_aarch64_word): Set insn_type for
26052 	"fioff" stood for, making it difficult to map it to something in the
26097 	and noticed that compilation failure for one exec prohibited testing of all
26119 	could not find '.gnu_debugaltlink' file for dwzbuildid-mismatch^M
26149 	While looking at the .debug_aranges section, I noticed that the entries for
26242 	testsuite, fortran: adapt tests for ifort's 'start' behavior
26246 	Normally, the expected behavior of fortran_runto_main for these would be
26249 	Strangely, neither gfortran nor ifx seem to do this for these tests.
26250 	Instead, issuing 'start' in ifx (for either of the 2 tests) lets GDB
26252 	declaration line.  E.g. for vla-type it stops at
26275 	This worked fine for gfortran and ifx, but it seems that, when compiled
26297 	actually containing line table info for line 3.  Running gdb, breaking
26308 	so two mov instructions are being issued for this assignment one copying
26333 	for the mixed_func_1b function (when in that function's frame).
26376 	To make both outputs pass the test, I kept the additional argument for now and
26377 	made the regex for the emitted name of the last variable match any
26388 	kvx: Add a testcase for bundles with KVXMAXBUNDLEWORDS syllables
26396 	While the patch already committed for pr30793 prevents the asan error,
26406 	kvx_reassemble_bundle return true for success rather than zero, and
26407 	removed the unnecessary check for zero wordcount.
26411 		Fail if wordcount is too large.  Don't check for wordcount zero.
26413 		(print_insn_kvx): Rewrite code reading bundle_words as a for loop.
26421 	-- to disable a pretty-printer for a varobj -- then
26450 	from its "children" method, this does not really work for MI.  I
26464 	[gdb/symtab] Fix gdb-index writing for .debug_types
26536 	  for (int i = 0; i < syms.size (); ++i)
26538 	      /* We already know the name matches, so we're just looking for
26644 	Add testcase for generation of 32/64_PCREL.
26649 	Subtraction for labels that require static relocation
26664 	Therefore, added letter `t' after `X' for t-head operands, to differentiate
26670 		gas/doc/c-riscv.texi.
26672 		* config/tc-riscv.c (validate_riscv_insn): Added `t' after `X' for
26673 		t-head operands.  Minor updates for indents and comments.
26675 		* doc/c-riscv.texi: Minor updates.
26677 		* riscv-dis.c (print_insn_args): Added `t' after `X' for t-head
26678 		operands.  Minor updates for indents and comments.
26684 	The std::basic_string template type is only specified for
26692 		char32_t for 2- and 4-byte entry size, respectively.
26694 		(Stringpool_template): Explicitly instantiate for char16_t,
26707 	releasing memory for a fixup that just happened to be the same size as
26719 	Test-case gdb.ada/same_enum.exp is supposed to be a regression test for this
26738 	remove_extra_symbols has no effect for the test-case.
26755 	Multiple matches for red^M
26787 	 	  for (compunit_symtab *cust : objfile->compunits ())
26793 	In other words, when doing a lookup in the loop for a PU we duplicate the
26794 	lookup for a CU that is already handled by the loop.
26841 	libsframe.  See also previous similar commits for GDB_SUPPORT_DIRS.
26845 	configured contents.  Do as for the single gdb files and include
26858 	configuration file. These variables must be set for all gprofng tests.
26910 	Some embedded targets don't have full support for argc/argv.  argv
26912 	This causes problems for the regexps in the style.exp line-wrapping
26917 	and reworks some of the line-wrapping tests to account for the argv
26928 	are added, one for Ada and one for Rust.
26974 	"array-like".  This is the currently the case for certain
26989 	The test case for this will come in a later patch.
27003 	Refactor Rust code for slice-to-array operation
27005 	rust_slice_to_array, in preparation for subsequent patches that will
27024 	Fix is simple - don't ask for fewer than 1 space (since
27062 …for filedata being NULL. (section_name_print): Delete. (section_index_real): New function.  Return…
27063 	  * doc/binutils.texi: Document the new option.
27070 	M_VMSGEU and instead simply use an unused (for these macros) field to
27075 	RISC-V: Add stub support for the 'Svadu' extension
27076 	This commit implements support for 'Svadu' extension.  Because it does not
27104 	privileged specification version 1.9.1, CSRs for this extension are only
27123 		(riscv_csr_address): Add handling for new CSR classes.
27129 		and "mhcounteren" CSRs and note that they are now reused for
27249 	Note that for the test-case to be effective, the exec is not required to be in
27304 	With this patch, gdb.arch/i386-avx512.exp passes completely for me.
27316 	config: Fix host -rdynamic detection for build != host != target
27319 	The GCC_ENABLE_PLUGINS configure logic for detecting whether -rdynamic
27320 	is necessary and supported uses an appropriate objdump for $host
27328 	for $host binaries that runs on $build; that is, it's appropriate to
27332 	with -rdynamic as expected.  Also bootstrapped with no regressions for
27342 	Fix "usage" errors for some MI varobj commands
27343 	I noticed that the "usage" error for -var-set-frozen mentioned the
27364 	x86: correct source used for two non-AVX512 VEXWIG tests
27382 	This partly reverts 839189bc932e ("RISC-V: re-arrange opcode table for
27394 	RISC-V: Fixed the wrong expansion for pseudo vmsge[u].vx instructions.
27402 		* config/tc-riscv.c (vector_macro): Fixed the wrong expansion for
27420 	PR30806, CPPFLAGS are missing for bfd/chew, syslex_wrap and sysinfo
27437 	2. z80 fails since a, b, c, d are registers for z80.
27438 	3. hppa fails since .text sections aren't merged for relocatable link.
27441 		* testsuite/ld-elf/pr30791a.d: Xfail for generic and z80
27443 		* testsuite/ld-elf/pr30791b.d: Xfail for hppa and z80 targets.
27448 	This adds symbol::matches, a wrapper for symbol_matches_domain.  Most
27517 	convenient for me to merge this function into its only caller.
27524 	This commit adds a new test case for bug 27831.  See the contents
27525 	of the .exp file for a description of what it's about.
27535 	instructions for reproducing the bug here:
27545 	.c file is fairly simple as is the recipe for reproducing the problem.
27549 	assertion failure - for this run, the process id of the separately
27574 	set.  This, in turn, causes the "maybe_copied" flag to be set for
27580 	for the new (attach-created) objfile, however the "maybe_copied"
27581 	flag will still be set for the global symbol.  Had it been loaded
27583 	for the objfile.
27599 	assumes that it won't be called with the OBF_MAINLINE flag set for
27606 	infinitely for the case under consideration.)
27608 	So, the problem here is that the maybe_copied flag is set for the
27609 	symbol AND the OBJF_MAINLINE flag is set for the objfile.  As noted
27612 	OBJF_MAINLINE will be set for that objfile, leading to this
27646 	during a rebase in addition to making some changes to account for a
27658 	then 'object_format_has_copy_relocs' should be set for objfiles using
27690 	isn't recommended as a normal use case.  That said, it's bad for
27728 		* doc/webassembly.texi, doc/bfd.texi: Revert 8bb23cdb, adding
27770 	s_stab_generic at least does allocate the name for the stab section on
27772 	after issuing a warning don't release the memory, nor the memory for
27880 	copy_fields, and there's already a comment for the third.
27967 	- MEMORY_FILE is a new emulation paramter and sets the name for the
28012 	libbfd.texi zero size
28014 	libbfd.texi from libfd.h or libbfd.c.  Since both files exist and the
28044 	The problem is that were looking for "typedef void decltype\\(nullptr\\)"
28067 	Revert "Gold/MIPS: Use EM_MIPS instead of EM_MIPS_RS3_LE for little endian"
28075 	Revert "Gold/MIPS: Add targ_extra_size=64 for mips32 triples"
28083 	Revert "MIPS: Use 64-bit a ABI by default for `mipsisa64*-*-linux*' targets"
28099 	only defines them only for RV64 (because all Ventana's processors implement
28147 	   undeclared identifier is reported only once for each function it appears in
28227 	Use gdb::array_view for value_array
28308 	In test-case gdb.tui/pr30056.exp we check for:
28341 	getpkt and getpkt_or_notif_sane are just wrappers for
28373 	[gdb/testsuite] Check for sys/random.h in gdb.reverse/getrandom.exp
28392 	Fix this by testing for the presence of the header, such that we have instead:
28423 	for the major version and ignore the backported fixes.
28436 	- Reuse num_xmm_registers directly for the count of ZMM0-15 registers
28437 	  as is already done for the YMM registers for AVX rather than using
28440 	- Replace 3 identical variables for the count of upper ZMM16-31
28443 	  handling for the various sub-registers in this region are always
28496 	i387_set_xsave_mask as i387-fp.cc defaults to the SSE case used for
28507 	All of the tables describing the offsets of individual registers for
28509 	offsets.  Some tables (those for MPX registers and ZMMH registers) had
28517 	gdb: Support XSAVE layouts for the current host in the Linux x86 targets.
28540 	gdb: Support XSAVE layouts for the current host in the FreeBSD x86 targets.
28562 	x86 nat: Add helper functions to save the XSAVE layout for the host.
28589 	function should only be used as a fall back for older core dumps.
28611 	upper 128 bits of YMM registers for AVX.
28617 	component in the "standard" layout for a given CPU.  (There is also a
28623 	for state components in the extended region and hardcoded those
28626 	Specifically, AMD Zen3 and later processors do not leave space for the
28680 	concatenating multiple auxents for the old PE multi-aux scheme of
28697 		available.  Use external auxents for multi-aux long file
28710 	case with a C_FILE sym using multiple auxents for a long file name
28767 	MIPS: Use 64-bit a ABI by default for `mipsisa64*-*-linux*' targets
28769 	n32 or n64, rather than o32 for `mipsisa64*-*-linux*' targets, just as
28775 	Gold/MIPS: Add targ_extra_size=64 for mips32 triples
28776 	So we can enable 64bit ELF support for MIPS32 toolchain.
28785 	Gold/MIPS: Use EM_MIPS instead of EM_MIPS_RS3_LE for little endian
28789 	This problem didn't make some trouble for us, is due to that
28845 	A bfd_cleanup function needs to run when only tdata is correct for the
28864 	coffswap.h:coff_swap_aux_in.  The existing check only catered for
28915 	for purposes of finding the enclosing function or shared library.
28940 	Delete support for old compilers that don't support string
28984 	The getsymname function tries to emit an error using %ld for an
28986 	for uintptr_t.
29056 	The issue here is that the COFF offset for the fuzzed symbol's
29070 	COFF is not very common anymore. GCC removed support for it five
29075 	Update FreeBSD system calls for the upcoming 14.0-RELEASE
29081 	Fix for call feature having 9th function parameter and beyond corrupt values.
29091 	bfd: correct relocation handling for objcopy COFF -> ELF
29092 	While documented to not be reliable, it is still odd for objcopy to
29099 	for the VMA (which is always zero for object files anyway), but not for
29104 	altogether, which may suggest that a much simpler macro might do for the
29114 	Rather than special-casing rx-*-* for section30, force use of
29122 	the need to xfail section11 for LoongArch and RISC-V also goes away.
29152 	Code in som_write_symbol_strings neglected to allow for padding, which
29184 		for size == 64, and assert that rela_dyn_ already exists.
29186 		set when size == 64 for ELFv1.
29194 	gdb/solib-rocm: Detect SO for unsupported AMDGPU device
29261 	gdb/testsuite: Multiple improvements for gdb.reverse/insn-reverse.exp
29267 	for some reason, the test will emit an UNSUPPORTED and continue testing
29268 	by reversing from the current location and checking all registers for
29273 	This commit changes the UNSUPPORTED for a FAIL, since the test has in
29317 	code checks for an infinite loop by seeing if we land on the line that
29321 	Clang-15, for instance, associates 6. Because of this, the inferior used
29325 	This commit changes the test so that we check for PC instead of line
29336 	assumption that line tables will have an entry for the closing } in a
29355 	Clang does not add line information for lines that only contain a
29367 	kvx-dis.c:1078:10: error: (near initialization for 'dec.nb_ops')
29379 	As commit fa4f2d46f9 did for x86, there a few other targets that
29380 	wrongly use the output section rather than the dynamic section for
29384 		section for DT_JMPREL.
29386 		section for DT_JMPREL and DT_PLTRELSZ.
29388 		and for DT_PLTGOT and when adjusting DT_RELA.
29500 	values for DT_JMPREL and DT_PLTRELSZ - they cover the entire ELF section,
29510 		section for DT_JMPREL and DT_PLTRELSZ.
29590 …(display_debug_ranges): Only show debug ranges whose version is suitable for the secction being di…
29604 	replacement for this commit:
29611 	which solved the two stop problem, but only for the CLI.  Before both
29618 	commit 2e411b8c68eb tried to solve (for the CLI) and b1c0ab20809a
29619 	extended also address the issue for MI too.
29632 	this fixes things for both CLI and MI.
29638 	notification will be for the location where the inferior call stopped,
29663 	commit this was only done for the case where the inferior function
29668 	now call async_enable_stdin for each of the three cases listed above,
29719 	  Error in testing condition for breakpoint 1:
29745 	  Error in testing breakpoint condition for breakpoint 1:
29771 	  Error in testing condition for breakpoint 1:
29793 	there's a demand for it.
29815 	responsible for building the 'frame={...}' part of the pattern.
29825 	Currently, each target backend is responsible for printing "[Thread
29831 	with gdbserver, letting it run for a bit, and then pressing Ctrl-C, we
29884 	... and sometimes wants to suppress the notification for the main
29973 	      Introduce "static constructor" for mi_parse
29976 	on the list the reasons for seem to have been lost[1].  Given there
29978 	propose we should do that for now.
30021 	gdb/testsuite: improve MI support for inferior specific breakpoints
30041 	easier to write MI tests for inferior specific breakpoints.
30090 		(elfNN_kvx_relocate_section): Similarly for r_offset, and
30103 	through O_md32 enums are for use by target code.  Worse, kvx-parse.c
30139 		* config/tc-kvx.h (TOKEN_NAME): Check for tok <= 0, not just -1.
30159 		* elfnn-kvx.c (kvx_relocate): Update for
30177 	bfd_get_symbol_leading_char, which may be zero, didn't check for "".
30180 	in dbxread when looking for "__DYNAMIC" that also might access past
30187 	bfd_get_symbol_leading_char, which may be zero, didn't check for the
30238 	done for yacc in yy-remap.h.
30240 	Likewise for targets frv and lm32, the two other targets that include
30243 	Likewise for more cgen symbols that I got the same warning for when using
30267 	aarch64: Improve naming conventions for A and R-profile architecture
30269 	for the A-profile architecture omitted the trailing `A' such that, for
30270 	example, assembling for `-march=armv8.4-a' set the `AARCH64_ARCH_V8_4'
30276 	`R' for the R-profile.  Referring back to the example above, the flag
30277 	set for `-march=armv8.4-a' is better characterized if labeled
30388 	don't consume data (which doesn't make sense for a table of names).
30400 	and it's better to choose some default for a user passing an unknown
30409 		unexpected arch or mach.  Default to bfd_mach_kv3_1 for
30459 		* doc/c-bpf.texi (BPF Instructions): Remove erroneous neg and
30480 	Teach binutils/BFD about it so that gdb can make use of it for reading
30482 	correct identification for the NT_ARM_ZT register set.
30677 	accidentally.  The first problem I hit is that sim looks for cgen in a
30679 	layout set up for opcodes rather than sim.  Fix that by making both
30695 		* cris/local.mk: Add $(srcdir) to paths for regenerated source.
30740 	psympriv.h was intended for use by code that created partial symbols.
30759 	symbol for which both return true; both may return false. Therefore
30765 	RISC-V: Report "c or zca" for INSN_CLASS_C when error reporting.
30798 	This commit extends the breakpoint mechanism to allow for inferior
30801 	As GDB gains better support for multiple connections, and so for
30809 	This commit adds a new 'inferior' keyword that allows for the creation
30821 	However, I'm leaving that as an exercise for another day.  For now,
30841 	optimisation for thread-specific breakpoints.  Once this series has
30865 	Fix this by renaming to ada_exp_yysymbol_kind_t and likewise for other .y
30879 	the source for debugging, but don't want it for comments in bfd.pot
30906 	Re: sim frv: Add a missing return value for frvbf_check_acc_range.
30925 	Fix this by using instead std::pmr::polymorphic_allocator for c++20.
31091 		* doc/c-bpf.texi (BPF Instructions): Add note about how numerical
31092 		literal values are interpreted for instruction immediate operands.
31110 	ld: ld-lib.exp: log failed dump.out contents for debugging
31140 	Fix this by inhibiting the scan_attributes self-recursion for self-references.
31145 	Note that this doesn't fix the same problems for the more complicated case of:
31154 	but the approach for deciding whether to fix pathological dwarf cases is as
31202 	includes a confounding case for array aggregates as well, but as these
31257 	so for Linux this will be all-stop on top of non-stop.
31273 	immediately exits.  The vfork-parent will wait for the vfork-child and
31274 	then blocks waiting for gdb.  Once gdb has released the vfork-parent,
31323 	     EXITED event for the vfork-child and the VFORK_DONE event for the
31373 	     for all threads, this causes the vfork-child to be resumed.  Then
31380 	     EXITED event for the vfork-child and the VFORK_DONE event for the
31383 	  6. We are now in a situation identical to step (5) as for
31394 	proceed_resume_thread_checked just once, for the current thread,
31398 	thread, read the commit message for the justification for this change.
31421 	What I noticed was that for the all-stop-on-non-stop, after commit
31424 	back), so if feels like we there's no harm in just waiting for the
31435 	Having done that, now the process is for all-stop-on-all-stop after
31451 	     for all threads, this does not resume the vfork-parent (because
31455 	At this point we are back in the same situation as for
31472 	This patch adds support for the Cortex-A720 CPU to binutils.
31482 		* doc/c-aarch64.texi: Update docs.
31527 	locations, one for each inferior.
31553 	From what I can tell, inferior::priv is reserved for the
31563 	Updated Russian translation for the bfd directory
31623 	RISC-V: Add support for the 'Zihintntl' extension
31643 		* testsuite/gas/riscv/zihintntl.s: New test for 'Zihintntl'
31647 		* testsuite/gas/riscv/zihintntl-base.s: New test for correspondence
31702 	Fix this by renaming to ada_exp_YYSTYPE and likewise for other .y files.
31704 	Likewise for yyalloc.
31749 	  for software breakpoints before detaching.  In particular, threads
31754 	  kernels, ::detach fixes up the PC for any SIGTRAP stop whose potential
31766 	structure which trackes the number of existing and running LWPs for
31768 	set of LWPs currently resumed for each process.
31772 	current inferior's process for a wildcard ptid.  If a resumed process
31781 	later.  If not, send a SIGSTOP to the process and wait for it to stop.
31782 	If the event reported by the wait is not for the SIGSTOP, queue the
31783 	event and remember to ignore a future SIGSTOP event for the process.
31787 	processes (via pid), not for an event from a specific thread.
31789 	Other changes in this commit handle bookkeeping for the per-inferior
31797 	If wait_1 finds an event for a thread or process that does not match
31799 	If the event is for a specific thread, suspend the thread and continue
31800 	the associated process before waiting for another event.
31940 	If ADDRESS is provided, dump only the file for that address.
31952 	If ADDRESS is provided, dump only the file for that address.
31962 	the symbols for the file with code at that address".
31998 	ld: fix relocatable, retain7a target pattens for HPPA
32001 	Put back the old pattern for hppa-*-linux* and add hppa[12]*-*-linux* to cover
32094 	Re: gdb: warn unused result for bfd IO functions
32110 	to reinsert software single-step breakpoints for a LWP when
32123 	assert for this case was NOT a good fix - a study of the log file for
32142 	      /* GDBserver must insert single-step breakpoint for software
32150 	The C code for the test case was loosely adapted from the reproducer
32151 	provided in Zhiyong's bug report for this problem.  The .exp file was
32154 	"on" from the loop for non-stop as it was failing on all architectures
32157 	works.  I also increased the number of iterations for the loop running
32159 	until the loop counter exceeded 100 iterations.  The C file for the
32221 	Also, I see no regressions when running the entire test suite for
32224 	using --target_board=native-gdbserver, I also see no regressions for
32225 	the entire test suite for x86-64 and aarch64 running Fedora 38.
32252 	Use the substituted value for GCDFLAGS instead of hardcoding $(CFLAGS) so
32283 	Disable warnings as errors for STAGEautofeedback.
32288 	This patches disables warnings as errors for STAGEautofeedback.
32292 		* Makefile.tpl: Disable warnings as errors for STAGEautofeedback
32301 	Fix collection and processing of autoprofile data for target libs
32304 	turning off debug info for this stage.
32312 		* Makefile.tpl: Remove -gtoggle for STAGEautoprofile
32316 	Collect both user and kernel events for autofdo tests and autoprofiledbootstrap
32317 	When we collect just user events for autofdo with lbr we get some events where branch
32325 		* Makefile.tpl: Collect both kernel and user events for autofdo
32335 	    - Add support for bootstrapping the D front-end.
32339 	runtime modules, only libdruntime is built for the bootstrap stages.
32358 		* Makefile.tpl (POSTSTAGE1_HOST_EXPORTS): Fix command for GDC.
32379 	Do not use HAVE_DOS_BASED_FILE_SYSTEM for Cygwin.
32382 		for CYGWIN.
32411 	Generic configury support for shared libs on VxWorks
32414 	for libraries variants where this is generally supported (rtp,
32424 		and friends for rtp !large. Assume the linker has the required
32518 	There were two uses for the Darwin host config fragment:
32520 	The first is to arrange for targets that support mdynamic-no-pic
32532 	of toolchains for which it is included which reduces clutter in
32546 	Source code for mcfgthread is available at <https://github.com/lhmouse/mcfgthread>.
32549 		* gthr.m4 (GCC_AC_THREAD_HEADER): Add new case for `mcf` thread
32556 	with LTO to work so we need to pass down NM just like we do for ranlib
32566 		* configure.ac: Drop GCC configury for hpux10
32579 		Add NCN_STRICT_CHECK_TARGET_TOOLS entry for gm2.
32580 		Add GCC_TARGET_TOOL entry for gm2.  (compare_exclusions)
32586 		Add entry for language=m2 with gcc-check-target=check-m2
32588 		* Makefile.tpl (BUILD_EXPORTS): Add definition for GM2
32589 		and GM2FLAGS.  (HOST_EXPORTS) Add definition for GM2.
32590 		(BASE_TARGET_EXPORTS) Add definition for GM2.
32600 	When the GCC build runs GCC_FOR_TARGET, e.g. for selftests or for
32602 	patch arranges for TFLAGS to be passed from the top level down to gcc
32624 	not respect the user's choice for OBJDUMP.
32631 	Remove support for Intel MIC offloading
32649 	of the host_pie setting so that the logic for setting PICFLAG must be amended
32650 	for Darwin.
32655 	is not given in the configure line.  To cater for this we pass the current
32660 		* configure.ac: Adjust the logic for shared and PIE host flags to
32661 		ensure that PIE is passed for hosts that require it.
32713 	up for testing, so it is preferrable not to build it.
32720 	Darwin : Update libtool and dependencies for Darwin20 [PR97865]
32723 	for shared libraries.
32727 		for Darwin20.
32733 	__builtin_{clz,ctz} for count_{leading,trailing}_zeros.  This improves
32761 	but only 16KiB pages are supported for now.
32768 		(VTV_PAGE_SIZE): Set VTV_PAGE_SIZE to 16KiB for loongarch64.
32777 	The NUMCHILD value for the "A_String_Access" test differs for X86 and
32798 	The patch adds a second possible result string for the test
32801 	Currently for the mi_var_access.exp test VAROBJ_UPDATE_RESULT.TYPE_CHANGED
32810 	Fix Python documentation for range type fields
32829 	RISC-V: Reflect actual range of vlen for hashing
32836 	less than 16 (but 4 or greater), to support vector subset extensions for
32841 	gdb: warn unused result for bfd IO functions
32884 	warn unused result for bfd IO functions
32913 		Fix bitrotted code to look for first section with non-zero filepos.
32959 	RISC-V: Remove support for non-existing 'Zve32d'
33017 	  for (const auto &entry : m_deferred_entries)
33028 	So, the root cause of this is that when we lookup the parent for DIE 0x25, we get
33067 	When doing "maint print objfiles" for the exec of test-case
33119 	Fix gdb.ada/O2_float_param.exp for PowerPC
33128 	The printing of the address for the frame is done by function
33129 	print_frame in gdb/stack.c.  If SAL.IS_stmt is false for the frame,
33150 	Search for "Finding new threads in the inferior".
33153 	better to arrange for such notification if something on the gdb side
33173 	This patch adds support for the Cortex-A520 CPU to gas.
33181 		* doc/c-aarch64.texi: Update docs.
33213 	The following FAIL is a consequence of the first FAIL, so require for the
33259 		* bpf-opc-c (bpf_opcodes): Use %sw for AAD32, AOR32, AAND32
33264 		* testsuite/gas/bpf/atomic-be-pseudoc.d: Use "w" for source reg
33284 	Dump of assembler code for function main:
33343 		(bfd_seek): Reinstate optimisation for seek to same position.
33348 	Use move capture in gdb_demangle when compiling for c++14 or higher, to save a
33358 	ld: Fix retain7a.d XFAIL/notarget entry for hppa
33360 	* ld/testsuite/ld-elf/retain7a.d: Fix XFAIL entry for hppa to match
33363 	ld: Fix relocatable.d XFAIL/notarget entry for hppa
33365 	* ld/testsuite/ld-elf/relocatable.d: Fix notarget entry for hppa to match
33384 	If $inferior_pid doesn't refer to a single process for some reason, this
33440 		for sub-experiment filtering.
33444 	RISC-V: move comment describing rules for riscv_opcodes[]
33458 	that any variables named, for example "allocated", could not be
33466 	the case when GDB has access to symbols for abs from libm. This was
33506 	will cause the symtab expansion for the containing CU.
33509 	partial symbol table to find language for main") a feature was added to avoid
33512 	This feature stopped working after commit 7f4307436fd ("Fix "start" for D,
33517 	- for language D, "main" was found instead of "D main", and
33518 	- for Rust, the correct function was found, but attributed the wrong name
33553 	However, only "cacheable" BFDs will be eligible for reopening when
33590 	The documentation for the Python free_objfile event registry uses the
33604 	This serves as regression test for PR symtab/30718.
33611 	[gdb/testsuite] Move "maint wait-for-index-cache" ALAP in gdb.base/index-cache.exp
33618 		gdb_test_no_output "maintenance wait-for-index-cache"
33626 	- moving the "maintenance wait-for-index-cache" to proc check_cache_stats, and
34181 	Likewise for the dwz build id, which likely suffers from the same issue.
34275 	  index-cache entry for $exec needs to be written
34291 	Check for output buffer overruns.
34301 	a) there are both local-dynamic and global-dynamic tls accesss for a
34389 	+	      /* In order for the index to work when read back into
34461 	integer for the name of a stack frame, like:
34511 	  Error in testing condition for breakpoint 1:
34527 	not to print the frame during the stop announcement, and for the CLI
34528 	this is fine, however, it was pointed out that for the MI this still
34550 	  &"Error in testing condition for breakpoint 1:\n"
34570 	calling normal_stop at all for the stops which should not be reported
34658 	sprintf return value rather than using strlen, for get_machine_flags.
34669 	to prevent buf + r being out of bounds for the second snprintf call.
34752 		for alias match rather than recreating.
34812 	for a single char, or a two char string.
34846 	RISC-V: Add support for 'Zvfh' and 'Zvfhmin'
34847 	This commit adds support for recently ratified vector FP16 extensions:
34851 …<https://github.com/riscv/riscv-v-spec/blob/master/v-spec.adoc#zvfhmin-vector-extension-for-minima…
34852 …<https://github.com/riscv/riscv-v-spec/blob/master/v-spec.adoc#zvfh-vector-extension-for-half-prec…
34899 	that's too late for earlier uses.
34911 	[gdb/dap] Disable DAP for python <= 3.5
34915 	- disabling the dap interpreter for python version < 3.5
34916 	- returning 0 in allow_dap_tests for python version < 3.5
35006 	Don't supply DAP 'path' for non-file shared libraries
35023 	Implement ValueFormat for DAP
35024 	This patch implements ValueFormat for DAP.  Currently this only means
35029 	should be handled.  I'll file a new gdb bug for this, and perhaps an
35034 	  that we only had tests for "hover" failing, not for it succeeding.
35042 	I noticed that the support for memoryReference in the "variables"
35053 	  emit this for pointer types.  There's no spec support for the
35060 	Add DAP support for C++ exceptions
35061 	This adds DAP support for the various C++ exception-catching
35095 	event code to breakpoint.py in preparation for the change.
35104 	would include a relative path name for the "path" component.
35143 	ensures that this is done for the private method of FrameDecorator.
35162 …Fix "--only-keep-debug for ELF relocatables" binutils test for compilers which add .debug_macro se…
35168 	gas: rework timestamp preservation on doc/asconfig.texi
35194 		* src/Command.cc: Add commands for gprofng GUI.
35195 		* src/gprofng.rc: Set defaults for gprofng GUI.
35205 	case that a race is detected, but we see the full stack trace only for one of
35315 	other events are cached for later calls of the wait method.
35329 	- The driver creates the runtime activation for inferior 2 and writes to
35331 	- GDB has inferior 1 selected and calls target_wait for some reason.
35333 	  all events from the driver, including the runtime activation event for
35336 	The fix for this problem is simple.  To avoid such problem, we need to
35337 	make sure that amd_dbgapi_target::wait only pulls events for the current
35390 	Updated Spanish translation for the gprof directory
35448 	This patch adds support for EF_BPF_CPUVER bits in the ELF
35450 	version for which the object file has been compiled for.
35505 	This patch makes the BPF assembler to throughfully check for overflow
35516 		(encode_insn): Check for overflow in constant immediates.
35560 	The BPF V4 ISA thus introduced support for a jump-always
35581 		(md_longopts): Likewise for -mno-relax.
35609 		* doc/c-bpf.texi (BPF Options): Document -mno-relax.
35636 	After looking into this for a while (with no results) using ASan and
35663 	MIPS: Support `-gnuabi64' target triplet suffix for 64-bit Linux targets
35664 	Make the n64 ABI the default for 64-bit Linux targets specified with
35665 	`-gnuabi64' suffix included in the target triplet, for configurations
35681 	ones for a more exact match.  So this is best deferred to a separate
35685 	discards a number of trailing entries from output here for n64 composed
35744 	contents of either as irrelevant for all the affected compact EH tests,
35796 	`objdump' for such relocations is:
35811 	relevant for generic or even some MIPS tests, so optionally match them
35813 	for MIPS/OpenBSD targets from gas/elf/missing-build-notes.d, removing
35881 	Several MIPS test cases are suitable for the n64 ABI if not for the
35887 	mips64-openbsd  -FAIL: MIPS DSP ASE for MIPS64
35895 	mips64el-openbsd  -FAIL: MIPS DSP ASE for MIPS64
35938 	not relevant for the test cases concerned, fixing these regressions:
35977 	mips-sgi-irix6  -FAIL: MIPS16 interlinking for local functions 1 (n32)
35989 	The MIPS16 interlinking test for local functions expects to be assembled
35995 	Use the per-ABI framework then to run the test explicitly for o32 and
36003 	with n32 testing for some targets, and ultimately removing these
36006 	mips64-openbsd  -FAIL: MIPS16 interlinking for local functions 1
36007 	mips64el-openbsd  -FAIL: MIPS16 interlinking for local functions 1
36017 		for o32 and n32 ABIs only.
36021 	MIPS/GAS/testsuite: Force o32 for tests expecting 32-bit addressing
36053 	mips64-openbsd  -FAIL: Paired LL/SC for mips64r6 (mips64r6)
36075 	mips64el-openbsd  -FAIL: Paired LL/SC for mips64r6 (mips64r6)
36089 	MIPS/LD/testsuite: Run `got-dump-1' for o32/n32 ABIs
36092 	test already for the n64 ABI.
36095 	for o32 and n32 ABIs only.
36098 		* testsuite/ld-mips-elf/mips-elf.exp: Run `got-dump-1' for o32
36105 	output and specific header sizes.  Disable it for `mips64*-*-openbsd*'
36106 	for these targets then, removing these failures:
36175 	Convert the tests then to use the per-ABI framework and run them for the
36195 	Similar tests for the n64 ABI can be added separately, using suitable
36215 	Compact EH #7 tests use output templates that are not suitable for the
36225 	Suitable corresponding tests for the n64 ABI can be added separately.
36228 		* testsuite/gas/mips/compact-eh-eb-7.d: Exclude for
36288 	created by empty-address-2* and empty-address-3* for some reason, and
36292 		* testsuite/ld-scripts/empty-address-2a.d: xfail for xcoff.
36314 	This fixes failure of the "extract symbols" test for rs6000, where
36316 	coffcode.h the same problem might occur for coff/pe too, but doesn't
36323 		* objcopy.c (setup_section): Clear SEC_LOAD for --extract-symbol.
36409 		* doc/c-i386.texi: Document .pbndkb.
36424 		(rm_table): New entry for pbndkb.
36440 		* doc/c-i386.texi: Document .sm4.
36469 		* doc/c-i386.texi: Document .sm3.
36507 		* doc/c-i386.texi: Document .sha512.
36557 		* doc/c-i386.texi: Document avx_vnni_int16.
36613 		* doc/c-bpf.texi (BPF Special Characters): Add note that '#' may
36614 		be used for inline comments.
36630 	60ebc257517 ("Fixes a buffer overflow when compiling assembler for the MinGW
36651 		* testsuite/gas/bpf/alu.s: Add test for NEGI and NEG32I.
36689 	Note that this is for the amd64 case (using gdb.dwarf2/typeddwarf-amd64.S).
36724 	Type commands for definition of "foo".
36735 	Type commands for definition of "foo".
36798 	- the destructor for known_window_types is called, which triggers calling the
36799 	  destructor for the only element E of m_window_maker_list.  The destructor
36801 	- the destructor for m_window_maker_list is called.  It's empty, so it's a nop.
36807 	- the destructor for m_window_maker_list is called.  This doesn't destroy it's
36809 	- the destructor for known_window_types is called, which triggers calling the
36810 	  destructor for E.  An attempt is done to remove E from m_window_maker_list,
36901 		* doc/c-bpf.texi (BPF Instructions): Update accordingly.
36918 	get_symbol_name currently returns "" for the usual STT_SECTION symbols
36924 		std::string.  Return section name for STT_SECTION symbols with
36930 		type and symbol for relocation overflows.
36936 		group name matches current group for section.
36957 		* doc/c-bpf.texi (BPF Instructions): Document atomic exchange and
36969 		(enum bpf_insn_id): New entries for BPF_INSN_ACMP{,32} and
36973 		* bpf-opc.c (bpf_opcodes): Add entries for ACMP{,32} and
36979 	This patch updates the pseudo-C dialect templates for the BPF v3 atomic
36980 	instructions.  The templates match the strings emitted by clang -S for
36986 		* doc/c-bpf.texi (BPF Instructions): Update entries for atomic
37002 		* bpf-opc.c (bpf_opcodes): Update pseudo-C dialect templates for:
37074 …* doc/binutils.texi (objcopy): Document change in behaviour of objcopy's --preserve-dates command …
37077 	  * ld.texi (--insert-timestamp): Document change in behaviour.
37081 	Updated translations for bfd, gold and opcodes
37086 	In LoongArch, the R_LARCH_IRELATIVE relocations for local ifunc symbols are
37118 	Now, the immediate overflow check before rightshift for easier understand.
37148 	bpf: gas,include,opcode: add suppor for instructions BSWAP{16,32,64}
37149 	This patch adds support for the BPF V4 ISA byte swap instructions to
37167 		* bpf-opc.c (bpf_opcodes): Add entries for the BSWAP*
37174 		* doc/c-bpf.texi (BPF Instructions): Document BSWAP* instructions.
37189 		* doc/c-bpf.texi (BPF Instructions): The pseudoc syntax for MOVS*
37194 	bpf: gas,opcodes: fix pseudoc syntax for MOVS* and LDXS* insns
37202 		* bpf-opc.c (bpf_opcodes): Fix pseudo-c syntax for MOVS* and LDXS*
37209 		* doc/c-bpf.texi (BPF Instructions): Fix pseudoc syntax for MOVS*
37227 	bpf: add support for jal/gotol jump instruction with 32-bit target
37228 	This patch adds support for the V4 BPF instruction jal/gotol, which is
37257 		* doc/c-bpf.texi (BPF Instructions): Document new instruction
37272 		* bpf-opc.c (bpf_opcodes): Add entry for jal.
37304 	operating on the sibling thread, so I think it makes sense, for
37309 	that the vfork-parent check now happens after the checks for whether
37420 	makes it easy to find the objfile for a given address.
37423 	for my original need, it's not clear to me whether I should close the
37438 	Document array indexing for Python gdb.Value
37439 	I noticed that the documentation for gdb.Value doesn't mention array
37446 	bpf: opcodes, gas: support for signed load V4 instructions
37457 		* opcode/bpf.h (enum bpf_insn_id): Add entries for signed load
37465 		* bpf-opc.c (bpf_opcodes): Add entries for LDXS{B,W,H,DW}
37477 		* doc/c-bpf.texi (BPF Instructions): Document the signed load
37482 	bpf: opcodes, gas: support for signed register move V4 instructions
37496 		(enum bpf_insn_id): Add entries for MOVS{8,16,32}R and
37503 		* bpf-opc.c (bpf_opcodes): Add entries for MOVS{8,16,32}R and
37512 		* testsuite/gas/bpf/alu32.s: Likewise for movs32 instruction.
37525 	Remove redundant @findex from python.texi
37527 	@defun.  This patch removes all such uses from python.texi, plus a
37534 	Fix typo in py-type.c docstring
37543 	allows for convenient updates.  This patch implements this for gdb's
37585 	based on CGEN.  Please see that commit log for more information.
37599 	CGEN is cool, but the BPF architecture is simply too bizarre for it.
37605 	all examples of what makes it a PITA to continue using CGEN for this
37622 	  opcodes table for BPF.
37639 	  relocations are used for section-relative 16-bit offsets used in
37642 	* The disassembler now has support for the "pseudo-c" assembly syntax of
37646 	* The disassembler now has support for dumping instruction immediates in
37652 	  fixed there.  The assembler generic tests that were disabled for bpf-*-*
37682 	object containing such program is loaded once for each device available,
37686 	GDB gets higher than the allowed number of opened files for the process.
37692 	underlying file once for each shared library it sees.  That means that
37750 	The reason for the difference is that the optimized out variable aaa:
37774 	Tested gdb.opt/static-optimized-out.exp with gcc-8 to gcc-12, for which we now
37780 	and with gcc 7.5.0 and clang 13.0.1, for which we still consistently get:
37785 	due to missing debug info for the variable.
37794 	[gdb/tui] Fix superfluous newline for long prompt
37813 	     rl_redisplay will not do it for us.  If the calling application has a
37863 	The use case for rl_already_prompted seems to be:
37941 	spaces, and so when accessing memory for those address spaces, we must
37955 	inferior_ptid point to the thread, for example.
37968 	Updated Romainian translation for the opcodes directory
38036 		* configure.ac (od_vectors): Set up for --enable-targets=all.
38058 	Updated Swedish translation for the binutils subdirectory
38176 	accepting '^' only.  But let's do this anyway, if only for
38195 	The comment suggests these are to allow for output from a vforked
38201 	this test, I left the test running for a couple of hours, and tried
38213 	This commit provides tests for all of the bugs fixed in the previous
38238 	I have cleaned things up a little, for example, making use of
38249 	  gdb: don't restart vfork parent while waiting for child to finish
38299 	  for the vfork child to complete,
38317 	  handle_vfork_child_exec_or_exit for details).  Further the comment
38343 	  waits for the thread, instead of a stop due to signal, we instead
38361 	similar case that checks for the vfork parent when we plan to follow
38373 	If you do want to reproduce this failure then you will for certainly
38416 	  No unwaited-for children left.
38419 	Notice the "No unwaited-for children left." error.  This is incorrect,
38429 	parent process, the inferior for the vfork parent will have its
38440 			that inferior is waiting for a vfork-done event (this means
38441 			breakpoints are out for this inferior).  */
38456 	nullptr (see above for why).
38461 	        that inferior is waiting for a vfork-done event (this means
38462 	        breakpoints are out for this inferior).  */
38496 	'if' block is not going to exist for long.
38510 	gdb: don't restart vfork parent while waiting for child to finish
38525 	  and creates an inferior and thread for the vfork child,
38535 	  4. GDB waits for the next event, eventually entering
38542 	  6. Unfortunately, resume_stopped_resumed_lwps doesn't check for
38561 	  handle_vfork_child_exec_or_exit for details).  Further the comment
38587 	  waits for the thread, instead of a stop due to signal, we instead
38616 	convinced it must exist: if we forget vforks for a moment, in step #13
38626 	pointing this out just for completeness.
38635 	If you do want to reproduce this failure then you will for certainly
38747 		* ld.texi (ALIGNOF, SIZEOF): Update and mention NEXT_SECTION.
38783 	ERROR: no fileid for xerxes
38968 	Add a have_native_target helper function for use with require.
38976 	register set for the architecture.
38992 	register set for the architecture.
39010 	gdb/doc: document '+' argument for 'list' command
39011 	The command 'list' has accepted the argument '+' for many years already,
39013 	help text for the command.  This commit documents it.
39040 	gdb/cli: add '.' as an argument for 'list' command
39046 	to do that using '.' as a new argument for the 'list' command.  If the
39051 	would make the resulting log harder to read for no benefit, it was
39062 	could be re-used. As a preparation for those commits, this one factors
39072 	 - we did not catch a timeout for each test.
39084 		for native testing.
39132 		* configure.ac (AIX_WEAK_SUPPORT): Don't set for aix5.[01].
39135 		for aix < 5.2.
39153 	Looking at the sole caller, I see this can only be called for two
39175 		symbols for a file with no section headers until all the
39190 	Fix this by removing the !HAVE_WBORDER case, which was introduced for Ultrix
39275 	.noinit and .persistent for msp430
39356 	a few others can easily be converted to do so as well. Note that for it
39368 	opcode bytes similar to before, make BadOp() also account for VEX/XOP/
39378 	While there also use Ux for VPMOV{B,W,D,Q}2M, where decoding through
39387 	going through vex_len_table[] for two of the insns.
39395 	also eliminates mis-named enumerators (we use M_1 for register forms).
39412 	Most of them use Mx already for the memory operand, which rejects the
39413 	register form of the insn. Use that operand type also for the two EVEX
39415 	the register forms), compensating by flagging broadcast as bad for all
39430 	there for {,V}LDDQU drop hoing through mod_table[] - OP_M() rejects
39467 	Add Ada scope test for DAP
39468 	This adds a DAP test for fetching scopes and variables with an Ada
39478 	The no-ops pretty-printers that were introduced for DAP have a classic
39480 	strange behavior; for example not showing the children of a variable
39528 	When reading the doc string for execute_frame_filters, I wasn't sure
39567 	Use unique_ptr for trace_dirname
39575 	Use unique_ptr for trace_filename
39600 	to crash gdb.  The problem is that the BFD section for a particular
39602 	Digging deeper, the problem was that elfread.c dropped the section for
39620 	eval_result_names array does not include a string for either
39625 	string for every possible error.
39642 	When comparing the test results for two different runs of GDB I
39643 	noticed a difference in the results for gdb.base/frame-view.exp.
39654 	If for whatever reason the stack address changes between test runs
39676 	      gdb/testsuite: add test for core file with a 0 pid
39679 	a pre-generated core file for x86-64 and for other architectures the
39802 	    * NEWS: Mention the new feature for objcopy.
39803 	    * doc/binutils.texi: Mention "large".
39900 	gdb: check max-value-size when reading strings for printf
39901 	I noticed that the printf code for strings, printf_c_string and
39905 	As such it would be possible for an badly behaved inferior to cause
39922 	The default for max-value-size is 64k so there should be no user
39941 	However, in this case we are building a string, and (at least for
39946 	string, we're just constructing a printf format specifier for a hex
39986 	memory... but I'm leaving that for a follow on patch.
40083 	as 128-bit loads and stores for efficient data movement.
40110 	Udated Freach and Romainian translations for various sub-directories
40120 	Linux: Avoid pread64/pwrite64 for high memory addresses (PR gdb/30525)
40206 	 /* Resume execution (or prepare for execution) of the current thread
40243 	ld: fix plugin tests for MIPS PIC
40244 	On MIPS, for PIC objects, symbols may reference 2 times:
40264 		non-native too, except for attempting to run the binaries.
40265 		Run tests for ELF in general, not just linux.
40286 	and in fact run_host_cmd_yesno is a better choice for it.
40338 	x86: flag bad EVEX masking for miscellaneous insns
40339 	Masking is not permitted for certain further insns, not falling in any
40349 	Masking is not permitted in this case. See the code comment for how this
40358 	Zeroing-masking is not permitted in this case. See the code comment for
40415 	we have a large number of symbols, but for now I'm not worrying about
40417 	that would increase the size of every dictionary for a use case that
40425 	Updated Ukranian, Romanian and German translations for various sub-directories
40432 	Wrong encoding for null destination NEG instruction. Fix it.
40440 	IBM Z: Fix pcrel relocs for symA-symB expressions
40442 	which reloc to apply currently does the wrong thing for absolute
40447 	the fx_pcrel flag in md_apply_fix. However, only for the last one we
40459 	Fix two Python calls that don't check for errors
40640 	The gdb.arch/core-file-pid0.exp test has been update to check for the
40647 	gdb/testsuite: add test for core file with a 0 pid
40648 	This patch contains a test for this commit:
40656 	This is another test that has been carried in the Fedora GDB tree for
40679 	then the lwpid for that thread is stored as 0 in the vmcore file.  If
40697 	threads for the core file.  The processing is done by calling
40698 	add_to_thread_list, a function which looks for sections named .reg/NN
40699 	where NN is the lwpid of the thread, GDB then builds a ptid_t for the
40702 	Remember, in our case the lwpid is 0.  Now for the first thread this
40756 	merged I can add some additional core files for other architectures,
40795 	The only thing about this change that gave me cause for concern is
40804 	found), then we look for a thread in the current inferior.  If there
40827 	Currently we have three instruction classes defined for Zvkh[a,b]:
40839 	Fixes: 62edb233ef5 ("RISC-V: Add support for the Zvknh[a,b] ISA extensions")
40844 	Add markers for the 2.41 branch
40851 		* NEWS: Mention LoongArch changes for 2.41.
40858 		* NEWS: Mention LoongArch changes for 2.41.
40864 	("LoongArch: gas: Add support for linker relaxation."), in order to
40883 		* loongarch-opc.c: Mark the offset operands as "so" for
40922 	RISC-V: Add support for the Zvksc ISA extension
40925 	Zvksc is shorthand for the following set of extensions:
40940 	RISC-V: Add support for the Zvknc ISA extension
40943 	Zvknc is shorthand for the following set of extensxions:
40958 	RISC-V: Add support for the Zvksg ISA extension
40961 	Zvksg is shorthand for the following set of extensions:
40976 	RISC-V: Add support for the Zvks ISA extension
40979 	Zvks is shorthand for the following set of extensions:
40996 	RISC-V: Add support for the Zvkng ISA extension
40999 	Zvkng is shorthand for the following set of extensions:
41014 	RISC-V: Allow nested implications for extensions
41024 		implications for extensions.
41028 	RISC-V: Add support for the Zvkn ISA extension
41031 	Zvkn is shorthand for the following set of extensions:
41048 	RISC-V: Add support for the Zvksh ISA extension
41058 		class support for Zvksh.
41074 		support for Zvksh.
41082 	RISC-V: Add support for the Zvksed ISA extension
41092 		class support for Zvksed.
41110 		support for Zvksed.
41118 	RISC-V: Add support for the Zvknh[a,b] ISA extensions
41128 		class support for Zvknh[a,b].
41147 		support for Zvknh[a,b].
41155 	RISC-V: Add support for the Zvkned ISA extension
41170 		class support for Zvkned.
41204 		support for Zvkned.
41212 	RISC-V: Add support for the Zvkg ISA extension
41222 		class support for Zvkg.
41238 		support for Zvkg.
41246 	RISC-V: Add support for the Zvbc extension
41256 		class support for Zvbc.
41276 		  support for Zvbc.
41284 	RISC-V: Add support for the Zvbb ISA extension
41302 		class support for Zvbb.
41350 		(enum riscv_insn_class): Add instruction class for Zvbb.
41373 	We picked up support for a few new extensions over the last weeks
41379 		* binutils/NEWS: announce suuport for the new RISC-V
41384 	RISC-V: Add support for the Zfa extension
41385 	This patch adds support for the RISC-V Zfa extension,
41416 		class support for 'Zfa' extension.
41426 		* doc/c-riscv.texi: Add floating-point chapter and describe
41507 		classes for the Zfa extension.
41511 		* riscv-dis.c (print_insn_args): Add support for
41527 	  * strings.c (main): Check for an excessively large minimum string length.
41563 	In addition, the "$x" name for $r21 was never included in any released
41565 	for every project I could think of that accepted a LoongArch port.
41569 	certainly create confusion for developers.
41571 	Issue warnings for such usages per the deprecation procedure detailed
41613 	opcodes/loongarch: do not print hex notation for signed immediates
41621 	style for immediates, like for example printing every immediate in
41693 	Add a flag in the pinfo field for being able to mark certain specialized
41763 	doc: sframe: update specification for SFRAME_VERSION_2
41764 	Add details for the changes made from Version 1 to Version 2 of the format.
41777 	for SFrame FDEs of type SFRAME_FDE_TYPE_PCMASK.
41779 	Introduce two extra bytes for padding: this ensures that the memory
41788 	The additional argument (for rep_block_size) is useful for SFrame FDEs
41812 		section for plt entries with version SFRAME_VERSION_2.
41833 		* ld-aarch64/sframe-simple-1.d: Adjust for SFRAME_VERSION_2.
41843 		* sframe-dump.c (dump_sframe_header): Add support for
41864 	for convenience only.  The linker may want to use these APIs as the
41879 	libsframe: fix sframe_find_fre for pltN entries
41880 	For a toy application on x86_64, for example, following is the SFrame
41881 	stack trace information for the 3 pltN entries of 16 bytes each:
41910 	This works for pltN entry of size, say, less than 16 bytes.  But if the
41911 	pltN entries or similar code stubs (for which SFrame FDE of type
41916 	a modulo operation.  The constant for the modulo operation must be the
41918 	encoded in the format, as it may be different for each ABI.
41931 		* sframe-spec.texi: Fix the text for SFRAME_FDE_TYPE_PCMASK FDE
41943 	ld: Add tests for -z nosectionheader and --strip-section-headers
41974 	ld: Add simple tests for -z nosectionheader
42043 		* objcopy.c (is_strip_section_1): Remove non-alloc sections for
42082 		* NEWS: Mention --strip-section-headers for objcopy and strip.
42089 		(copy_object): Handle --strip-section-headers for ELF files.
42092 		* doc/binutils.texi: Document --strip-section-headers for objcopy
42105 		* ld.texi: Document -z sectionheader and -z nosectionheader.
42117 	ignore lto-wrapper warnings for lto builds.
42144 	There is no need for the toolchain to restrict combinations of unrelated
42181 		parents for a name match.
42185 	Fix handling of DW_TAG_unspecified_type for Ada
42199 	Instead, this patch changes gdb to not enter a symbol for an
42200 	unspecified type -- but only for Ada.
42206 	There's no need for this any more, so this removes it.  There is still
42218 	Updated French translation for the gold sub-directory
42286 	libsframe: bfd: use uint32_t for return type of get_num_fidx APIs
42302 	libsframe: use appropriate data types for args of sframe_encode
42311 	libsframe: use uint8_t for return type of sframe_fre_get_base_reg_id
42319 		for base reg id.
42325 	libsframe: use uint8_t instead of unsigned char for abi_arch
42326 	Use uint8_t consistently for identifying ABI/arch in SFrame format.
42331 		* sframe-dump.c (is_sframe_abi_arch_aarch64): Use uint8_t for
42342 	libsframe: bfd: use uint32_t for return type of sframe_calc_fre_type
42343 	Use uint32_t type alias consistently for all APIs in libsframe.
42346 		* elfxx-x86.c (_bfd_x86_elf_create_sframe_plt): Adjust for the
42349 		* sframe.c (sframe_calc_fre_type): Use uint32_t for return type.
42355 	libsframe: use uint32_t for fre_type and fde_type function args
42357 	users are the bfd linker.  Adjust the argument type for the variables
42400 	with version node LIBSFRAME_1.0 for the first time.
42429 	release of libsframe, where all exposed symbols will be versioned for
42450 	to fall back on the libtool's -export-symbols option for platforms where
42451 	some other linker (with a different command line option for symbol
42455 		* Makefile.am: Use symbol versioning for libsframe.
42457 		* configure: Check for Solaris ld.
42470 	should technically not be directly necessary for a stack tracer.  A
42481 		Add comment for intention to deprecate.
42485 	        (sframe_get_funcdesc_with_addr_internal): New definition for
42494 	evolves, some changes will break the ABI.  Add library versioning for
42502 	In libtool-version, set the current to 1 to prepare for the upcoming
42518 	    The Zicond extension acts as a building block for branchless sequences
42527 	    for the proposed specification and usage details.
42576 	Fix gas tests for aarch64-pe
42582 	Updated French translation for the gprof sub-directory
42629 	This testcase sometimes gets stuck in a loop for hours when running in our
42661 	relocations for these addresses are not sorted properly with other
42667 	account for needed dynamic relocations, delaying adding the actual
42675 		relaxation to account for needed indirect branches, and add
42685 	accounted for in the value set in add_target_dynamic_tags, which is
42713 		dyn relocs for ADDR64 and similar using add_global_relative.
42728 	Simon pointed out that commit a2bbca9fa5e ("Use std::vector<bool> for
42765 	standard_output_file directory, for all test-cases.
42774 	the reponsibility for the cleanup at the callers in gdb/testsuite/Makefile.in
42780 	An exception is made for performance tests, where cleaning up the
42801 	there was any reason for this prohibition in the first place.
42827 	Implement type checking for DAP breakpoint requests
42857 	their names are valid. An identifier for a variable, can't ever have an
42859 	languages allow for that).
42893 	allocate a new symbol buffer and a new relocation buffer for each
42897 	are used to track relative relocations against local symbols for later
42917 	our yearly update.  I've updated the script to account for this, but I
42933 	This is on a CentOS 7 distro for powerpc64le.
42965 	The problem is that the regexp doesn't account for the ^C:
42984 	In commit 0961e631575b, the fix for PR30217, make_lplt_section and
42987 	is needed for long branches, due to needing to iterate sizing and thus
43005 	    # As proc command, but don't wait for an initial prompt.  This is used for
43016 	- in order for tuiterm to show something, its input processing procs need to
43043 	    # a regexp matching the line to wait for.  Return 0 on timeout, 1
43062 	For test for PR 29072 when the linker is configured with --enable-default-execstack=no.
43064 …* testsuite/ld-elf/elf.exp (target_defaults_to_execstack): Always return false for linkers configu…
43070 	'prepare_resume_reply' for a more readable log message.
43113 	aop_last is only used for an assertion.  However, due to the '.def'
43129 	Use bool for agent_expr::tracing
43145 	Use std::vector<bool> for agent_expr::reg_mask
43182 	to use std::string for everything, simplifying the code and removing a
43206 	Use unique_xmalloc_ptr for mi_parse::command
43216 	Use std::string for MI token
43279 	I ran into two issues for this, which I could not resolve in this patch;
43306 	Currently no event is emitted for a thread exit.
43340 	names for an applications that set the name of a thread in ways that
43347 	  * elf64-x86-64.c (elf_x86_64_relocate_section): Add more checks for a valid relocation offset.
43352 	Test-case gdb.ada/catch_ex_std.exp passes for me with package
43419 	riscv: Use run-time endianess for floating point literals
43443 	Replace this with cleaning up the entire directory instead, for all
43534 	but failed to do so for gdb.arch/thumb*.S.  Fix this oversight.
43574 	Correct ld-elf/eh5 test for hppa64
43575 	Commit 3c0afdb78988 regressed this test for hppa64, because the test
43576 	had been enabled for hppa64 in the time between the mips changes and
43578 	the testsuite change by hand for hppa64: Two lines in eh5.d might need
43579 	further changes for mips.
43619 	for said device including documentation.
43628 		* doc/as.texi (MIPS Attributes): Correct Tag_GNU_MIPS_ABI_MSA
43633 	Revert "MIPS: gas: alter 64 or 32 for mipsisa triples if march is implicit"
43653 	Revert "MIPS: add MT ASE support for micromips32"
43663 	Re: Add some expected failures for bfin linker tests
43708 	glibc-32bit-debuginfo), we have for -m64 (note: __GI__exit instead of _exit):
43724 	The gdb_test allows for both _exit and __GI__exit, but not _Exit:
43737 	Add some expected failures for bfin linker tests
43741 … function. (ldfile_print_input_remaps): New function. * ldfile.h: Add prototypes for new functions.
43746 	  * ld.texi: Document the new options.
43830 	There is a test-case that contains a unit test for tuiterm:
43897 	gdb/testsuite: use proper int size for gdb.dwarf2/symbol_needs_eval*.exp
43933 	`sizeof(int)` evaluates to for the current target.
43936 	DWARF information so we use the actual target's size for an int instead
43950 	Tom Tromey pointed out that the test and call to error() for the
44042 	I realized that I had only implemented DAP breakpoint conditions for
44069 	Co-workers who work on a program that uses DAP asked for the ability
44079 	"target remote".  I thought "attach" made the most sense for this,
44099 	This adds an 'assign' method to gdb.Value.  This allows for assignment
44127 	Use tuples for default arguments in DAP
44145 	Add test for DAP pause request
44146 	I neglected to write a test for the DAP "pause" request.  This patch
44158 	for this.
44176 	This implements the DAP setExceptionBreakpoints request for Ada.  This
44189 	Don't require inferior execution for Ada catchpoints
44191 	However, there's no deep reason for this -- for example, C++ exception
44246 	- the glibc object crti.o containing debug information for function
44257 	__libc_csu_fini and __libc_csu_init, but that doesn't work for call_weak_fn.
44280 	26                  for C of S loop^M
44308 	  Gas does not emit ADD/SUB relocation pairs for label differences
44318 	This commit implements a fix for a bug reported against GDB on
44339 	Enable debuginfod for this session? (y or [n]) y
44377 	Note that there's no DW_AT_location, so I looked for an abstract origin entry:
44385 	is the DIE for the local variable "value".)
44389 	    00027cf1 v000000000000000 v000000000000000 views at 00027ce1 for:
44425 	libsframe: testsuite: add sframe_find_fre tests for pltN entries
44427 	information for pltN entries is correct.
44433 	The test first looks up SFrame FREs for some addresses in the first pltN
44434 	entry, followed by lookups for some addresses in the fourth pltN entry.
44444 	libsframe: fix sframe_find_fre for pltN entries
44451 	work for a pltN entry of size say, 16 bytes).
44457 	For now, we should fix the code to at least behave correctly for the
44458 	generated code and the generated SFrame stack trace information for the
44462 		* sframe.c (sframe_find_fre): Correct the bitmask used for
44574 	   Downloading separate debug info for /usr/bin/ls
44594 	  /* Deleter for a debuginfod_client.  */
44629 	It's not obvious how this issue can easily be tested for. The bug does
44726 	language, so for Ada and Fortran the string will be an array of
44774 	This patch fixes the leaks for binutils and ld, leaving the gas leaks
44775 	for another day.  The mips elf backend already had this covered, and
44778 	for both ecoff and elf.
44794 		(_bfd_ecoff_bfd_copy_private_bfd_data): Set alloc_syments for
44825 	to locate and open files which were mapped in the process for which the
44827 	opened, GDB will re-try to open it once for each time it was mapped in
44831 	a given file once and does not re-try the process for each mapping.
44845 	warning is printed once for each time the file was mapped.  I find this
44902 	render node (/dev/dri/renderD$NUM) exposes the issue.  This happens for
44903 	example for processes using AMDGPU devices to offload compute tasks.
44968 	I noticed that the help texts for tui border-mode and tui active-border-mode
44977 	[gdb/cli] Handle pending ^C after rl_callback_read_char for readline 7
44979 	we handled a problem (described in detail in that commit) for readline >= 8
44988 	There is precedent for using private readline variables and functions, but
45006 	The gdb.dwarf2/dw2-prologue-end-2.exp test was failing for both AArch64 and
45010 	there are issues with both the prologue skipper for AArch64 and Arm and an
45032 	Here we send "tui enable" to gdb, but don't wait for it to arrive before
45033 	checking for a window box:
45036 	    Term::check_box "check for python window" 0 0 80 16
45039 	Fix this by waiting for the prompt to be issued in TUI before doing the check.
45076 	Commit cb81e84c72 resulted in an xpass for hppa64-hp-hpux11, but the
45077 	test still fails on hpp64-linux.  Let's make it pass for hppa64-linux
45095 	doc/bfdint.texi and comments in the aout and som code about this
45364 	for the two function value_cstring and value_string should represent.
45369 	than one 'char' would be needed for each character.  As such using
45376 	The value_cstring function is now responsible for adding a null
45381 	strings are null terminated.  Fortran and Ada strings, for example,
45404 	for Ada strings.
45409 	will be a null-terminated string (by calling value_cstring), and for
45412 	function is responsible for selecting a language appropriate character
45484 	bfd_errmsg uses asprintf for bfd_error_on_input, which means we
45493 		(bfd_errmsg): ..and here.  Use it for asprintf output.
45499 		csym against remaining space for symbols.  Error on out of bounds
45506 	oprand char with micromips. So for mips32, we use:
45508 	  ^  is added for 5bit sa oprand for some new DSPr2 instructions:
45511 	  +t is removed for coprocessor 0 destination register.
45513 	  +t is now used for RX oprand for MFTR/MTTR (MT ASE)
45514 	  ?  is added for sel oprand for MFTR/MTTR (MT ASE)
45516 		while for micromips, they are different.
45523 	MIPS: add MT ASE support for micromips32
45526 	MIPS® Architecture for Programmers
45527 	Volume IV-f: The MIPS® MT Module for
45538 	Revert "MIPS: add MT ASE support for micromips32"
45543 	MIPS: add MT ASE support for micromips32
45546 	MIPS® Architecture for Programmers
45547 	Volume IV-f: The MIPS® MT Module for
45560 		use -mabi=32 not for -gnuabi64
45570 	6. ld-gc/gc.exp: add -KPIC into asflags for pr13683, pr14265, pr19161
45572 		use noarch for mips16-local-stubs-1, since it use -mips4
45575 		add -KPIC into asflags for lto-3r, lto-5r, PR ld/19317 (2)
45588 	11. ld-selective/selective.exp: add -fno-PIC, which is needed for -mno-abicalls
45609 	Which use `-march=from-abi` for pre-R6 testcases,
45613 		-mips32r2 for micromips32
45614 		-mips1 for mips16-32
45615 		-march=from-abi for testcases to o32/n32/n64 both/all.
45617 	Replace `addi` with `addiu` for some cases for both r6 and pre-R6.
45619 	Introduce some new testcases for r6 with FPXX/FP64.
45625 	  2)some test think -march=mips64rN will alway true for mipsisa64rN,
45628 	This patch fix testsuite for all r6-default gnu triples:
45640 	We also set the default ABI for mips*-img-elf to O32.
45644 	and We believe that the multilib should be used for this case.
45648 	MIPS: gas: alter 64 or 32 for mipsisa triples if march is implicit
45650 	is pinned to a fix value if not given explicitly. for example
45804 	[gdb/guile] Fix doc string for value-optimized-out?
45824 	Show the tab witdh, in characters, for the TUI.
45947 	Another fix for fuzzed object files, exhibiting as a segfault in
45964 	Minor objcopy optimisation for copy_relocations_in_section
45966 		for STRIP_ALL if keep_specific_htab is empty.
45974 	libsframe: avoid using magic number
45975 	Define a new constant for the maximum number of stack offsets handled in
46015 	[PR ld/22263][PR ld/24676] RISC-V: Avoid spurious R_RISCV_NONE for TLS GD/IE.
46018 	for dynamic relocations since the conservative estimatation.
46021 	R_RISCV_NONE for pr22263-1 test, and the test in pr24676.
46044 	buffer overflows and other confusion when OPD handling for a second
46045 	.opd section references data for the first .opd section, by keeping
46060 		(ppc64_elf_before_check_relocs): Allow for opd sec_type
46063 		unset.  Error for unexpected toc relocs.
46065 		asserting.  Check and set sec_type too.  Adjust for changed
46067 		(ppc64_elf_relocate_section): Adjust for changed location of
46132 	I add two new targets (check-extra, check-install) for gprofng testing:
46133 	  `make check` runs sanity testing for gprofng and takes ~30 secunds.
46167 	I found the documentation for -dprintf-insert a bit unclear.  It
46209 	[gdb/testsuite] Fix gdb.tui/pr30056.exp for native-extended-gdbserver
46216 	  localhost:2346^[[7GWARNING: Timed out waiting for EOF in server after \
46224 	Add a KFAIL for the PR, and ensure that the isearch is aborted by using ^G,
46232 	pe/coff - add support for base64 encoded long section names
46234 …* coffcode.h (coff_write_object_contents): Handle base64 encoding on PE.  Also check for too large…
46235 …tion extracted from ... (make_a_section_from_file): ... here.  Add support for base64 long section…
46248 	[gdb/tui] Fix fingerprint for cmd-only layout
46266 	I traced this back to tui_set_layout, where for both the old and the new
46271 	The fingerprint is "VC" for both the old (cmd) and new (src) layouts, which
46275 	should be "C" for the cmd layout.
46289 	gdb: add support for %V to printf command
46290 	This commit adds a new format for the printf and dprintf commands:
46292 	string, just as GDB would for a 'print' command, e.g.:
46320 	The reason for this is that $_as_string returns a value object with
46368 	really overkill for what we want.
46413 	support for '%V' will depend on the inferior function being called.
46448 	specifier, for example:
46470 	off for another day I hope.
46478 	Same idea as previous patches, but for memory_changed.
46485 	Same idea as previous patches, but for command_param_changed.
46492 	Same idea as previous patches, but for breakpoint_modified.
46499 	Same idea as previous patches, but for breakpoint_deleted.
46506 	Same idea as previous patches, but for breakpoint_created.
46513 	Same idea as previous patches, but for tsv_modified.
46520 	Same idea as previous patches, but for tsv_deleted.
46527 	Same idea as previous patches, but for tsv_created.
46534 	Same idea as previous patches, but for traceframe_changed.
46541 	Same idea as previous patches, but for about_to_proceed.  We only need
46550 	Same idea as previous patches, but for solib_unloaded.
46557 	Same idea as previous patches, but for solib_loaded
46564 	Same idea as previous patches, but for target_resumed.
46571 	Same idea as previous patches, but for record_changed
46578 	Same idea as previous patches, but for inferior_removed.
46585 	Same idea as previous patches, but for inferior_disappeared.
46598 	Same idea as previous patches, but for inferior_appeared.
46605 	Same idea as previous patches, but for inferior_added.
46617 	Same idea as previous patches, but for thread_exited.
46624 	Same idea as previous patches, but for new_thread.
46631 	Same as previous patches, but for user_selected_context_changed.
46638 	Same idea as the previous patches, but for command_error.
46645 	Same as previous patches, but for sync_execution_done.  Except that
46654 	Same as previous patches, but for no_history.
46661 	Same as previous patch, but for exited.  Remove the exited observable,
46670 	Same as previous patch, but for signal_exited.  Remove the signal_exited
46679 	Same idea as the previous patch, but for the normal_stop event.
46686 	Instead of having the interpreter code registering observers for the
46696 	observer.  These observer go over all UIs, and, for those that have a
46701 	method gets called once for each interpreter, the implementations only
46704 	The motivation for this patch comes from a future patch, that makes the
46723 	[gdb] Mention --with/without-system-readline for --configuration
46735 	- using this in test-case gdb.tui/pr30056.exp to declare it unsupported for
46745 	Slight wording improvement for the -Ur documentation
46747 	Improve header information displayed with objdump -P for PE binaries.
46758 	LoongArch: ld: Add support for linker relaxation.
46780 	LoongArch: gas: Add support for linker relaxation.
46782 	Add R_LARCH_RELAX reloc for instrction if it can be relaxed.
46783 	ADD R_LARCH_ALIGN reloc for align pseudo instruction because relax.
46784 	Add ADD/SUB reloc pair for debug and exception data to calculate symbol
46797 		(append_fixp_and_insn): Call frag_wane and frag_new for linker relax
46802 		(md_apply_fix): Generate ADD/SUB reloc pair for debug and exception
46859 	LoongArch: binutils: Add support for linker relaxation.
46860 	Add support for relocs related to relax to readelf.
46877 		for LoongArch.
46881 	LoongArch: opcodes: Add support for linker relaxation.
46891 	LoongArch: bfd: Add support for linker relaxation.
46932 	LoongArch: include: Add support for linker relaxation.
46942 	Add support for an ARMMAGIC value of 0xa00 to the PE dumper.
46951 	up" their constants for ARM windows CE.
46953 	This patch supports objdump -P for arm-pe, and another magic constant
46984 	for od-pe.c
47058 	executing a command for the second intepreter, clears the
47061 	called for the first intepreter first.  Since the
47066 	running_result_record_printed.  When mi_on_resume_1 gets called for the
47082 	Only for the interpreter doing the -exec-run command does the
47086 	Add a new test for this, that does pretty much what the reproducer above
47165 	Fix this by checking for "RL_ISSTATE (RL_STATE_ISEARCH)" after the call to
47187 	Lots of targets already fixed the TEXTREL problem for TLS in PIE.
47191 	any local dynamic reloc for TLS LE in pie/pde, and similar to other targets.
47193 	Just break and don't goto static_reloc for TLS LE in pie/pde can fix the
47197 	The risc-v code for TLS GD/IE in the relocate_section seems same as MIPS port.
47199 	also the right way to do the same thing for risc-v.
47211 		bfd_link_dll for TLS IE.  Don't need to reserve the local dynamic
47212 		relocation for TLS LE in pie/pde, and report error in pic just like
47226 …figure.ac (od_vectors): Add objdump_private_desc_pe for PE format targets. (od_files): Add od-pe f…
47231 	  * doc/binutils.texi: Document the new support.
47249 	(despite my dislike for casts).
47261 	The 31 means red, but only for foreground colors, for background colors 41
47264 	Make this more readable by using color names for both foreground and
47312 	Using this option doesn't really work when no support for any 32-bit
47313 	target was configured in (as is the case for at least cloudabi and
47318 	particular when one's after only the results for the 64-bit set, having
47323 	have (and that could potentially be used for undue modification of
47332 	allow for up to MAX_CODE_LENGTH - 1 prefix bytes (which then could be
47342 	x86: use fixed-width type for codep and friends
47353 	Instead they're separators for pseudo-prefixes. Don't insert them in
47355 	that this eliminates the need for another separator after a pseudo-
47356 	prefix. While maybe not overly interesting for a following real
47374 	sframe/doc: minor improvements for readability
47376 		* sframe-spec.texi: Cosmetic fixes.
47395 	libsframe: use const char * consistently for immutable FRE buffers
47403 	libsframe: use uint8_t data type for FRE info related stubs
47405 		* sframe.c: Use uint8_t for FRE offset count and FRE offset
47406 		size.  Use uint8_t for FRE info word as well.
47412 	test for various reasons.
47425 	exhaustive list.  This just tidies test results for those for which I
47430 		one to check for -z text errors, the other to check tprel
47437 	I've had this patch for a while now and figured I'd update it and send
47438 	it.  It changes MI commands to use a "const char * const" for their
47486 	This is the same idea as the previous patch, but for filtered_iterator.
47493 	    11007 |   for (breakpoint &b : all_tracepoints ())
47519 	     3030 |   for (breakpoint &b : all_breakpoints_safe ())
47538 	I think it would make sense for iterator wrappers such as
47562 	gdb: use intrusive_list for breakpoint locations
47568 	 - Add methods for the various manipulations that need to be done on the
47579 	 - Add a breakpoint::last_loc method, for use in
47612 …/usr/include/c++/13.1.1/bits/stl_iterator_base_funcs.h:179:11: error: no match for ‘operator--’ (o…
47621 	do in any case, for completeness.
47733 		use of parameter save area for integer arg regs.  Comment.
47741 	gdbsupport: add support for references to checked_static_cast
47766 	      [gdb/testsuite] Fix gdb.server/multi-ui-errors.exp for remote target
47796 	However the default pattern for gdb_test includes a '$' end anchor.
47888 	express the default for this parameter.
47932 	This minorly rearranges parse.c to avoid the need for a forward
47959 	This introduces some helper methods for mi_parse that handle some of
47962 	Introduce "static constructor" for mi_parse
47970 	Use accessor for mi_parse::args
47973 	makes it simpler for a subsequent patch to implement different
47974 	behavior for argument parsing.
47983 	convenient for a later patch if these are emitted using field_signed.
48000 	Additionally it's possible for gdb to crash during this pagination prompt.
48006 	To fix this, pagination is disabled for the duration for clear_current_line.
48008 	indicate that it is a special purpose function intended for use with
48051 	Updated Swedish translation for the opcodes directory
48100 	The epilogue of set_point0 (11cf for clang, 401146 for gcc) is the main
48104 	is added by the "call f" instruction isn't accounted for.
48116 	looking for (just like we don't recognize double-quoted operator or
48137 		* doc/c-i386.texi: Document .fred, .lkgs.
48150 		* i386-dis.c: New entry for fred, lkgs.
48170 	        * doc/c-i386.texi: Document .fred, .lkgs.
48183 	        * i386-dis.c: New entry for fred, lkgs.
48264 	Re: readelf: Support SHT_RELR/DT_RELR for -r
48278 	have been resized.  Report the count for users too, in ld --stats.
48291 	The fix for pr23686 had a hole in the reloc address sanity check,
48308 	for loop change is shamelessly stolen from Oleg.
48311 		flagword*, and adjust to suit.  Replace while loop with for
48323 	for coff_set_section_contents.  This is all quite OK, but I was on a
48325 	deleting the one for coff_set_arch_mach ran into a warning about the
48344 	Update documentation for Python Frame.older and Frame.newer
48354 	ld: drop stray blank from ld.texi
48360 	gdb: fix post-hook execution for remote targets
48370 	does not work (at least) for "target remote" and "target extended-remote".
48391 	original command string for the sole purpose of using it after command
48415 	This commit removes this extra frame switch and adds test coverage for
48448 	GDB's symtab_and_line lookup, we try to find a result for an address,
48450 	skip_prologue_using_sal we then walk the line table looking for an
48458 	Obviously, I have no reproducer for this, as I said, I don't think
48466 	gdb/testsuite: test for a function with no line table
48467 	This commit adds a test for the following commit:
48475 	We have been carrying a test for that commit in the Fedora GDB tree
48501 	for one of the functions in the source file, and as a consequence GDB
48530 	  I believe is the GDB style for warnings,
48549 	      gdb/python: extend the Python Disassembler API to allow for styling
48561 	and the new tests didn't allow for this.
48572 	There are some known limitations for now,
48601 		expressions and insert fixups for them.
48602 		(riscv_md_finish): Called riscv_insert_uleb128_fixes for all sections.
48607 		* testsuite/ld-riscv-elf/uleb128*: New testcase for uleb128 subtraction.
48613 	RISC-V: Minor improvements for dis-assembler.
48619 	Therefore, add a new function, disassemble_free_riscv, to release them for safe.
48623 		for riscv to release private_data and internal data structures.
48648 	would be evaluated in 32 bits only when !BFD64) signals the need for
48658 	  warnings, as there should be for any code which won't build [warning-
48664 	gas: invoke md_optimize_expr() also for unary expressions
48667 	for the left operand (typically because of checking the operator first).
48705 	Eli pointed out that @sc only produces small caps for lower case
48780 	gdb/elfread.c: Add plt symbol check for _PROCEDURE_LINKAGE_TABLE_
48799 	IFUNC function addresss. First check to see if the real address for
48912 	libsframe: testsuite: add tests for sframe_get_funcdesc_with_addr API
48930 	libsframe: testsuite: add new tests for sframe_find_fre API
48935 	test that sframe_find_fre () works for the first, second, third and the
48937 	testing for the sframe_find_fre () function which is going to be the
48958 	NULL.  Well, yes, the hash table isn't initialised for the output bfd.
48979 		* config/obj-elf.c (obj_elf_section_word): Only compile for sparc.
48982 		* doc/as.texi (Section): Mention that solaris .section
48983 		directive is only supported for sparc.
48995 	parser doesn't look for types with names like this, but instead tries
49000 	This patch adds a special case for &str.
49015 	  * pe-dll.c (make_one): Check for decoated symbols.
49061 	Also FUNC_FLAG_SIMULATED is needed for these fake functions.
49071 	[gdb/tui] Don't show line number for lines not in source file
49072 	Currently, for a source file containing only 5 lines, we also show line
49104 	  * ld.texi (WIN32): Document how to create a resource only DLL.
49118 	Update comments for the gdb/24331 fix.
49130 	queries GDB for the list of supported languages, rather than just
49140 	  * ld.texi (-Ur): Clarify the actions of this option.
49171 	The reason for this warning is that this test deliberately calls
49182 	The impacted targets use AT_ENTRY_POINT as their strategy for handling
49198 	a68f7e984420 we are now stricter for GDB emitting additional,
49210 	gdb/python: extend the Python Disassembler API to allow for styling
49211 	This commit extends the Python Disassembler API to allow for styling
49227 	Neither of these approaches allowed for, or preserved, disassembler
49228 	styling, which is now available within libopcodes for many of the more
49256 	disassemble_info::fprintf_styled_func, or for disassemblers that don't
49283 	what happens if the user calls builtin_disassemble for an architecture
49390 		* testsuite/ld-elf/shared.exp: Clear xfail for LoongArch.
49407 	prints complete string, which is not what the user asked for.
49416 	Testing for NULL in pic_need_relax fixes the other call to this
49430 	cases INSERT handling looks for the specified output section later on
49436 		* ld.texi (INSERT): Specify ordering when -T is used both to
49447 	caused a rgression.  When debugging gnat1, gdb started asking for
49451 	Multiple matches for pp
49459 	This patch adds a test case for this situation and fixes the bug by
49475 	Import and Pragma Export.  This patch adds support for these to gdb,
49477 	underlying C symbol (for Import) or by introducing a second symbol
49478 	(for Export).  A somewhat tricky approach is needed, both because gdb
49497 	number doesn't get too large for the field size in the symbol.
49520 	-- checking for != PROP_UNDEFINED where == PROP_CONST is actually
49521 	required, the key thing being that const_val may only be called for
49558 	There's a test for the new functionality.
49562 	gdb/python: implement __repr__ methods for py-disasm.c types
49563 	Add a __repr__ method for the DisassembleInfo and DisassemblerResult
49564 	types, and add some tests for these new methods.
49592 	changes for '^' had not been replicated for gdb_test_multiple.  This
49615 	the logic for the special '^' handling in the case where the expected
49616 	output pattern is empty.  I replicated these updates for both gdb_test
49629 	gdb: fix error message for $_gdb_maint_setting
49636 	command, which isn't correct for $_gdb_maint_setting, in this case I
49639 	This same issue is present for $_gdb_maint_setting_str.
49647 	[gdb/testsuite] Fix gdb.dwarf2/opt-out-not-implptr.exp for -m32
49663 	the "generic type" has the size of an address on the target machine, which for
49676 	32-bit case and require is_target_64 just for the 64-bit case.
49693 	gcc: error: '-gdwarf64' is ambiguous; use '-gdwarf-64' for DWARF version or \
49694 	  '-gdwarf -g64' for debug level^M
49699 	fails for both cases.
49701 	The reason that is_target_64 is failing for target board dwarf64, is because
49704 	Fix this by making is_target_64 use nodebug instead of debug for compilation.
49710 	[gdb/cli] Fix wrapping for TERM=ansi
49806 	Note that now we report the same width for both TERM=xterm and TERM=ansi,
49810 	indicated by "maint info screen", for xterm:
49824 	I didn't manage to come up with a regression test for PR cli/30411.  Perhaps
49857 	now checking for O_register,
49858 	- for targets creating register symbols through symbol_{new,create}() ->
49864 	  have been used there from the beginning, if only that had worked for
49891 	First, check_pieced_synthetic_pointer did not account for the
49896 	for as well.)
49910 	    Downloading 10 MB separate debug info for /lib64/libxyz.so
49915 	    Downloading separate debug info for /lib64/libxyz.so
49926 	stops (i.e., stop and wait for the next GDB command). When GDB normal
49965 	This is one part of the fix for GCC PR109128, along with a
50066 	gdb/rust: fix crash for expression debug with strings
50110 	There's a new test to check for this case.
50125 …* elf32-or1k.c (or1k_elf_relocate_section): Prescan for R_OR1K_GOT_AHI16 relocs as they may occur …
50133 	  * lexsup.c (ld_options[]): Add entries for --print-map-locals and --no-print-map-locals.
50136 	  * ld.texi: Document the new command line option.
50186 	The default display uses more space for line numbers and starts the
50188 	much space as is needed for the line numbers in the current file, and
50202 	The abbreviation is due to allocating space for <lines in source>, which is
50203 	8 for this example, and takes a single digit.  The line numbers though
50204 	continue past the end of the file, so fix this by allocating space for
50222 	Then again, it could be part of the calculation for the number of digits
50223 	needed for printing.  With this minimal example:
50226 	  for (int i = 8; i <= 11; ++i) {
50241 	which shows that the number of digits needed for printing i is
50247 	With the fixes, we get for compact-source on:
50280 	use-after-free in the breakpoints iterations (see below for full ASan
50470 	gdb: Avoid warning for the jump command inside an inline function.
50515 	I also found it necessary to enable long section names for the bfd
50545 	this patch replaces it with a for-each and an explicit temporary
50549 	This replaces ALL_DICT_SYMBOLS with an iterator so that for-each can
50553 	This replaces ALL_OBJFILE_OSECTIONS with an iterator so that for-each
50559 	field to objfile::sections_start in preparation for that.
50568 	Python pretty-printers haven't applied to static members for quite
50585 	  Add support for .MIPS.abiflags and .gnu.attributes sections
50654 	protection against dependencies creeping in - though for full
50661 	One other change of note was for gdbpy_initialize_gdb_readline, this
50710 	was for:
50719 	newline sequence, this was for:
50757 	out that this script doesn't actually check for FILENAME.
50759 	This commit extends the test pattern to check for the full warning
50767 	indexer picks up an address for this symbol:
50816 	for TERM=xterm and TERM=ansi, both with auto-detected and hard-coded width.
50819 	add a KFAIL for that failure mode.
50827 	for CLI and TUI, both with auto-detected and hard-coded width.
50830 	KFAIL for that failure mode.
50836 	Debug info is lost for functions only called from functions marked with cmse_nonsecure_entr
50876 	The '--simple-values' argument ought to be suitable for IDEs that need
50879 	account, and this makes the argument unsuitable for this purpose.
50891 	        for (int i = 0; i < 10; ++i) total += s.v[i];
50912 	See https://github.com/microsoft/MIEngine/pull/673 for a case where this
50932 	   for the PRINT-VALUES argument, for example, '--scalar-values' (3),
50933 	   that would be suitable for use by IDEs.
50937 	   available for use when refreshing the call stack.
50949 	Stop the linker from loosing the entry point for COFF/PE code when compiling with LTO enabled.
51069 	commit 9b0ccb1ebae ("Pass const frame_info_ptr reference for
51095 	Pass const frame_info_ptr reference for skip_[language_]trampoline
51124 	that as workaround for this warning.
51135 	Improve the speed of computing checksums for COFF binaries.
51174 	could be implemented for other formats.  Move it to opncls.c because
51194 	libbfc.c: Use stdint types for unsigned char and unsigned long
51207 	uint32_t.  Also use bfd_byte* for buffers.
51301 	This patch is a fix for the same.
51329 	Fixed in this commit by adding the 'c++' flag for prepare_for_testing.
51341 	    Since launching is debugger/runtime specific, the arguments for
51344 	This patch adds some documentation for the parameter GDB currently
51392 	evaluate_expression is just a little wrapper for a method on
51422 	[gdb/tui] Fix TUI resizing for TERM=ansi
51433 	The discrepancy comes from tui_resize_all, where we ask readline for the
51489 	gdb.tui/resize-2.exp serves as a regression test for that change.  Without
51543 	[gdb/testsuite] Fix gdb.ada/excep_handle.exp for updated gdb_test
51641 	thread-specific breakpoints for non-existent threads.  Then if we try
51645 	valid thread_info pointer, which we can't have for a non-existent
51656 	The CLI doesn't allow a breakpoint to be created for a non-existent
51665 	breakpoints for non-existent threads.  This would preserve the current
51669 	breakpoints being created for non-existent threads.  This is good for
51670 	consistency, but is a breaking change for the MI.
51683 	I certainly didn't intend for this test to rely on this feature of the
51684 	MI, so I propose to update this test to only create breakpoints for
51688 	breakpoint for a non-existent thread, and I've also extended the test
51734 	current inferior from a set callback, move to the API that allows for
51749 	current inferior from a set callback, move to the API that allows for
51770 	responsible for copying the scratch area into the current inferior.
51802 	I don't know if there's actually any tests for completion of these
51845 	these are the recorded instructions (basically one for each instruction
51882 	In this list, we only have entries for the beginning of each line.  This
51883 	is because of the remote target's support for range stepping.  The
51891 	remote target to report stops for each instruction.
51960 	patch removes the cases I found in python.texi.  I also renamed some
51989 	ld: Use run_cc_link_tests for PR ld/26391 tests
51990 	Use run_cc_link_tests for PR ld/26391 tests to compile PR ld/26391 tests
51994 		* testsuite/ld-elf/elf.exp: Use run_cc_link_tests for PR ld/26391
52003 	RISC-V: Enable x0 base relaxation for relax_pc even if --no-relax-gp.
52004 	Let --no-relax-gp only disable the gp relaxation for lui and pcrel
52018 	RISC-V: Relax R_RISCV_[PCREL_]LO12_I/S to R_RISCV_GPREL_I/S for undefined weak.
52023 		(_bfd_riscv_relax_pc): Likewise, but for R_RISCV_PCREL_LO12_I/S.
52028 	The function doesn't use "ins" for other than retrieving "info". Remove
52050 	- a wrong M_0 suffix for TILEZERO is also corrected to be M_1 (now an
52076 		filestart a ufile_ptr.  Update for xcoff_artdata change.
52079 		(add_ranges): Update for xcoff_artdata change.
52087 		for anything but a small archive.
52114 	gas: bpf: fix tests for pseudo-c syntax
52115 	This patch fixes the GAS BPF testsuite so the tests for pseudo-c
52180 	lang_add_section won't actually insert anything for most of them.  That
52206 	This commit addresses PR gdb/7946.  While checking for bugs relating
52225 	In this commit I propose that we add special handling for the '^' when
52277 	event for example.  As there is no command sent to GDB (from the
52296 	Apologies for any regressions this commit causes, hopefully fixing the
52307 	First, for the newline pattern between the command output and the
52316 	then we should be checking for it, the current gdb_test doesn't do
52348 	As such, there's no value to it, it just adds more complexity for no
52465 	gdb, doc: add index entry for the $_inferior_thread_count convenience var
52466 	Add a marker in the documentation for indexing the $_inferior_thread_count
52473 	Add support for %x and %lx formats to the linker's vinfo() function.
52482 	    Ventana Micro has published the specification for their
52488 	    that can be used in constructing branchless sequences for
52499 	    requirements for X-extensions (which are likely to be captured in the
52504 	      - instructions are prefixed by a vendor-prefix (vt for Ventana)
52515 	            * doc/c-riscv.texi: Add section to list custom extensions and
52538 	gas: documentation for the BPF pseudo-c asm syntax
52548 		* doc/c-bpf.texi (BPF Pseudo-C Syntax): New section.
52563 	syntax.  Tests for all BPF instructions are included.
52566 	  for both syntaxes in the same source.
52592 	gas: support for the BPF pseudo-c assembly syntax
52593 	This patch adds support to the GNU assembler for an alternative
52595 	unconventional for an assembly language, but it is generated by
52671 	overload a method in a way that will work "naturally" for all integer
52684 	Updated debug architecture version checks for fbsd
52686 	code for Linux, but fbsd also needs updating.
52696 	Teach gdb about a new debug architecture version for AArch64 (0x11).
52710 	2) Return get32s and get16 value in a bfd_vma, reducing the need for
52717 	"mask" which was wrong for w_mode anyway.
52720 	don't know for sure that unsigned int is 32-bit.
52807 	Then both the GPR lookup there and the yet more ad hoc workaround for
52808 	PR/gas 29940 can be removed (including its extension needed for making
52811 	RISC-V: test for expected / no unexpected symbols
52812 	Both the temporary workaround for PR/gas 29940 and the existing special
52815 	there any test for uses of symbols with names matching GPRs, where such
52825 	subsequent parsing attempt for another operand combination might
52831 	The use of a wrong (for the insn) relocation operator (or a future one
52836 	arranging for a guaranteed subsequent error message by marking the
52840 	Both callers check for no relocations, so there's no point parsing for
52852 	riscv_ip() looks only for whitespace when finding the end of a mnemonic.
52855 	The sole caller of parse_relocation() has already checked for the %
52856 	prefix, so there's no need to check for it again in the strncasecmp()
52901 	which waits for:
53077 	[gdb/testsuite] Add warning for timeout in accept_gdb_output
53130 	Note that this doesn't happen for "{}".
53200 	[gdb/testsuite] Use -std=gnu99 for gdb.server/attach-flag.exp
53205 	attach-flag.c:22:3: error: 'for' loop initial declarations are only allowed \
53207 	   for (int i = 0; i < NTHREADS; i++)
53254 	[gdb/testsuite] Add basic lmap for tcl < 8.6
53264 	Fix this by adding basic lmap support for tcl version < 8.6.
53286 	New georgian translation for the bfd sub-directory
53326 	[gdb/testsuite] Skip dap tests for tcl 8.5
53357 	retrieved it for local use.
53392 	Let's use N64 abi by default for the triple with gnuabi64.
53472 	   synonym) early, instead of in the for loop.  I think it makes the two
53495 	   that part and update the condition to just check for
53504 	The `language` global variable is mostly a scratch variable used for the
53534 	- making sure the test-cases work for non-native and remote setups, if
53548 	An example of make-check-all.sh for one test-case is:
53574 	As for gdb, readline and the environment variables, the way things work
53588 	Add a command "maint info screen" that prints these notions, both for width
53604 	And for TERM=ansi:
53618 	is due to gdb making readline adjust twice for the lack of auto-wrap, this is
53627 	And for TERM=ansi, with width and heigth set to 0:
53640 	all reported values are updated, except for curses when not in TUI mode.
53646 	I'd like to use this command in the regression test for PR cli/30346.
53679 	Use entry values for 32-bit PPC struct return
53680 	AdaCore has a local patch for PPC "finish", but last year, Ulrich
53681 	Weigand pointed out that this patch was incorrect.  It may work for
53711 	implements it for PPC64.  Some care is taken so that GDB will continue
53716 	No check for 'nop' is done, as subsequent discussion revealed that the
53745 	x86: change fetch error handling for get<N>()
53750 	Leave value types as they were for the helper functions, even if I don't
53754 	need for a local variable of signed type). This also eliminates the need
53755 	for custom printing of '-' in Intel syntax displacement expressions.
53766 	Introduce a special error indicator node, for the sole (real) caller
53777 	... and its direct helper get_sib(). Using setjmp()/longjmp() for fetch
53782 	Also introduce a fetch_modrm() helper, for subsequent re-use.
53798 	adding "const" there, also add it for "sec".
53811 	Even if the output section candidates may be different for each relax passes,
53823 	Originally, this patch also do the same optimization for the call relaxations,
53841 		we can reset the max_alignment_for_gp for each repeated relax passes.
53859 	ar does not do this.)  Unfortunately this is an easy target for
53865 	used by elements as _bfd_read_ar_hdr is called for each element.  See
53870 	for the big and small archives, it's nicer to use a union.
53892 		checks.  Set up range for header.
53996 		* sframe.c (sframe_encoder_write_fre): Formatting fixes for
54017 	libsframe: use return type of bool for predicate functions
54073 	Like for parse_real_register() follow the model of strtol() et al: input
54089 	Updated Hungarian translation for the gprof directory
54112 	GCC introduced the _Float128 internal type as a work around for the issue.
54116 	workaround.  The workaround checks for "_Float128" name when reading the
54119 	double typedef.  The same is done for the complex long double typedef.
54142 	Assembler Internal Docs: Describe handling of opcodes for relaxation a bit better.
54221 	Our library does not set the default version for symbols.
54272 		* doc/gprofng.texi: Update documentation.
54273 		* doc/version.texi: Likewise.
54276 		* doc/gp-archive.texi: New file.
54277 		* doc/gp-collect-app.texi: New file.
54278 		* doc/gp-display-html.texi: New file.
54279 		* doc/gp-display-src.texi: New file.
54280 		* doc/gp-display-text.texi: New file.
54281 		* doc/gp-macros.texi: New file.
54282 		* doc/gprofng_ug.texi: New file.
54297 	Prior to this patch, it's not possible for GDB to debug GPU code in fork
54300 	after a fork or exec.  This patch adds support for that, such that it's
54301 	possible to for an inferior to fork and for GDB to debug the GPU code in
54327 	Same for exec.  A previous version of the code had the amd-dbgapi target
54371 	I think it would be a good idea to switch to the inferior for which the
54402 	sequence of events would happen, if it was not for the current patch.
54406 	   returns a stop event for an amd-dbgapi wave (thread).
54422 	   because the regcache is for a ptid managed by the amd-dbgapi target
54423 	   (e.g. (12345, 1, 1)), a ptid that does not make sense for the
54454 	boards.  When we detach a fork child, we may create a regcache for the
54467 	but I looked for other regcache methods doing target calls, and added
54559 	This adds support for 128-bit integers to the Ada parser.
54576 	This adds support for 128-bit integers to the Rust parser.
54583 	This changes long_const_operation to use gdb_mpz for its storage.
54588 	In preparation for adding more 128-bit support to gdb, a few additions
54596 	situation of zero-length types.  This can happen for a Rust '()' type;
54644 	Add support for the .gnu.sgstubs section to the linker for ARM/ELF based targets.
54662 	gdb/testsuite: accept script argument for mi_make_breakpoint_pending
54701 	pauth: Create new feature string for pauth to prevent crashing older gdb's
54718 	by all targets going forward, except native linux gdb and gdbserver, for
54721 	gdb/gdbserver will still emit the old feature string for Linux since it doesn't
54730 	debug registers: Add missing debug version entry for FEAT_Debugv8p8
54731 	The Arm Architecture Reference Manual defines debug version 0b1010 for
54744 	gdb/testsuite: Skip dump ihex for 64-bit address in gdb.base/dump.exp
54761 	On LoongArch, variable intarray address 0x120008068 out of range for IHEX,
54813 	Because 64-bit variable address out of range for IHEX, it's not an
54814 	functional problem for LoongArch. Refer to the handling of 64-bit
54816 	tests for the target has 64-bit addresses.
54822 	[gdb/testsuite] Add regression test for PR30325
54823 	Add regression tests for PR30325, one for the asm window and one for the
54845 	prepared for an exception, bad things result.
54855 	All the tests are designed for a little-endian ARC system. Thus,
54856 	update the arc predicate in arc.exp, improve the matching pattern for
54861 	ARC ISA.  The same holds for some short instructions.  Update the
54874 	rather than that for a later unsuccessful target match.
54946 	may be something else, for instance a '[' as reported in PR tui/30325.
54979 	commit 9e820dec13e ("Use a curses pad for source and disassembly windows"),
55033 	giving us this for the source window:
55041 	and this for the disassembly window:
55059 	which only happens for certain window widths.
55155 	Except it isn't out of bounds because space for a larger array has
55174 	results for targets checked by bfd_check_format_matches after that
55235 	gdb, doc: correct argument description for info connections/inferiors
55236 	It said for 'info inferiors' and 'info connections' that the argument
55257 	  * dwarf.c (display_debug_lines_decoded): Check for an overlarge number of files or directories.
55265 	  * readelf.c (uncompress_section_contents): Check for a suspiciously large uncompressed size.
55362 	Also the test is skipped for extended-remote boards as there's a
55363 	different set of options for limiting hardware watchpoints on remote
55373 	didn't have debug information installed for libgomp.so, which this
55378 	The reason for the failure to unwind was that the function prologue
55384 	This commit adds support for c.li.  After this GDB is able to unwind
55389 	for our c.li support.
55399 	build to fail.  Use GDB's version which provides a fallback for this case.
55401 	Tested for regressions on native aarch64-linux.
55415 	having it check for 'pc==0' -- but then I figured this could affect
55425 	x86: Add inval tests for AMX instructions
55486 	        already exists and we are making one for no input in particular.
55508 	So, audit and fix all those places.  Add tests for as many of those
55530 	generating CTF for it.  This only works if the host, on which
55532 	the target, for which the CTF is generated: when crossing, the trick
55559 	Add Ada test case for break using a label
55560 	I noticed there aren't any Ada test cases for setting a breakpoint
55564 	Use ui_out for "maint info frame-unwinders"
55567 	ui-out for tables.
55580 	Type "show copying" and "show warranty" for details.
55582 	Type "show configuration" for configuration details.
55589 	Type "apropos word" to search for commands related to "word".
55619 	Likewise for gdb.arch/i386-disp-step-self-call.exp.
55630 		* doc/c-i386.texi: Document .amx_complex.
55663 	gdb/testsuite: updates for gdb.arch/{amd64,i386}-disp-step-self-call.exp
55721 	references.  Fixed by emitting initialization for all static members.
55758 	I'm now using 'O!' as the format specifier for the second argument,
55820 	commit there's no huge benefit for the users in accepting named
55825 	with the PendingFrame.read_register method, this allows for the
55829 	Minor update to allow for named arguments, and an extra test to check
55840 	There's no huge benefit for making this change, both of these methods
55848 	argument name in GDB.  My preference for APIs is to use full words
55852 	There should be no user visible changes (for existing code) after this
55868 	as the argument format for the function's value argument.  This means
55884 	My preference for argument names is to use full words where that's not
55887 	I've made GDB look for here.
55927 	The problem here is that for amd64 and ARM setting up for a displaced
55938 	architecture specific code considers safe to borrow for the lifetime
55960 	signals provides one reason.  GDB sets up for the displaced step and,
55982 	This commit only aims to address the issue on amd64 for now, though I
55983 	believe that the approach I'm proposing here might be applicable for
55993 	for some "other" reason.  On ARM GDB can potentially read the
56012 	fixup functions for AArch64, rs600, s390, and ARM.  For all of these
56021 	also added support for testing the displaced step in the presence of
56024 	I've also added two new tests (for amd64 and i386) that check that GDB
56048 	Fix memory leaks and do a general tidy of the code for printing coff
56054 		(struct pr_stack): Delete "num_parents".  Replace tests for
56093 		for malloced strings.
56094 		(stab_push_string_dup): New function.  Use it throughout for
56097 		(stab_enum_type): Increase buffer sizing for worst case.
56117 	toolchains still have good support for it. Therefore, if a specific debug
56174 	of how to go about specifying 'configure' time options for
56232 	to be (re-)generated which are actually needed for the build.
56247 	time, but skipping ones which look to be of interest for debugging
56252 	Use bfd_alloc memory for read_debugging_info storage
56300 		for string passed to debug_start_source and push_bincl.  Copy
56307 		(parse_stab_cpp_abbrev): Use debug_xalloc for _vb$ type name.
56311 		(parse_stab_argtypes): Use debug_xalloc memory for physname
56336 	of the few ways for a client to actually acquire a memory reference.
56350 	thread-specific for the current inferior_thread().
56394 	  Error in testing condition for breakpoint 1:
56445 	  Error in testing condition for breakpoint 1:
56455 	  Error in testing condition for breakpoint 1:
56520 	The problem is, in our case, GDB first stops at the breakpoint for
56539 	computed for the inferior function call's stop, which is why we now
56567 	  Error in testing condition for breakpoint 1:
56600 	checks for different sizes of memory access.
56614 	next commit I will update the users of agent_mem_read to check for the
56623 	When GDB fails to test the condition of a conditional breakpoint, for
56637 	The line I'm interested in for this commit is this one:
56646 	I don't think it makes sense for GDB to report the stop as being at
56690 	So, in this commit, in preparation for the later commits, I propose to
56693 	  Error in testing condition for breakpoint NUMBER:
56702 	  Error in testing condition for breakpoint 1:
56714 	checked for the error in the expected output.
56724 	test passes for the remote boards, in the next few commits I will fix
56738 	failures in gdb.base/unwind-on-each-insn.exp for RISC-V.
56746 	was compiled for 64-bit RISC-V with compressed instruction support:
56748 	  Dump of assembler code for function bar:
56764 	the frame-pointer, as such GDB's (current) preference for using the
56774 	instructions at the current $pc looking for this pattern:
56790 	to work for every function.  If the compiler reorders the
56797 	Remember, this is for debugging code without debug information,
56813 	Add support to the RISC-V prologue scanner for c.ldsp and c.lwsp
56821 	support for the two additional compressed instructions.
56823 	When I added support for those two compressed instructions I noticed
56829 	The reason for the failures is that GDB is trying to build the
56846 	adding support for in this commit.
56860 	After this commit, we can now build the frame-id correctly for every
56877 	There should be no visible change for anyone not turning on debug.
56882 	While I was working on the disassembler styling for ARM I noticed that
56884 	the other ARM disassembly output, the disassembly for cpsie looks like
56910 	      [gdb/testsuite] Fix gdb.server/server-kill.exp for remote target
57017 	[aarch64] tpidr2: Fix erroneous detection logic for TPIDR2
57018 	The detection logic for TPIDR2 was implemented incorrectly.  Originally
57020 	for backwards compatibility, the detection should be based on the size of
57025 	return a iovec size of 8, even if we asked for 16 bytes.
57107 	gdb/arm: Fix backtrace for pthread_cond_timedwait
57120 	for the "futex" syscall used by pthread_cond_timedwait.
57128 	Dump of assembler code for function pthread_cond_timedwait@@GLIBC_2.4:
57143 	lto: Don't add indirect symbols for versioned aliases in IR
57144 	Linker adds indirect symbols for versioned symbol aliases, which are
57151 	for versioned symbol aliases in IR.
57157 		symbols for ".symver foo, foo@FOO" aliases in IR.
57194 	Type commands for definition of "remove".^M
57203 	Type commands for definition of "remove".^M
57221 	Proc gdb_test_multiple has special handling for multi-line commands, which
57222 	splits it up into subcommands, and for each subcommand issues it and then
57223 	waits for the resulting prompt (the secondary prompt ">" for all but the last
57271 	most useful for Fortran programs which have a variable main method.
57282 	code of DW_AT_calling_convention attribute for determining the name of
57296 	GDB: Favor full symbol main name for backtrace stop
57333 	In this commit, prefetch offset operand "f" for 'Zicbop' extension is moved
57335 	"f" for this operand type seemed too much).
57345 	types (for operands including instructions from unratified extensions).
57351 	                          solely for widening conversion instructions.
57366 	This can't be done for all insns currently encoded with .byte. For one
57390 	Where necessary --divide is added as gas option, to allow for the use
57402 	x86: handle immediate operands for .insn
57409 	inconsistent results at least for effectively negative values, depending
57420 	x86: allow for multiple immediates in output_disp()
57424 	x86: handle EVEX Disp8 for .insn
57432 	x86: process instruction operands for .insn
57443 	x86: parse special opcode modifiers for .insn
57453 	x86: parse VEX and alike specifiers for .insn
57455 	the bits presently reserved could be used for other purposes down the
57482 	contains cases for RETURN_QUIT and RETURN_ERROR, but is missing a case
57483 	for the recently added RETURN_FORCED_QUIT.  This commit adds that case.
57487 	though the addition of a case for RETURN_FORCED_QUIT isn't the actual
57509 	      for (inferior *inf : all_inferiors ())
57537 	Sorry for not catching this during testing.  I was using a
57667 	Add support for the SME2 ADD. SUB, FADD and FSUB instructions.
57690 	SME2 adds lookup table instructions for quantisation.  They use
57717 	SME2 adds LD1 and ST1 variants for lists of 2 and 4 registers.
57727 	and extractors for each lower bound.  This in turn required adding
57733 	SME2 defines new MOVA instructions for moving multiple registers
57743 	strided lists, for which the requirements aren't a simple multiple.
57747 	aarch64: Add support for predicate-as-counter registers
57748 	SME2 adds a new format for the existing SVE predicate registers:
57753 	This patch adds support for these registers and extends some
57760 	aarch64; Add support for vector offset ranges
57772 	aarch64: Add support for vgx2 and vgx4
57776 	for disassembly.
57807 	This patch adds bare-bones support for +sme2.  Later patches
57814 	as { v0.4s - v3.4s } as an unofficial shorthand for
57820 	The range form was already binutils's preferred disassembly for 3- and
57821 	4-register lists.  This patch prefers it for 2-register lists too.
57822 	The patch also adds support for wrap-around.
57826 	aarch64: Add support for strided register lists
57831 	The parsing code already had (unused) support for strides of 2.
57869 	a placeholder for the register number.  However, we don't use that
57870 	convention for integer and FP registers, and (more importantly)
57874 	registers.  The main hitch is that Z was also used for the
57885 	opcode entry for both forms since (a) that matches the ISA definition
57902 	the SVE and SME uses of qualifiers: a macro defined for one can
57903 	be useful for the other too.
57932 	pick the closest match within an opcode entry for the
57942 	The error for invalid register lists had the form:
57952 	This patch goes for slightly shorter messages, setting a template
57953 	that later patches can use for more complex cases.
57975 	aarch64: Add an operand class for SVE register lists
57983 	even though we already have a dedicated error code for register
57988 	aarch64: Commonise checks for index operands
57989 	This patch splits out the constraint checking for index operands,
57992 	aarch64: Add an error code for out-of-range registers
57997 	adds a dedicated error type for out-of-range errors.
58028 	Trying to parse an invalid assembly line will trigger an error for
58032 	GAS has quite an elaborate system for picking the most appropriate
58042 	matches for an attempted SVE2 instruction is:
58056 	the register types that an opcode table entry expected for a
58062 	The patch includes tests for all new messages except REG_TYPE_ZA,
58067 	class.  I then looked for cases where the new routines fell back on the
58069 	I locally added dummy messages for each one until there were no
58071 	for each of these combinations.  In each case, the combination didn't
58083 	report errors in subsequent registers in the same way as for the
58087 	The problem is that if there are multiple opcode entries for the
58089 	default error.  There's no guarantee that the default error for
58108 	aarch64: Improve errors for malformed register lists
58109 	parse_typed_reg is used for parsing both bare registers and
58155 	aarch64: Tweak errors for base & offset registers
58161 	A later patch moves away from using get_reg_expected_msg for failed
58167 	aarch64: Tweak error for missing immediate offset
58176 	However, SME2 adds instructions for which the range is
58184 	like p0-p7.  A quick internal poll showed a preference for
58206 	but we need to remove that restriction for SME2.
58222 	The patch also adds a new check_za_access function for checking
58223 	ZA accesses.  That's a bit over the top for one offset check, but the
58226 	sme-9-illegal.s checked for an invalid .q suffix using:
58241 	parts around individually is more awkward than for other operand
58245 	This patch therefore replaces arguments for the individual pieces
58246 	with a single argument for the index as a whole.
58251 	A later patch moves the range checking for ZA vector select
58261 	za_tile_vector is also used for indexing ZA as a whole, rather than
58262 	just for indexing tiles.  The former is more common than the latter
58272 	does the same for ZA itself.  parse_sme_zero_mask can then parse
58276 	is that it allows ZA to take qualifiers.  This is necessary for many
58285 	While there, the patch also tweaks the error messages for invalid
58296 	we can check there for out-of-range tile numbers.  The other check
58301 	aarch64: Reuse parse_typed_reg for ZA tiles
58302 	This patch reuses the general parse_typed_reg for ZA tiles.
58337 	a register type too, and REG_TYPE_ZA is the obvious name for that.
58345 	but it's better for later patches if it reuses the binutils-wide
58365 	immediates, due to the obvious potential for confusion with
58369 	that GAS rejects for existing instructions.  For example:
58383 	although it didn't matter in practice for base SVE instructions
58390 	24-31 have been reused for the encoding of the new RPRFM instruction.
58391 	The PRFM opcode space is now capped at 23 for these forms.  The other
58395 	The opcode mask for PSEL was missing some bits, which meant
58402 	for compatibility.
58446 	objects, but the only reason for that requirement is that we have some
58519 	Additionally, users can now use integers for the 'sp' and 'pc'
58561 	As such there's no tp_init method defined for UnwindInfo.
58568 	to be invalid for use in GDB.
58580 	gdb/python: add __repr__ for PendingFrame and UnwindInfo
58582 	little bit easier.  This commit adds __repr__ for gdb.PendingFrame and
58602 	the interface for the two classes the same.  For this reason
58610 	  - gdb.PendingFrame.name: Return the name for the frame's function,
58613 	  - gdb.PendingFrame.pc: Return the $pc register value for this
58617 	    language for this frame, or None.
58620 	    for the current location within the pending frame, or None.
58622 	  - gdb.PendingFrame.block: Return a gdb.Block for the current
58625 	  - gdb.PendingFrame.function: Return a gdb.Symbol for the current
58633 	There are tests for all the new methods.
58650 	              assert str(rte) == "Cannot locate block for frame."
58690 	I started writing some tests for this change and immediately ran into
58738 	  output (how to display a non-string name for an unwinder?),
58752 	There's tests for all the changes, and lots of documentation updates
58754 	the general documentation for GDB's Unwinder API.
58773 		* libcollector/synctrace.c: Fix typo for pthread_mutex_lock.
58777 	Setting sh_link for SHT_REL/SHT_RELA
58782 		comment.  Always set sh_link to .dynsym for alloc reloc
58783 		sections and to .symtab for non-alloc.
58834 	Maybe we should add this check for all pc-relative relocations, rather
58857 	* Don't need dynamic relocation for R_RISCV_32/64 under RV32/RV64 when
58880 	    and need to make ifunc-seperate* testcases work for rv32.
58887 	These types of codes are different for each target, I am not sure what are the
58888 	best for RISC-V, so extract them out may be more easy to compare what's the
58893 	    from riscv_elf_check_relocs, to see if dynamic reloc is needed for the
58930 	This adds a frame parameter to resolve_dynamic_type and arranges for
58951 	This adds a 'rust_at_least' helper proc, for checking the version of
58957 	[gdb/testsuite] Require gnatmake 11 for gdb.ada/verylong.exp
58968 	AFAICT, support for Long_Long_Long_Integer was added in gcc 11.
59017 	gdb: more debug output for displaced stepping
59078 	I'm not proposing to do anything about this issue for now.
59084 	[gdb/testsuite] Fix gdb.guile/scm-symbol.exp for remote host
59085 	Fix test-case gdb.guile/scm-symbol.exp for remote host by making a regexp less
59094 	[gdb/testsuite] Fix /gdb.guile/scm-parameter.exp for remote host
59095 	Fix test-case gdb.guile/scm-parameter.exp for remote host by taking into
59096 	account that gdb_reinitialize_dir has no effect for remote host.
59102 	[gdb/testsuite] Fix gdb.guile/scm-objfile-script.exp for remote host
59109 	[gdb/testsuite] Fix gdb.guile/scm-objfile-script.exp for remote host
59123 	[gdb/testsuite] Fix gdb.guile/guile.exp for remote host
59124 	Fix test-case gdb.guile/guile.exp for remote host using gdb_remote_download.
59131 	This function doesn't just initialise for compression, it actually
59133 	buffers for the uncompressed contents.
59158 	is no need for the ld_compile command line to include
59186 	This changes partial symbol tables to use unrelocated_addr for the
59200 	[gdb/testsuite] Fix gdb.btrace/multi-inferior.exp for remote host
59201 	Fix test-case gdb.btrace/multi-inferior.exp for remote host using
59208 	[gdb/testsuite] Fix gdb.btrace/gcore.exp for remote host
59209 	Fix test-case gdb.btrace/gcore.exp for remote host using
59216 	[gdb/testsuite] Fix gdb.btrace/reconnect.exp for remote target
59217 	Fix test-case gdb.btrace/reconnect.exp for target board
59260 	[gdb/testsuite] Fix gdb.server/server-kill-python.exp for remote host
59261 	Fix test-case gdb.server/server-kill-python.exp for remote host using
59268 	[gdb/testsuite] Fix gdb.server/sysroot.exp for remote host
59269 	Fix test-case gdb.server/sysroot.exp for remote host, by:
59271 	- disabling the "local" scenario for remote host/target, unless
59278 	[gdb/testsuite] Require non-remote host for gdb.server/multi-ui-errors.exp
59279 	Require non-remote host for test-case gdb.server/multi-ui-errors.exp, because
59287 	[gdb/testsuite] Fix gdb.server/solib-list.exp for remote host
59288 	Fix test-case gdb.server/solib-list.exp for remote host using
59297 	[gdb/testsuite] Fix gdb.server/file-transfer.exp for remote host
59298 	Fix test-case gdb.server/file-transfer.exp for remote host using
59305 	[gdb/testsuite] Fix local-remote-host-native.exp for gdb.server tests
59342 	Now gdb.server/*.exp passes for host+target board local-remote-host-native,
59343 	except for file-transfer.exp.
59405 	to address 0x62600000016c with insufficient space for an object of
59418 	the wrong answer for gdb.rust/expr.exp, which doesn't require it.
59447 	[gdb/testsuite] Unsupport gdb.rust for remote host
59458 	The problem is that find_rustc returns "" for remote host, so we fall back to gcc, which fails.
59460 	Fix this by returning 0 in allow_rust_tests for remote host.
59467 	which is not a valid value for type '_Bool'
59477 	[gdb/testsuite] Fix gnat_runtime_has_debug_info for remote host
59478 	Fix gnat_runtime_has_debug_info for remote host by checking for
59481 	This fixes an error for test-case gdb.testsuite/gdb-caching-proc.exp and
59488 	fbsd-nat: Use correct constant for target_waitstatus::sig.
59498 	This is in #ifdef'd code for a workaround for FreeBSD versions older
59581 	signals when the thread didn't actually stop for a signal.  So we can
59590 	[gdb/testsuite] Fix gdb.stabs/exclfwd.exp for remote host
59591 	Fix test-case gdb.stabs/exclfwd.exp for remote host using include_file.
59597 	[gdb/testsuite] Fix gdb.stabs/weird.exp for remote host
59598 	Fix test-case gdb.stabs/weird.exp for remote host by not using an absolute
59603 	[gdb/testsuite] Fix gdb.gdb/unittest.exp for remote host
59604 	Fix test-case gdb.gdb/unittest.exp for remote host, by:
59606 	- not using with_gdb_cwd $dir for remote host (because it does
59621 	do_self_tests for remote target).
59628 	It could be made to work for the "[is_remote host] && [is_remote target]
59661 	Use gdb_gmp for scalar arithmetic
59662 	This changes gdb to use scalar arithmetic for expression evaluation.
59676 	arguments, and this approach can then fail for integers wider than
59677 	LONGEST.  Instead, rewrite this in a form that works for any size
59696 	useful for manipulation values via gdb_mpz.
59709 	This is preparation for using this class for scalar arithmetic in gdb
59717 	store.  This reduces memory use a little for "gdb gdb":
59719 	(before) Space used: 28909568 (+0 for this command)
59720 	(after)  Space used: 28884992 (+0 for this command)
59728 	[gdb/testsuite] Fix gdb.asm/asm-source.exp for remote host
59729 	Fix test-case gdb.asm/asm-source.exp for remote host using
59736 	[gdb/testsuite] Fix gdb.dwarf2/imported-unit-bp-c.exp for remote host
59744 	[gdb/testsuite] Unsupport gdb.dwarf2/gdb-add-index-symlink.exp for remote host
59745 	Declare test-case gdb.dwarf2/gdb-add-index-symlink.exp unsupported for remote
59752 	[gdb/testsuite] Fix gdb.dwarf2/gdb-index-cxx.exp for remote host
59753 	Fix test-case gdb.dwarf2/gdb-index-cxx.exp for remote host using
59760 	[gdb/testsuite] Fix gdb.dwarf2/enqueued-cu-base-addr.exp for remote host
59761 	Fix test-case gdb.dwarf2/enqueued-cu-base-addr.exp for remote host by using
59778 	[gdb/testsuite] Fix gdb.dwarf2/per-bfd-sharing.exp for remote host
59779 	Fix test-case gdb.dwarf2/per-bfd-sharing.exp for remote host using
59798 	Try 'rm --help' for more information.^M
59808 	[gdb/testsuite] Fix quoting issues in gdb.dwarf2 for remote host
59815 	Fix this by introducing a new proc quote_for_host that also works for remote
59825 	[gdb/testsuite] Fix have_index for remote host
59827 	for remote host.
59845 	My distro has no support for gdc, but I'd like to have the test-case
59866 	doesn't function as regression test for commit 47fe57c9281 ("Fix "start" for
59897 	that in gdb/coffread.c for "negative" values won't work if long is
59901 	data.)  long is also a poor choice for x_sect.s_scnlen, which might
59963 	When given two or more DW_AT_call_file for a given function we
60034 	I see for each test-case:
60076 	Implement repl evaluation for DAP
60092 	was a silent regression on openSUSE Leap 15.4 for test-case
60120 	that this bit in dwarf_decode_lines is executed again for m-static1.cc:
60122 	  /* Make sure a symtab is created for every file, even files
60149 	string, so I just spent ten minutes auditing for obvious memory leaks
60167 		value for returning if never reset during the function.
60176 	ready for this, misinterprets it as a type appearing more that once (a
60179 	Fixed, audited for further instances of the same failure (none found)
60204 	aarch64: Check for valid inferior thread/regcache before reading pauth registers
60292 	that has native support for the pointer authentication feature. But
60299 	support for pointer authentication are not that common yet.
60307 	target_has_registers was one function that seemed useful for detecting these
60348 	If the target has support for pointer authentication, gdb needs to use
60349 	a couple (or 4, for bare-metal) mask registers to mask off some bits of
60350 	pointers, and for that it needs to access the registers.
60371 	for bare-metal debugging when switching between exception levels.
60406 	That's fine for say:
60410 	for which this evaluates to:
60415 	But there are more complex uses, for instance:
60438 	In commit 722c4596034 ("[gdb/testsuite] Fix gdb.cp/*.exp for remote host"), I
60470 	which manifests on openSUSE Leap 15.4 for native and readnow, and on Ubuntu
60471 	20.04 for readnow, but not for native.
60478 	pass whether the bug manifests or not.  We could add an xfail for the PR, but
60516 	Fix minor grammar issue in python.texi
60522 	Add support to readelf for the PT_OPENBSD_MUTABLE segment type.
60542 	- downloading to a location which is safe for parallel testing, by
60581 	This commit is initial support for SystemTap for RISC-V Linux.  The
60591 	file, while for amd64, i386, and s390 the implementation lives in
60596 	Anyway, for this patch I selected riscv-tdep.c (though clearly, moving
60625 	predicate, and I have updated the validation check for the
60632 	the fixup method, so this change should cause no problems for anyone.
60663 	[gdb/testsuite] Fix gdb.cp/cp-relocate.exp for remote host
60664 	Fix test-case gdb.cp/cp-relocate.exp for remote host using
60671 	[gdb/testsuite] Fix gdb.cp/annota{2,3}.exp for native-extended-gdbserver
60682 	[gdb/testsuite] Fix gdb.cp/*.exp for remote host
60683 	Fix a few test-cases in gdb.cp/*.exp for remote host using new proc
60747 		string offset when setting up name for use by error messages.
60767 	PE fake section for C_SECTION syms
60774 		fake section created for C_SECTION syms.  Don't zero asection
60816 	PowerPC: regression fix for reverse-finish command.
60823 	   PowerPC: fix for gdb.reverse/finish-precsave.exp and gdb.reverse/finish-reverse.exp
60887 	[gdb/testsuite] Use localhost instead of 127.0.0.1 for boards
60896 	[gdb/testsuite] Fix gdb.xml/tdesc-regs.exp for remote host
60897 	Fix test-case gdb.xml/tdesc-regs.exp for remote host by using appropriate
60904 	[gdb/testsuite] Fix gdb.xml/tdesc-reload.exp for remote host
60905 	Fix test-case gdb.xml/tdesc-reload.exp for remote host by using appropriate
60917 	Reintroduce handling of HOST_DIR using remotedir, now that using remotedir for
60972 	Update python-helper.exp for type allocation changes
61028 	language detection for msymbols, in some cases GDB can't tell if a
61031 	The test application contains symbols for functions which are
61033 	DWARF for these symbols, so all GDB has is the msymbols built from the
61045 	for that symbol.
61051 	And so, because we check the C++ language before we check for rust,
61055 	demangled symbol is not actually a valid C++ symbol, for example, in
61057 	C++ symbol, we could look for ':<' and '>:' and refuse to accept this
61103 	and returns.  In our case, when we're looking for 'pars', the match
61108 	strncmp_iw_with_mode, and inside strncmp_iw_with_mode we allow for
61147 	The reason we don't often see this problem in C++ is that for C++
61179 	The problem here is that the C++ symbol for the constructor looks like
61254 	quite achieve that: '$' for example is unconditionally marked as part of
61255 	symbol names, but was included as identifier char for Intel syntax only.
61256 	Note that i386_att_operand() checks for the immediate prefix first, so
61258 	there, but it does matter for something like
61264 	symbol name). Similarly including '%' as an identfier for Intel syntax
61279 	will fail anyway for a zero-length name.
61288 	While in principle merely rejecting this for .insn would be sufficient
61289 	for the purposes there, be more generic and reject it for anything that
61293 	improves diagnostics for misuses like
61303 	don't need special casing anymore for SSE2AVX handling. Simplify the two
61312 	for a particular value, which we don't really need to retain.
61320 	The function has accumulated a number of special cases for no real
61343 	Reloc howto access broken for BPF
61379 	for recreating the current breakpoints.  The CLI does not use global
61384 	most consistent solution would be for the saved breakpoints file to
61401 	inferior-qualified thread-id, even for this single inferior case.
61457 	Enable vector register visibility in core file for AIX binutils
61490 	Another sanity check for read_section_stabs_debugging_info
61497 		* ctf-open.c (ctf_bufopen_internal): Check for NULL cts_data.
61524 	preparation for their unification.
61534 	because it is ok for an objfile-allocated type to refer to an
61541 	Use type allocator for set types
61551 	Use type allocator for array types
61562 	Use type allocator for range types
61677 	[gdb/testsuite] Handle unbuffer_output.c for remote host
61684 	[gdb/testsuite] Handle my-syscalls.h for remote host
61691 	[gdb/testsuite] Handle attributes.h for remote host
61753 	library gets loaded, GDB computes new breakpoint locations for each
61760 	Since commit cb1e4e32c2d9, the inserted flag isn't transferred for
61780 	Because locations for tracepoints have the bp_loc_other type,
61781 	bl_address_is_meaningful started to return false for them, where it
61796 	address.  bp_loc_other is a catch-all for "the rest", in practice for
61798 	bl_address_is_meaningful returns false for them).  For instance,
61805 	breakpoints for them (even though they might be implemented using
61809 	return true for them.  And they'll be ignored by insert_bp_location and
61810 	GDB won't try to insert a memory breakpoint for them.
61827 	PowerPC: fix for gdb.reverse/finish-precsave.exp and gdb.reverse/finish-reverse.exp
61925 	[gdb/testsuite] Fix gdb.arch/i386-biarch-core.exp for remote host
61933 	Handle REMOTE_HOST_USERNAME in local-remote-host, similar to how that's done for
61938 	Since the setup makes $build/gdb/testsuite on build unreadable for the remote
61939 	host, we run into permission problems for GDB and the data-directory, so fix
61940 	this (as was done for gdbserver in gdbserver-base.exp) using file normalize.
61957 	This doesn't work for host/target board local-remote-host-native, so xfail this.
61963 	[gdb/testsuite] Fix have_avx for remote target
61978 	[gdb/testsuite] Handle precise-aligned-alloc.c for remote host
62030 	escape_for_host that care of this for us, allowing us to write:
62049 	[gdb/testsuite] Declare ada unsupported for remote host
62094 	With the removal of gasp (about 20 years ago) the need for this kind-
62121 	gdb/doc: extended documentation for inferior function calls
62122 	I noticed that the documentation for inferior function calls doesn't
62139 	gdb/testsuite: Add support for LoongArch in gdb.base/float.exp
62179 	occurrences but I couldn't see any, so I hope this fix is OK for the
62189 	The documentation for the Python Unwinders API could do with some
62195 	registration line in the skeleton code.  But this is confusion for
62196 	users (I think) as the skeleton code is almost complete, except for
62197 	one missing line which the user has to figure out for themselves.  By
62220 	ld/testsuite: disable ilp32 tests for aarch64-qnx
62229 	        * testsuite/ld-aarch64/emit-relocs-112-overflow.d: Skip for
62275 	        * testsuite/ld-aarch64/aarch64-elf.exp: Add support for
62280 	ld: add support of QNX stack arguments for aarch64nto
62300 	readelf: add support for QNT_STACK note subsections
62316 		(process_note): Add support for QNX support.
62364 	HAS_CONTENTS by default.  This is wrong for .comment.  Fix that by
62367 	set to zero, as is usual for non-alloc sections.
62369 	Also, use source_sh for all of the sourced scripts to set up make
62437 		handling for forced-local global symbols.
62439 		parameter "is_local".  Emit relative relocs for globals that
62463 	Enable vector register visibility in core for AIX.
62479 	[gdb/testsuite] Fix gdb.arch/amd64-stap-special-operands.exp for remote host
62503 	[gdb/testsuite] Fix gdb.arch/i386-pkru.exp for native-gdbserver
62510 	This looks similar to the the problem for which there's already an xfail, so
62526 	Enable debuginfod for this session? (y or [n]) ^CQuit^M
62530 	The problem is that the unsetenv for DEBUGINFOD_URLS in default_gdb_init:
62533 	    # debug info for f.i. system libraries.  Prevent this.
62538 	Fix this by using "set debuginfod enabled off" for remote host.
62550 	the .S file is already copied from build to host, such that it's available for
62553 	But that's not the case for the .c file, which is needed by gdb to show a
62573 …* NEWS: Mention the new feature. * ld.texi: Document the new feature. * ldgram.y: Handle LINKER_VE…
62577 	  * mep.opc (mep_print_insn): Check for an out of range index.
62581 	  * arm-dis.c (get_sym_code_type): Check for non-ELF symbols.
62613 	This adds some operators and methods to gdb_mpq, in preparation for
62673 	with the return value of proc ${board}_file for delete, so fix this.
62678 	Likewise for board local-remote-host.exp, so remove proc ${board}_download and
62687 	  * dwarf.c (display_debug_lines_decoded): Reduce space for filenames.
62693 …* doc/as.texi (Pseudo Ops): Document that data directives such as .byte and .int are not intended …
62704 		(slurp_dynamic_symtab): Likewise for dynsymcount.
62711 		one extra for strings.
62725 	the -I dirs would be searched for the path.
62737 		use notes for include path.
62772 	stepping; it controls the size of the buffers allocated for the
62777 	However, it has started to be used in other places in GDB, for
62784 	ARM, and AArch64 for examples of this.
62798 	that the default for displaced_step_buffer_length will be the
62812 	gdbarch: make invalid=True the default for all Components
62813 	This commit switches the default value for the 'invalid' field from
62817 	I think that True is a good choice for the default, this means that we
62862 	obviously not needed.  These are lines for components that are not
62863 	Values (i.e. the component holds a function pointer anyway), or for
62884 	The validation algorithm for gdbarch values is now:
62886 	  - If the Value has an 'invalid' field that is a string, use that for
62914 	gdbarch: use predefault for more value components within gdbarch
62924 	All use a postdefault but no predefault to set the default value for
62927 	As the postdefault values for these components are all constant
62942 	and for the 'invalid' property to be a string.
62944 	Removing the option for 'invalid' to be None allows us to simplify the
62954 	it easier for others to add new components in the future.
62958 	for this field from None to False.
62976 	a comment noting that the validation has been skipped for a specific
62979 	In gdbarch_components.py I've had to add 'invalid=True' for two
62983 	And in gdbarch.py I've reworked the logic for generating the
62984 	verify_gdbarch function, and for generating the getter functions.
62986 	The logic for generating the getter functions is still not ideal,  I
63032 	Due to the algorithm used in gdbarch.py for generated verify_gdbarch,
63034 	be generated for the component, as such setting 'invalid=True' on the
63079 	DW_TAG_namespace for "main".  This happens because the file is named
63082 	least for me.  The namespace always is generated, but perhaps this
63098 	[gdb/testsuite] Fix gdb.python/tui-window-factory.exp for remote host
63114 	[gdb/testsuite] Fix gdb.python/tui-window.exp for remote host
63128 	[gdb/testsuite] Fix gdb.tui/completion.exp for local-remote-host-notty
63139 	Fix this by adding the missing check for readline_is_used.
63145 	[gdb/testsuite] Fix gdb.tui/tui-layout.exp for remote host
63154 	has effect, which is not the case for remote host.
63156 	Fix this by skipping the test for remote host.
63162 	[gdb/testsuite] Fix gdb.tui/tui-nl-filtered-output.exp for remote host
63170 	check for this, and consequently runs unsupported tests.
63178 	[gdb/testsuite] Require ![is_remote host] for TUI
63196 	For now, simply make TUI unsupported for remote host, by returning 0 in
63258 	[gdb/testsuite] Fix gdb.threads/step-bg-decr-pc-switch-thread.exp for native-gdbserver
63269 	(gdb) WARNING: Timed out waiting for EOF in server after monitor exit
63279 	[gdb/obvious]: fix python formatting for test gdb.python/py-typeprint.py
63285 	gdb/testsuite: add regression test for per-objfile typeprinters
63289 	out-of-tree for a while but I think it's worth upstreaming. The code
63300 	scalar_binop has code for "&&" and "||", but I think this code can't
63315 	XML features for AArch64 targets is rather brief.  I have received the same
63325 	The documentation of the XML features for Arm targets is very brief.  I have
63402 	simplifies both the calls to sort and one other spot that checks for
63425 	for other external packages used by GDB such as zlib or zstd.  If a
63433 	for "local" componenets before external components.
63440 	ld: Allow R_386_GOT32 for call *__tls_get_addr@GOT(%reg)
63441 	Similar to d58854b6dd88e05dbf2a5d1c32c5acb7bd6ea274 for x86_64.
63454 	R_386_GOT32X was required for call *func@GOT(%ebx), so R_386_GOT32 was
63473 	ld: Allow R_X86_64_GOTPCREL for call *__tls_get_addr@GOTPCREL(%rip)
63485 	R_X86_64_GOTPCRELX was required for call, so R_X86_64_GOTPCREL was
63519 	(gdb) WARNING: Timed out waiting for EOF in server after monitor exit
63540 	[ Using $pp as shorthand for the pagination prompt
63541 	"--Type <RET> for more, q to quit, c to continue without paging--". ]
63566 	- without waiting for response to the "q\n", another test_multiline command is
63590 	WARNING: Timed out waiting for EOF in server after monitor exit
63597 	[gdb/testsuite] Fix py-autoloaded-pretty-printers-in-newobjfile-event.exp for remote target
63613 	(Using $so as shorthand for
63621 	for $so once it checks for is_target_filename.
63629 	[gdb/testsuite] Fix gdb.python/py-event-load.exp for remote target
63630 	Fix test-case gdb.python/py-event-load.exp for target board
63670 	Revert "Add support for the ASCII directive inside linker scripts."
63677 	This is a hopefully temporary reversion of new ld features for
63685 	Revert "ld: Use correct types for crc64 calculations"
63740 	the need for (potentially bogus) calculations when processing .insn.
63743 	Before altering how build_modrm_byte() works, arrange for this part of
63766 	x86: use set_rex_vrex() also for short-form handling
63767 	This is benign for all existing insns, but is going to be needed for
63769 	function, to avoid the need for a forward declaration.
63799 	[gdb/testsuite] Fix gdb.threads/pending-fork-event-detach.exp for remote target
63800 	Fix test-case gdb.threads/pending-fork-event-detach.exp for target board
63801 	remote-gdbserver-on-localhost using gdb_remote_download for $touch_file_bin.
63803 	Then, fix the test-case for target board remote-stdio-gdbserver with
63812 	objdump's read_section is never used for bss-style sections, so to
63888 	We could add a KFAIL for this, but the functionality the test-case is trying
63901 	[gdb/testsuite] Fix gdb.server/*.exp for remote target
63902 	Fix test-cases for target board remote-gdbserver-on-localhost by using
63909 	[gdb/testsuite] Fix gdb.server/unittest.exp for remote target
63915 	Selftests have been disabled for this build.^M
63922 	Selftests have been disabled for this build.^M
63939 	Selftests have been disabled for this build.^M
63961 	[gdb/testsuite] Fix gdb.server/sysroot.exp for remote target
63965 	- disabling the "local" scenario for remote host.
63971 	[gdb/testsuite] Fix gdb.server/multi-ui-errors.exp for remote target
63972 	Test-case gdb.server/multi-ui-errors.exp fails for target board
64000 	[gdb/testsuite] Fix gdb.server/server-kill.exp for remote target
64012 	  for target board remote-gdbserver-on-localhost, it returns the
64015 	Fixing the method for getting the inferior PID gives us fails, and there's no
64019 	original method of getting the gdbserver PID which does work for target board
64026 	[gdb/testsuite] Fix gdb.server/connect-with-no-symbol-file.exp for remote target
64049 	for a remote host configuration.
64059 		* ld.texi: Revert 2023-03-08 commit 9a534b9f8e3d.
64078 	OBJF_REORDERED is set for nearly every object format.  And, despite
64106 	ld: Use correct types for crc64 calculations
64146 		check for reloc overflow.  Don't abort on unexpected reloc type,
64160 	for architectures to provide either a return_value or
64200 	DIE, setting the CU members is only necessary for the toplevel DIE in
64225 	I realized that the memory for interp names does not need to be
64286 	this caused the configure check "checking for ELF support in BFD" to stop
64287 	working causing build failures as we need our LDFLAGS to be used for
64299 	Enable vector instruction debugging for AIX
64300 	AIX now supports vector register contents debugging for both VMX
64305 	[gdb/testsuite] Fix gdb.threads/execl.exp for remote target
64319 	to wait for all pending writes to the index cache.
64326 	[gdb/testsuite] Fix gdb.base/skip-solib.exp for remote target
64327 	Fix test-case gdb.base/skip-solib.exp for target board
64353 	[gdb/testsuite] Fix gdb.base/fork-no-detach-follow-child-dlopen.exp for remote target
64354 	Fix test-case gdb.base/fork-no-detach-follow-child-dlopen.exp for target board
64361 	[gdb/testsuite] Fix gdb.base/break-probes.exp for remote target
64372 	[gdb/testsuite] Fix gdb.dwarf2/dw2-zero-range.exp for remote-gdbserver-on-localhost
64373 	Fix test-case gdb.dwarf2/dw2-zero-range.exp for target board
64417 	[gdb/testsuite] Fix gdb.base/signals-state-child.exp for remote-gdbserver-on-localhost
64441 	Fix this by using an absolute path name for the exec on the target board.
64443 	The dejagnu proc standard_file does not support op == "absolute" for target
64464 	Modify altivec-regs.exp testcase for AIX
64481 	- making mi_locate_shlib check for mi_spawn_id, like
64524 …5:52: error: integer value -1 is outside the valid range of values [0, 15] for this enumeration ty…
64530 	matter, we have similar warning/errors for many of them, if we let the
64533 	clang is right that the value -1 is invalid for the enum type we cast -1
64539 	std::underlying_type for that.  It turns out that the comment just above
64590 	So, the "CHECK_VALID" above checks that this property works for enum flags the
64612 	- Some OS's use a different syscall for exit().  For example, the
64619 	  tests on non-Linux systems.  FreeBSD kernels for example use the
64717 	[gdb/testsuite] Use regular proc syntax for gdb_caching_proc
64757 	The DAP stackTrace implementation did not fully account for frames
64762 	This patch fixes the problem by adding another check for None.
64769 	catchpoints, for example Ada catchpoints, don't have this method.
64849 		to read dynamic symbols for synth syms.
64859 	that lineno_cache_bfd is somehow left pointing at memory for a closed
64860 	bfd and that memory is later reused for another bfd, not that I think
64867 		(get_relocs): Adjust for struct rename.  Don't call bfd_fatal
64879 	the case for command line errors.
64913 	difference is listed in the documentation for bash's POSIX-correct mode
65024 	There isn't really any good reason for code in rdcoff.c to distinguish
65026 	the array reserved for basic types and instead handles all types using
65040 	As for commit 72d225ef9cc7, handle type numbers starting anywhere.
65073 	for move-construction, and the (implicit) move constructor copies the
65103 	gdb: LoongArch: Add support for static data member in struct
65180 	GDB has support for handling multiple debug formats, but the common use case
65181 	for ctf is to be used when dwarf2 is not present, and gdb reflects that,
65210 	uses of "set always-read-ctf on", but I've left that for another commit.
65235 	Use const for dwarf2_property_baton
65267 	when defined, and that determine whether the magic NARG parameter be
65329 	This could be caused by the same hw bug as we already have an xfail for, so
65342 	Also fix an error introduced in 1998 in reporting a zero count for
65346 	      Correct order of tests for invalid repeat counts.  Ensure
65352 	Fix an internal error after "non-constant fill count for absolute
65404 	think this bit is more relevant for the "catch throw" part of the test-case,
65442 	gdb: fix mi breakpoint-deleted notifications for thread-specific b/p
65456 	breakpoint-deleted notification for that breakpoint, and indeed, this
65522 	As GDB prints the breakpoint, the thread-id for the breakpoint is
65529 	thread for the thread-specific breakpoint has exited.  The
65541 	breakpoint_deleted observer for any breakpoint with the number zero.
65597 	be hidden from the user, for example, the breakpoint is removed from
65606 	wait for GDB to next stop before sending the notification.
65623 	print the thread-id for an exited thread.
65646 	for the breakpoint exits.
65662 	After my change the breakpoint_deleted notification (for
65675 	My solution is to follow the model for how bpfinishpy_pre_stop_hook
65796 	patterns for thread specific breakpoints, make use of this
65797 	functionality for gdb.mi/mi-nsmoribund.exp and gdb.mi/mi-pending.exp.
65836 	I've update lib/mi-support.exp to provide support for building
65861 	  /* NOTE drow/2003-09-08: This state only exists for removing
65865 	disp_del_at_next_stop state is not just used for deleting watchpoints,
65880 	[Aarch64] Add Binutils support for MEC
65897 		(print): Use PRIdPTR for *isp.
65922 	More anti-fuzzer bounds checking for the ECOFF support.  A lot of this
65923 	is in ancient code using "long" for counts and sizes, which is why the
65928 	care to do for COFF/ECOFF.
65966 	call set_quit_flag and, for gdb_exception_forced_quit, also
65971 	existing catch swallows the exception.  I've added a catch for
65978 	Thanks to Pedro Alves for suggesting this idea.
66006 	QUIT processing w/ explicit throw for gdb_exception_forced_quit
66007 	This commit contains changes which have an explicit throw for
66008 	gdb_exception_forced_quit, or, in a couple of cases for gdb_exception,
66014 	in these cases, a catch/throw for gdb_exception_forced_quit was added.
66035 	However, for this case, we must take care not to change the way that
66038 	catch/throw for gdb_exception_forced_quit.  I also did a bit of
66039 	rewriting here, adding a catch for gdb_exception_quit in favor of
66040 	checking the 'reason' code in the catch block for gdb_exception.
66060 	to swallow a gdb_exception_quit for SIGTERM.  However, it does seem
66063 	check the exception's 'reason' field for RETURN_FORCED_QUIT and
66064 	do a throw for this case.
66073 	This commit contains QUIT processing updates for GDB's Guile support.
66078 	I've adopted the same solution that I used for Python; whereever
66080 	language support, a catch for gdb_exception_forced_quit has been
66091 	See the previous patches in this series for the motivation behind
66096 	language; I made an attempt to do this for gdb_exception_quit in an
66101 	a SIGTERM for GDB, nor do we want to force modules written in the
66103 	idea is for GDB to cleanup and quit for this exception, we'll simply
66114 	As described in the previous commit for this series, I became
66118 	propagate the exception for a Ctrl-C / SIGINT, but I don't think that
66133 	  2) The catch block contains a throw for conditions that it
66137 	  3) There was (also) a catch for gdb_exception_quit.
66142 	My first thought was to add catch blocks for gdb_exception_quit and
66160 	setting of this global is the important bit for the SIGTERM part of
66167 	ensure that the user won't have to wait too long for a Ctrl-C or
66186 	...we found that it is possible for inferior_ptid and current_thread_
66193 	if sync_quit_force_run is set."  However, after the v2 series for this
66194 	patch set, we tweaked that idea by introducing a new exception for
66210 	for gdb.base/gdb-sigterm.exp when run on a machine with glibc-2.34.
66230 	a wrapper for throwing the exception, throw_forced_quit().
66263 	gdb.Value.  The rationale for this is that if you write a command that
66275 	Python for pretty-printing.  Now, normally this route boxes the value
66297 	for him, I can't make it fail on this machine; nevertheless, he tried
66306 	anymore for anything.  Remove it.
66320 	... follow_fork notices that thread 1 had last stopped for a fork
66336 	stopped for a fork which hasn't been followed yet, and because thread
66345 	influence the execution command that the user issued for the parent
66358 	for a solo-thread resume (to collect the vfork_done event), with
66384 	stopped for a fork/vfork, and if so,
66400 	  * thread 1 stops for fork
66415 	  * thread 1.1 stops for fork
66429 	  * thread 1 stops for fork
66439 	TARGET_WAITKIND_FORKED.  Thanks to Simon for this example.
66502 	know which thread we are printing info for.  For example, for the
66506 	 Last stopped for thread 2.1 (process 710867).
66510 	 Type "info stack" or "info registers" for more information.
66520 	 Type "info stack" or "info registers" for more information.
66539 	 Last stopped for thread 2.1 (process 710867).
66551 	 Last stopped for thread 2.1 (process 710867).
66575 	I have since found a new motivation for this change -- I would like to
66702 	readers know what attributes exist for entries, which is not clear
66826 	because for this function, rustc doesn't follow the platform ABI.
66834 	also remove the directives intended for GNU indent.
66840 	type, at least for the purposes of agent expressions.  This patch
66841 	arranges for range types to be handled this way in ax-gdb.c, letting a
66846 	Implement some agent expressions for Ada
66872 	 for f in aarch64-linux.xml amd64-linux.xml arm-linux.xml bfin-linux.xml \
67251 	You can see the current master's table for Linux x86-64 here:
67264 	gas/testsuite: adjust another test for case insensitive file systems
67285 	This is used in the standard library for things like std::byte.
67329 …PR 28909 * doc/local.mk (asconfig.texi): Use "cp -p" to preserve timestamps. * Makefile.in: Regene…
67337 	Updated Serbian translations for gold, gprof and opcodes sub-directories
67345 	and only add a check for the correct output.  This commit adds new
67346 	options for both, tab and command completion.
67391 	opcodes/m68k: enable libopcodes styling for GDB
67392 	The following commit added libopcodes styling for m68k:
67400 	disassemble.c, which is needed in order for GDB to start using the
67418 	gdb already has several decent structures available for growing
67454 	cache.  In particular, the cache will require gdb to wait for the
67466 	waits for the index cache task to complete.
67468 	To avoid gdb exiting early, an exit observer is used to wait for all
67485 	for the next patch.
67488 	file.  It seems to me that checking for the existence of a build-id is
67489 	good enough for the index cache.
67500 	trigger failures in the regexp from dump tests, especially for those
67501 	checking for warnings or errors. They are usually skipping everything
67531 	Note that for some forms of XCHG, {store} has already been performing
67552 	x86: have insns acting on segment selector values allow for consistent operands
67567 	smallest_imm_type() blindly setting .imm8 for signed numbers determined
67633 	variants that use GP for other purposes.
67667 	I noticed that the --disable-gdbmi option was broken for almost a year
67694 	some.  I couldn't find anybody caring deeply for that option, and it's
67727 	Commit 18b4d0736bc5 ("gdb: initial support for ROCm platform (AMDGPU)
67830 	memory and reading contents.  These size checks are not done for bss
67898 	Just like we suppress emitting REX.W for e.g. MOV from/to segment
67899 	register, there's also no need for it for LAR and LSL - these can only
67934 	return a NULL for an empty section, which was then treated the same as
67975 	Since configure.ac uses AC_SEARCH_LIBS to check for the curses library,
67979 	print_gdb_configuration because we would have to check for all 6 symbols
67981 	maintenance burden if support for other variations of curses are added.
68063 	  reported only once for each function it appears in
68098 	Updated translatios for the bfd and gprof directories.
68102 	gas/testsuite: adjust a test for case insensitive file systems
68107 	As the second filename doesn't matter in it, change it to fit for those
68117 	[aarch64] Enable pointer authentication support for aarch64 bare metal/kernel mode addresses
68118 	At the moment GDB only handles pointer authentication (pauth) for userspace
68121 	The Linux Kernel can be configured to use pauth instructions for some
68130 	There is a patch for QEMU that addresses the first point, and it makes
68174 	Fix that by outputting to a real file for all targets.
68188 		* testsuite/ld-libs/libs.exp: Don't run for alpha-vms.
68236 	This occurs because the code fragment for bfd_use_reserved_id comes
68245 	Don't use chew comments for static functions
68329 	gdb/doc: Consistency fixes for GDB/MI documentation
68337 	     Except for a few of the tracing command, which just use:
68348 	     Except for a few commands which use @subheading for the top-level
68349 	     command, and then continue to use @subheading for each part of
68362 	[gdb/symtab] Trust epilogue unwind info for unknown or non-gcc producer
68363 	Currently we only trust epilogue unwind info only for gcc >= 4.5.0.
68365 	This has the effect that we don't trust epilogue unwind info for:
68369 	Instead, only distrust epilogue unwind info only for gcc < 4.5.0.
68373 	[gdb/symtab] Trust epilogue unwind info for unknown producer (-g0 case)
68377 	compunit_epilogue_unwind_valid for cust == nullptr.
68403 	compunit_epilogue_unwind_valid for cust == nullptr.
68405 	But we'd run into the following problem for a -g0
68416 	while making sure that only one of the two is active.  Likewise for i386.  NFC.
68435 	And for i386:
68487 	I'm assuming it's the same root cause as for the already present XFAIL.
68498 	[gdb/testsuite] Fix gdb.threads/schedlock.exp for gcc 4.8.5
68500 	fast cpu"), the test-case fails for gcc 4.8.5.
68502 	The problem is that for gcc 4.8.5, the commit turned a two-line loop:
68565 	Use 'new' for block and global_block
68567 	use 'new' for allocation.
68696 	Fix "start" for D, Rust, etc
68697 	The new DWARF indexer broke "start" for some languages.
68702 	is for the code in find_main_name to use d_main_name to find the name.
68711 	approach will work for Pascal and Modula-2 as well, but I don't have a
68719 	However, we don't want to wait for canonicalization to be done before
68791 	gprofng: fix Dwarf reader for DW_TAG_subprogram
68806 		* libcollector/mmaptrace.c: Likewise for mmap64.
68816 	allocated for the main thread.
68841 	for *one* process with GDB's list of threads for *all*
68847 	true for the current inferior.
68851 	bug in solib-aix.c, where the BFD file name for shared
68853 	for the first time, which caused the library to no longer
68884 	- uses -nostartfiles -static, putting the burden for any necessary
68885 	  initialization for calling glibc's _exit on the test-case itself.
68943 	It's better to positively select targets for .section support than to
68975 		* config/tc-ppc.c (ppc_arch): Return bfd_arch_powerpc for ELF.
68989 	and it also claims that the 'x' response for an unavailable register
68999 	Add support for the ASCII directive inside linker scripts.
69005 	 * ld.texi (Output Section Data): Document the new directives.
69056 		file and arrange for dump_statistics to be called here rather
69305 	things for a similar reason.  This custom quit handler does nothing if
69401 	Fix this by simply adding an early check for
69436 	modern GCCs.  You would need to enable -Wswitch-enum for that, which
69438 	handling for the following type codes:
69456 	casing for whatever type code, I think that tests added at the same
69459 	somewhat incompletely than to error out and make it harder for users
69524 	gdb: fix dealloc function not being called for frame 0
69599 	  for (frame_info *fi = sentinel_frame; fi != NULL; fi = fi->prev)
69611 	the frame stash.  That is when we create the frame_info for the current
69613 	frame id.  The computation of the frame id for that frame (and only that
69620 	record_btrace_frame_dealloc_cache being called for each frame to remove
69624 	called for it, and it leaves a stale entry in bfcache.  That then leads
69645 		 Close a BFD. If the BFD was open for writing, then pending
69658 		 Close a BFD. If the BFD was open for writing, then pending
69683 	    the archive header for archive members).
69697 	     from the archive header for archive members).
69722 	leak memory, so I put some extra effort into trying to handle this for
69792 		* doc/webassembly.texi (File layout): Remove second argument from
69794 		* doc/bfd.texi: Use single-argument @node everywhere.
69837 	gdb: use std::string for internalvar::name
69895 	There are findex entries in annotate.texinfo,python.texi, and
69928 	Fix the linker's merge4 test for the HPPA architecture.
69933 	gdb, fortran: Fix quad floating-point type for ifort compiler.
69934 	I fixed this a while ago for ifx, one of the two Intel compilers, in
70035 	I suppose this was possible in the CVS days for the tui directory to be
70038 	sense.  Remove the check for that directory in configure.
70107 	ASCIZ Command for output section
70114 	In 162c6aef1f3a ("gas: fold symbol table entries generated for
70127 	particular the nul character. s_linefile() attempts to compensate for
70129 	when a newline ends the line. To facilitate such a check, the check for
70183 	deprecated_lval_hack.  Ultimately I think the goal should be for some
70575 	This renames all the fields of struct value, in preparation for the
70583 	this fixes the entry for 'fucomp' to use the correct Reg value
70659 	TUI window factory callback for Python defined TUI windows), are now
70683 	The documentation for gdb.register_window_type says:
70712 	In this commit, before the emplace call, I now search for an already
70720 	Fix doc build dependencies for --with-system-readline
70726 …make[4]: *** No rule to make target '../../../src/gdb/doc/../../readline/readline/doc/rluser.texi'…
70728 	The listed file (and hsuser.texi) are conditionally included by gdb.texinfo.
70731 	$BUILD/doc/GDBvn.texi with "@set SYSTEM_READLINE".  This surpresses the
70766 	      opcodes/mips: use .word/.short for undefined instructions
70772 	It was pointed out on the mailing list, that for microMIPS it would be
70789 	fails for some versions of guile.  It turns out that some versions of
70811 	in order to tidy memory on exit and to reinit everything for that
70840 	gdb/testsuite: look for hipcc in env(ROCM_PATH)
70842 	for it in $::env(ROCM_PATH) (if set).  If hipcc is still not found,
70862 	in an application, but GDB cannot debug it (at least for the offload
70867 	device available and that hipcc can compile for this or those targets.
70938 	gdb: fix describe_other_breakpoints for default task being -1
70944 	      gdb: use -1 for breakpoint::task default value
70970 	for the breakpoint, one location will be within the function itself as
70972 	for the call to the named function.  Consider this session:
71001 	for foo, and use these to create entries in GDB's msymbol table:
71004 	    the plt entry for foo, from this we add two entries into GDB's
71020 	iterate_over_minimal_symbols passing in the name we are looking for
71024 	the name we're looking for as the hash key), first we walk the hash
71028 	When the language is C++ the symbols for 'foo' will all have been
71041 	skip any parameters in the demangled symbol name when checking for a
71044 	once the string we are looking for ('foo' here) is exhausted, if we
71054 	mst_solib_trampoline, and in search_minsyms_for_name, we search for
71066 	By contrast, for C, there are no demangled hash table entries to be
71069 	symbol obviously matches when we are looking for 'foo', but in this
71072 	And so, when the user asks for a breakpoint in 'foo', and the language
71074 	symbol for foo in the shared library, while, when the language is C++,
71075 	we get two results, '_Z3foov' for the shared library function, and
71076 	'_Z3foov@plt' for the plt entry in the main executable.
71080 	success, GDB will instead search forward for the matching, closing,
71087 	gdb.linespec/cpcompletion.exp, when searching for the symbol of a
71118 	gdb: use -1 for breakpoint::task default value
71120 	which are used for thread or task specific breakpoints.  When a
71129 	What this commit does is switch to using -1 as the "default" value for
71130 	both fields, this means that the default for breakpoint::task has
71156 	was the first testing for this corner of the APIs, so I ended up
71175 	GDB, but for a new user, the manual doesn't suggest combining them is
71228 	gdb: add test for readline handling very long commands
71229 	The test added in this commit tests for a long fixed readline issue
71231 	Fedora GDB tree for several years, but I don't see any reason why this
71232 	test would not be suitable for inclusion in upstream GDB.  I've
71235 	The test is checking for an issue that was fixed by this readline
71371 	[gdb/tdep] Don't use i386 unwinder for amd64
71386 	and for amd64:
71405 	ISTM me there's no reason for the i386 unwinders to be there for amd64.
71408 	unwinders, see PR8434.  Currently, that's only available for both the dwarf2
71457 		* doc/binutils.texi (objdump options): Update -D, -s and -j
71473 		rather than objdump -D or objdump -d with tests checking for
71489 	open_source_file relies on errno to communicate the reason for a missing
71493 	for debuginfod_find_source to set errno to a value unrelated to the
71494 	reason for a failed download.
71496 	This can result in bogus error messages being reported as the reason for
71522 	optional parameter for specifying the errno used to generate the
71570 	Accesses with other languages work similarly, although for Ada only
71605 	such then and verify accesses to be in-range for them:
71620 	Consistently use the LONGEST and ULONGEST types for value byte/bit
71621 	offsets and lengths respectively, avoiding silent truncation for ranges
71639 	accesses cause an error for entries exceeding the currently selected
71641 	for elements located in the inferior, e.g.:
71669 	to lift the setting for value history accesses, under an implication
71689 	for minimum and maximum value macros provided by C++11.  Add LONGEST_MAX
71704 	gdb/testsuite: fix gdb.gdb/selftest.exp for native-extended-gdbserver
71813 	Output for i386:
71828 	Output for x86_64:
71860 	actual number of passes for the RISC-V linker relaxation from 3 to 2.
71882 	code and work for no gain.
71921 	elsewhere is SwapSources - see e.g. the BMI2 insns for similar operand
71946 	In generated code arrange for human readable output, by using the
71960 	Now that we have identifiers for the mnemonic strings we can avoid
71961 	opcode based comparisons, for (in many cases) being more expensive and
71965 	and hence LEA also needs checking for there.
71970 	Anti-fuzzer measure.  I'm not sure what the correct fix is for
72029 	[aarch64] Avoid initializers for VLAs
72030 	Clang doesn't accept initializer syntax for variable-length
72036 	The command has no effect for the loading of GDB pretty printers and is
72039 	Documentation for "set print pretty"
72045 	main_type::nfields is a 'short', and has been for many years.  PR
72046 	c++/29985 points out that 'short' is too narrow for an enum that
72053 	could be shrunk more drastically by using subclasses for the different
72077 	Let user C-c when waiting for DWARF index finalization
72079 	use C-c when the DWARF cooked index is waiting for finalization.  The
72112 		keep_contents for .loader.
72182 	gdb: give sentinel for user frames distinct IDs, register sentinel frames to the frame cache
72194 	   create a sentinel frame just for our user-created frame, in
72214 	   reason for frame 0, which requires trying to unwind frame 1.  This
72248 	   we created for it.  So the saved ID is the sentinel frame ID.
72261 	 - The ID of the sentinel frame created for the user-created frame is
72265 	 - Even if they had distinguishable IDs, sentinel frames created for
72271 	 - Give sentinel frames created for user frames their own distinct IDs
72279 	frames created for user frames (in create_new_frame) still have
72291 	The concrete changes for that part are:
72295 	   for building sentinel frame IDs and a is_sentinel_frame_id function
72309 	 - Change get_next_frame_sentinel_okay to check for a
72310 	   sentinel-frame-id-like frame ID, rather than for sentinel_frame
72320 	 - Change the "sentinel_frame != NULL" check in reinit_frame_cache for a
72331 	for nothing.  I however, noted in its comment that it is an
72334 	With this fix applied, the gdb.base/frame-view.exp now passes for me on
72350 	never call dealloc_cache for them.
72360 	cache, so we won't call dealloc_cache for them.  However, it's just a
72381 	expop.h needs block.h for a single inline function.  However, I don't
72397 	However, higher up the in chain, for the CLI we get to
72400 	  for (i = 1; i < nrules; i++)
72411 	and for MI we get to mi_cmd_interpreter_exec, which has:
72417 	    for (i = 1; i < argc; i++)
72496 	Many gdb.compile C++ tests fail for me on Fedora 36.  I think these
72504 …warning: Could not find symbol "_ZZ9_gdb_exprP10__gdb_regsE1a" for compiled module "/tmp/gdbobj-0x…
72553 	way for many years, seemingly without ill effect.  So, instead I chose
72587 	applying it to a symbol when the address is set.  This is done for
72624 	Test-case gdb.base/solib-corrupted.exp only works for a glibc without probes
72681 		* dwarf2.c (_bfd_dwarf2_slurp_debug_info): Correct test for
72690 	gdb: fix display of thread condition for multi-location breakpoints
72711 	Notice that, at the end of the location for breakpoint 3, the 'thread
72715 	In contrast, for breakpoint 2, the 'thread 1' appears randomly, in the
72717 	have the 'thread 1' information.  Additionally for breakpoint 2 we
72721 	1' for breakpoint 2 is due to a bug in print_one_breakpoint_location,
72742 	which makes the output the same for single location breakpoints and
72770 	All of the above points are also true for the Ada 'task' breakpoint
72776 	I've retained the existing code (but now only for MI like outputs),
72780 	updated all the tests I could find that checked for the old output.
72789 	PR 30080 * doc/binutils.texi (nm): Update description of the 'n' symbol type.
72796 	UNTESTED: gdb.ada/finish-var-size.exp: GCC too told for this test
72823 	gdb/doc: extend the documentation for the 'handle' command
72824 	The documentation for the 'handle' command does not cover all of the
72833 	for a single command, e.g. 'handle SIGFPE SIGILL nostop pass print',
72843 	So turning off the warning entirely for powerpc might not be the best
72845 	generated, unless the user explicitly asked for the warning.
72856 		* testsuite/ld-elf/elf.exp: Pass --secure-plt for powerpc to
72871 	No unwaited-for children left.^M
72892 	  which is already enough to make it impossible for me to reproduce the FAIL.
72914 	Currently, a thread or task specific breakpoint can only apply for a
72935 	I've added some new tests to check for the new error.
72939 	created.  Looking at what this test was for though, it was checking
73020 	only the requirement for resource_table to be aligned to 8.  But also
73029 	for which the default values (1 and 1) are sufficient.
73048 	CRT0 is spared from calling memset for the bss segment [1].  Instead the
73050 	for PRU, which typically has only 8KB for instruction memory.
73055 	bss sections).  This worked for the libgloss' CRT0.
73072 	section ordering, so I have disabled that test case for PRU.
73083 		* testsuite/ld-elf/orphan3.d: Disable for PRU.
73152 	In preparation for the following patch, where struct inferior needs to
73178 	Swapping operands for commutative insns occurs outside of
73179 	optimize_encoding() and hence needs explicit checking for a request to
73182 	x86: respect {nooptimize} for LEA
73184 	optimize_encoding() and hence needs explicit checking for a request to
73188 	The alternative encoding is valid for MOV, but there's no such thing for
73195 	precise: its <length>,<encoding> flavor) for disassembly.
73214 	gdb: initial support for ROCm platform (AMDGPU) debugging
73215 	This patch adds the foundation for GDB to be able to debug programs
73220 	The ROCm platform allows host programs to schedule bits of code for
73244 	      /* Allocate memory for the device to write the result to.  */
73252 	         point, waiting for the kernel dispatch to complete.  */
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
73333 …warning: Temporarily disabling breakpoints for unloaded shared library "file:///home/smarchi/build…
73339 	the same inferior.  This is a design goal for us, as programmers tend to
73346 	variables or printing a backtrace.  This is expected for the moment,
73357 	We think it's better to get the basic support for AMD GPU in first,
73358 	which will then give a better justification for GDB to support these
73365 	GDB uses the amd-dbgapi library [4], included in the ROCm platform, for
73392 	    duplicated and baked in GDB.  This is for example for things like
73411 	amd_dbgapi_target::fetch_registers for a simple example:
73434 	improbable for the init process to offload work to the GPU and much less
73435 	for the user to debug it).  We can therefore differentiate GPU and
73436 	non-GPU ptids this way.  See ptid_is_gpu for more details.
73443 	workaround for this is to have a dummy process (like a shell) fork and
73450 	is a precondition for amd_dbgapi_process_attach to work.  When the
73462 	support for the amdgpu architecture (amdgpu-tdep.c) depends on the
73463 	amd-dbgapi library being present, we have the following logic for
73466 	 - if the user explicitly asks for amdgcn support with
73467 	   --target=amdgcn-*-* or --enable-targets=amdgcn-*-*, we probe for
73470 	 - if the user uses --enable-targets=all, we probe for amd-dbgapi,
73474 	   we probe for amd-dbgapi, enable amdgcn if found and fail if not found
73477 	   we do not probe for amd-dbgapi, disable amdgcn support
73479 	 - otherwise, amd-dbgapi is not probed for and support for amdgcn is not
73513 	In ROCm-GDB, we install an solib provider for the GPU code objects on
73514 	top of the svr4 provider for the host, in order to add solibs
73569 	gdbsupport: add type definitions for pid, lwp and tid
73572 	types everywhere), define some type definitions in the ptid_t struct for
73600 	gdbarch_printable_names is used for a few things:
73608 	default, it is nullptr, meaning that the gdbarch accepts all "mach"s for
73626 	GDB has been converted to a C++ program for many years[1], and the
73636 	ld/doc: use "stack trace" instead of "unwind" for SFrame
73637 	SFrame format is meant for generating stack traces only.
73640 		* ld.texi: Replace the use of "unwind" with "stack trace".
73644 	bfd: use "stack trace" instead of "unwind" for SFrame
73645 	SFrame format is meant for generating stack traces only.
73658 	gas: use "stack trace" instead of "unwind" for SFrame
73659 	SFrame format is meant for generating stack traces only.
73676 	sframe: use "stack trace" instead of "unwind" for SFrame
73677 	SFrame format is meant for generating stack traces only.
73684 	libsframe/doc: use "stack trace" instead of "unwind" for SFrame
73685 	SFrame format is meant for generating stack traces only.
73688 		* doc/sframe-spec.texi: Use "stack trace" instead of "unwind".
73707 	but doesn't have any relevance there.  Instead is for aout64.h where
73713 	Provide a way for config/obj-* to clean up at end of assembly, and do
73714 	so for ELF.
73737 	for a specific process while current_thread is nullptr.
73866 	See previous patch's commit message for rationale.
73887 	[gas] Emit v2 .debug_line for -gdwarf-2
73897 		* dwarf2dbg.c (DWARF2_LINE_VERSION): Set to 2 for -gdwarf-2.
73901 		(out_debug_line): Don't output v3 standard opcodes for v2.
73996 	Updated Swedish translation for the binutils sub-directory
74000 	Re: Another fix for EFI generation with LTO enabled
74005 		* ldlang.c (lang_process): When rescanning archives for lto,
74011 	gas/ppc: Additional tests for DFP instructions
74027 	RISC-V: make C-extension JAL available again for (32-bit) assembly
74029 	moved as well by 839189bc932e ("RISC-V: re-arrange opcode table for
74030 	consistent alias handling"), for the assembler to actually be able to
74057 	appeared.  Someone might like to look into a better patch for the s390
74083 		"undefined line" depending on gcc version for s390.
74120 	For some reason g++ 12.2.1 on sparc produces spurious warnings for
74121 	stringop-overread and restrict in fbsd-tdep.c for a memcpy call.
74248 	First, a new mode is introduced: a sorting mode for
74265 	This is v2.  I believe it addresses the review comments, except for
74296 	Add small non-const and const wrappers for find and foreach.
74314 	gdb: Remove workaround for the vCont packet
74315 	The workaround for the vCont packet is no longer required due to the
74323 	gdb: Add per-remote target variables for memory read and write config
74324 	This patch adds per-remote target variables for the configuration of
74329 	The former global variables for that configuration are still available
74330 	to allow the command line configuration for all future remote
74339 	available, the default configuration for future remote connections is
74342 	configuration for future connections will be shown.
74345 	for --target_board=native-extended-gdbserver.  With that board GDB
74349 	for the current inferior.  To fix this, the clean_restart command is
74356 	for future remote connections and for the currently selected target, the
74366 	the fact that the global arrays that hold data for the remote packets
74373 	that for another pass, since it does not appear to be trivial, and I'd
74382 	Given the following setup for two gdbservers:
74389 	Before this patch configuring of range-stepping was not possible for one
74390 	of two connected remote targets with different support for the vCont
74411 	Two warnings are shown.  The warning for inferior 1 should not appear
74432 	Now only one warning is shown for inferior 2, which is connected to
74457 	remote target is selected the default configuration for future
74460 	If we have for instance the following setup with inferior 2 being
74485 	PACKET-NAME' commands and the new configuration impact for remote
74575 	With this changes I'm now only seeing a single refresh_window call for
74587 	The two calls would trigger in for the tui-disasm-long-lines.exp test
74775 	descriptor for gdb_stderr, and, as a result, does not currently format
74808 	itself causes an error for some reason, or, if we handle a single at a
74865 	Error (b) will trigger if NAME is ambiguous for multiple windows that
74880 	There are tests included for all the new errors.
74898 	Another fix for EFI generation with LTO enabled.
74907 	  logic and eliminating a conditional for operand-less insns,
74913 	also specify VEX3SOURCES. Hence there's no need for an "else" to the
74916 	x86: use ModR/M for FPU insns with operands
74921 	Now that we have identifiers for the mnemonic strings we can avoid
74922 	opcode based comparisons, for (in many cases) being more expensive and
74930 	such instrumentation in general (i.e. now for ia64-gen.c only), as that
74947 	no need to go looking for the output bfd via link_info (and doing so
74954 		* emultempl/pep.em: As for pe.em.
74975 	bfd_cache_close_all is good for closing file descriptors, but doesn't
74985 	This tidies memory allocated for entries in macro_hash.  Freeing the
74991 	There is also a fix for
75015 	gas/testsuite: Add -gcodeview test for aarch64-w64-mingw32
75016 	This is a copy of the x86 gas -gcodeview test, with changes made for the
75019 	gas: Add CodeView constant for aarch64
75085 	also provides a nicer model to copy for future tests.
75112 	    gdb/testsuite/fortran: Fix info-modules/info-types for gfortran 8+
75125 	Use ordinary calling convention for clean_restart
75149 		demand_copy_C_string for file.
75159 		is NULL (which it is for objdump -W) get the output bfd via the
75179 	gdb/testsuite/dap: fix gdb.dap/basic-dap.exp disassembly test for PIE
75193 	I chose to fix this by watching for a breakpoint changed event giving
75211 	waiting for some event, it checks if it received another event
75232 	access their contents.  This commits makes things a bit simpler for them
75247 	This catch didn't cause me any trouble, but for the same reason as the
75249 	propagate, to make for easier debugging.
75319 	limited, bailing out for gcc >= 4.5.0.
75321 	There was no regression test added for this preference scheme, so if we now
75325 	Fix this by adding an amd64 and i386 regression test for this.
75362 	caching the values for the stack pointers for the inner frame.  By
75368 	gdb: dwarf2 generic implementation for caching function data
75369 	When there is no dwarf2 data for a register, a function can be called
75378 	The cache object is unique for each function and frame, so if there are
75429 	There are definitely more of these; for example dw2-ranges.exp fails
75474 	[gdb/testsuite] Fix gdb.base/unwind-on-each-insn.exp for -m32
75543 	The comment seems no longer valid, the functions technically check for
75579 	For x86_64-linux, we have a reasonably complex foo (and similar for -m32):
75589 	Also for s390x-linux (and similar for -m31):
75599 	Likewise for powerpc64le-linux:
75612 	But for aarch64-linux, we have:
75672 	Also I've checked that the test-case still functions as regression test for PR
75688 	gdb/tui: better filtering of tab completion results for focus command
75695 	This commit improves the tab-completion results for the focus command
75705 	true that there is a tui_win_info object for every window at all
75706 	times.  We now only create a tui_win_info object for a particular
75784 	correctly.  The test should display the disassembly for the test
75799 	for a crash in GDB when the long identifier was encountered, I think
75800 	there is value in just leaving the test as it is for now, I have a fix
75801 	for the issue of the newpad call failing, which I'll post in a follow
75842 	The previous commit touched the source file for the test script
75871 		* doc/gprofng.texi: Update documentation for gprofng.
75890 	   @textrm Specify which key is used for signing the return
75909 		* doc/sframe-spec.texi: Fix various underfull and overfull
75925 	     for defined, global symbols.
75952 	ld: Avoid magic numbers for subsystems in pe.em and pep.em
75960 	ld: Set default subsystem for arm-pe to IMAGE_SUBSYSTEM_WINDOWS_GUI
75962 	default subsystem for arm-pe from 9 (IMAGE_SUBSYSTEM_WINDOWS_CE_GUI) to
75971 	Add support for secidx relocations to aarch64-w64-mingw32
75972 	This patch adds support for the .secidx directive and its corresponding
75977 	This is needed for PDBs, which represent addresses as a .secrel32,
75980 	The test is substantially the same as for amd64, but with changes made
75981 	for padding and alignment.
76012 	and $x29 (and strip the output of info frame to the first line, for brevity):
76095 	For for instance gcc x86_64 though, -fasynchronous-unwind-tables is enabled by
76104 	gdb.base/unwind-on-each-insn.exp stops being a regression test for commit
76116 	Updated Swedish translation for the binutils sub-directory
76125 	fix for gdb.base/unwind-on-each-insn.exp").
76160 	Fix objdump --reloc for specific symbol
76207 	believe this is the right use case for mutable.
76231 	current target frame (for frame 0) or frame_find_by_id (for other
76241 	test added by the previous patch by setting a pretty-printer for the
76259 	for that, it's more reliable.  I left the gdb.base/frame-view.exp pretty
76308 	Here, we create a custom frame for thread 1 (using the stack from thread
76309 	2, for convenience):
76376 	selected_frame_level for frames with level 0.  It leaves them at
76385 	!= 0` to account for the fact that we can restore user-created frames,
76392 	Add a minimal test case for the case described above, that is the
76414 	A subsequent patch makes it possible for frame_info_ptr to reinflate
76429 	frame_id::operator== to account for frame_id::user_created_p.
76446 	Later in this series, we'll need to differentiate frame ids for regular
76448 	ids for user-created frames (created with create_new_frame).  Add the
76496 	file dwarf2/call-site.h, but it doesn't sound like a good place for it,
76503 	concept, but for the moment it is only used in dwarf2/.
76526 	includes compile-internal.h for this reason, which kind of defeats the
76563 	I found this forward declaration for a struct that doesn't exist, remove
76571 	gdb.ada/ptype_tagged_param.exp is failing for me on x86-64 Fedora 36.
76586 …gdb/dwarf2/read.c:17689:20: runtime error: shift exponent 127 is too large for 64-bit type 'long u…
76615 	My obvious fix is just to skip the fixup for base types larger than a
76628 	gdb/testsuite: add test for negative subrange bounds with unsigned form
76634 	     with GCC, for instance, where the ambiguous DW_FORM_dataN form
76651 	Update gdb.dwarf2/subrange.exp to have a test for it.  When removing the
76680 	the test expects a second, but useless, $d mapping symbol for
76682 	for the completely merged section.  The new merging algorithm
76697 	  contents for lookup time
76699 	* care for cache behaviour for the hot lookup routine
76727 	bytes long. Otoh no register name is longer than 8 bytes. Hence even for
76734 	To amortize for the otherwise reduced folding of string literals by the
76742 	bytes long. Otoh no register name is longer than 7 bytes. Hence even for
76750 	Now that we have identifiers for the mnemonic strings we can avoid
76755 	- use the new shorthand for current_templates->start also elsewhere in
76761 	identifier for the following entry in a number of cases. Re-use that on
76766 	mnemonics are re-used for shorter ones, going beyond what compilers
76775 	even a 16-bit value would suffice. Use "unsigned int" for now, as
76788 	In preparation for changing the representation of the "name" field
76822 	GDB/testsuite: Expand for character string limiting options
76828 	with the `-elements' and `-characters' options for the `print' command.
76832 	Verify correct $_gdb_setting and $_gdb_setting_str values for the `print
76833 	characters' setting, in particular the `void' value for the `elements'
76836 	Add Guile and Python coverage for the `print characters' GDB setting.
76838 	There are new tests for Ada and Pascal, as the string printing code for
76852 	retain `set/show print elements' for controlling how many elements of an
76854 	which is used for controlling how many characters of a string are
76863 	option is set to `elements', which makes the limit for character strings
76870 	A corresponding `-characters' option for the `print' command is added,
76874 	`set/show print elements' setting, for characters as well regardless of
76906 	to the list of completions now shown for the `print' command, and a bare
76907 	minimum pair of checks for the right handling of `set print characters'
76908 	and `show print characters', copied from the corresponding checks for
76918 	options) to define arbitrary keywords for the user to use, removing
76919 	hardcoded arrangements for the `unlimited' keyword.
76930 	The "p" in `var_pinteger' stands for "positive", for the lack of a more
76932 	"n" would be confusing as to whether it stands for "non-negative" or
76936 	keywords allowed for a command and numerical values they correspond to.
76941 	follow the existing practice for some commands where user-entered 0 is
76944 	for completion as necessary.
76946 	So for example:
76955 	which get translated to INT_MAX for the setting to be used with.
76966 	is used for the requested setting.  If the last member were omitted (or
76967 	set to `{}') here, then only the keyword would be allowed for the user
76973 	replacing "only -1 is allowed to set as unlimited" previously used for
76975 	`var_pinteger' type.  It could only be used for the specific case where
76976 	a single extra `unlimited' keyword was defined standing for -1 and the
76977 	use of numeric equivalents is discouraged anyway as it is for historical
76989 	With these changes in place it should be trivial for a Scheme or Python
77036 	While we're at it, add an x31 alias for sp.
77046 	[gdb/testsuite] Fix gdb.python/py-value-cc.exp for big endian
77067 	Fix this by instead assigning 0x63636363, to ensure that u.c == 99 for both
77141 		* coff-aarch64.c (HOW): Define and use for reloc howtos.
77155 	perform the check unless it is needed.  There is precedence for this;
77200 	sim-main.h might get everything included just for the igen files.
77217 	callbacks for settings") and update inline documentation accordingly for
77226 	GDB: Add missing inline documentation for `add_setshow_cmd_full'
77228 	within cmd_list_element") and add missing description for
77231 	GDB: Correct inline documentation for `add_setshow_cmd_full_erased'
77236 	GDB: Fix documentation for `theclass' parameters in cli-decode.c
77237 	Rename CLASS to THECLASS in the documentation for `theclass' parameters
77249 	the wrong names for some source files.  Finally, a couple of obsolete
77263 	Revert "PowerPC: fix for gdb.reverse/finish-precsave.exp and gdb.reverse/finish-reverse.exp"
77270 	gdb: care for dynamic objfiles in build_id_bfd_get ()
77282 …_build_notes): Remember the last non-deleted note in order to speed up the scan for matching notes.
77299 	header is used to do the disambiguation for us, so that WinCE images get
77324 	PowerPC: fix for gdb.reverse/finish-precsave.exp and gdb.reverse/finish-reverse.exp
77352 	Test finish-reverse-next.exp is updated to include tests for the
77379 	behavior on X86 for the reverse-finish command now matches doing a
77388 	previous line.  The gdb output for tests gdb.reverse/until-precsave.exp
77447 	method already has a couple of local lambdas for a different hash
77475 	regressed for the arm target.
77494 	* The base instruction VCVT + NE for IT predication when inside an IT block.
77534 	Fix snafu in previous delta for elf32-csky.c
77551 	 checking for makeinfo... makeinfo --split-size=5000000
77576 	about the minor version for Texinfo > 6.9, we only care about the major
77589 	"foo" is at 0x2010.  This corrects the expected output for .long and
77633 	Updated translations for the gas and binutils sub-directories
77641 	for us to include, so we're doubly OK.
77647 	for us to include, so we're doubly OK.
77650 	This logic was added in order to expose the strsignal prototype for
77652 	and it takes care of probing system extensions for us, so there's no
77660 	rules would cascade such that it'd look for $arch/modules.o which
77694 	guarantees creating the depdir for us, so we can drop our configure hack.
77708 	Rather than force this to be built ahead of time for all targets,
77719 	DEPENDENCIES for targets that, alphabetically, come before "common".
77778 	"gdb --configuration", as was done for Python.  Then it changes the
77887 	Use "require" for Python tests
77888 	This changes various tests to use "require" for the Python feature.
78055 	    record that a test does not yet exist for some feature.
78123 	gdb: int to bool conversion for normal_stop
78134 	Updated Romainian translation for the bfd sub-directory
78142 	Disable ptype/o for dynamic types
78149 	Note that using "ptype/o" in this way makes sense for the time being,
78159 	exposes a problem for targets were that value is too high.
78161 	For example, for ARM(32, a.k.a. "Aarch32") specifically
78169 	an extreme value for an obscure corner-case.  The ARM
78188 	ld/testsuite: Adjust for ELF_MAXPAGESIZE 0x1000
78224 	all of them for the outdated-func-info thing we are checking here.
78278 	Thanks to Jose "Eye of the Eagle" Marchesi for spotting these.
78314 		* gold.h: Likewise, except for use inside GCC_VERSION < 4003.
78323 	Reflects the reality that I haven't done much on hppa32 for years.
78337 	Starting with Texinfo 7 (this commit [1]), the output directory for the
78382 	GCC recently added support for the Windows thread model, enabling
78387 	PR build/29966 points out that the GDB configure test for std::thread
78392 	for _WIN32_WINNT at configure time as is used at build time.
78420 		* dwarf2.c (read_indexed_address): Fix check for an out of range
78425 	[gdb/testsuite] Fix gdb.threads/dlopen-libpthread.exp for upstream glibc, again
78438 	Consequently, for each exec these dependencies are pulled in, including
78488 	gas/RISC-V: adjust assembler for opcode table re-ordering
78496 	the only insn _also_ allowing for a register as 1st operand (and then
78527 	gas: Restore tc_pe_dwarf2_emit_offset for pe-aarch64
78537 	This adds a mingw target for aarch64, including windres and dlltool.
78544 	Add .secrel32 for pe-aarch64
78555 	Fix size of external_reloc for pe-aarch64
78557 	support for creating aarch64 PE images.
78562 	needed for PDBs, and the SEH pseudos used for C++ exceptions.
78567 	AFAIK should be 10 for everything.
78571 	gdb/dwarf2: Fix 'rw_pieced_value' for values casted to different type.
78575 	for identity.
78598 	implemented for pieced values and causes an internal error if 'type'
78602 	fixes the previously mentioned cases by removing the check for identity.
78620 	'say_where' is only useful (and only called for) code breakpoints, so
78654 		* elf32-s390.c (elf_s390_relocate_section): Honor addend for
78656 		* elf64-s390.c (elf_s390_relocate_section): Honor addend for
78666 	PR 29981 references to init.texi
78672 	...bfd.texi:246: @include: could not find init.texi
78680 		* doc/bfd.texi: Don't include init.texi.  Adjust nodes to suit.
78785 	sim: build: add basic framework for compiling arch objects in top-level
78800 	sim: build: drop support for creating libsim.a in subdirs
78936 	The mips code is a little more tricky than others because, for multi-run
79182 	sim: build: drop support for subdir extra deps
79185 	header files (which we use automake depgen for now).
79190 	Add rules for tracking generated subdir modules.c files.  This doesn't
79266 	Similar to commit c799eddb3512, but for mips-ecoff.  mips-ecoff is
79283 	the only initialisation is for bfd.c static variables.
79295 		* doc/local.mk: Remove mention of init.texi and init.c.
79327 	needs to be returned.  The code mimics what has been done for AArch64.
79338 		reloc_class_ifunc for ifunc symbols.
79347 	Updated transaltions for the gprof and binutils sub-directories
79469 		for argument.  Adjust the check for SFRAME_FRE_TYPE_ADDR4_LIMIT
79474 		type for the argument.
79510 	Updated Bulgarian and Russian translations for LD and BFD respectively
79527 	long section names the intent is to do so for a particular bfd, not
79528 	for all bfds that might happen to be using the target xvec.
79569 	the block_symbol structure for the desired symbol, or an empty struct if
79580 	for example:
79587 	for interfaces using the mi interpreter to report the result.  It also
79598 	completion options for a function, either overload2_function,
79609 	about GMP and MPFR for gdb builds have been moved to the toplevel
79640 	move constructor being required for this to compile:
79687 	The following patch adds a hash type for gdb::string_view in gdbsupport,
79724 	instance, and dynamically allocate one as needed, like we do for all
79752 	[gdb/python] Avoid queue.SimpleQueue for python 3.6
79784 	Fix this by falling back to queue.Queue for python <= 3.6.
79820 	Un xfail the PR19719 test for the AArch64 architecture
79824 	Updated Bulgarian and Russian translations for the gprof subdirectory
79831 	allowed for the 32-bit reloc too.
79922 	10`, to account for the fact that reading the debug info of the gdb
79928 	desired change anyway for this kind of simple command / expected
79939 		* testsuite/ld-pe/cfi.d: Adjust for changed .idata padding.
79958 	the temp file is laid out for the large section.  It can take a long
79990 	      gdb: use libbacktrace to create a better backtrace for fatal signals
80005 	for 'GDB_PRINT_INTERNAL_BACKTRACE_USING_LIBBACKTRACE', so the second
80012 	for before the execinfo define, so we never actually end up using the
80053 		for differences in build environments.
80063 	with a 20-byte structure for each DLL, containing offsets into the rest
80069 	After this comes the .idata$4 entries for each function, which the
80098 	opcodes: xtensa: fix jump visualization for FLIX
80112 	Add test case for "finish" with variably-sized types
80113 	This adds a test case for "finish" with variably-sized types, and for
80151 	be reused.  However, for a call like "f(g())", the result of "g" might
80215 	The regression occurs for kernel versions v5.14-rc1 (the first tag containing
80218 	Fix this by adding an xfail for the appropriate kernel versions.
80245 	Updated translations for various languages and sub-directories
80277 	call_function_by_hand_dummy for "p strlen (p)" another call
80302 	sim: build: add var for tracking sim enable directly
80323 	only activates for `make all`, not `make foo.o`, but that shouldn't be
80354 	Rather than define our own hack for emitting an include statement,
80381 	it doesn't act like an ordinary interpreter -- for example it doesn't
80394 	threads are used for reading JSON from the client and for writing JSON
80411 	Fix target remote pipe command for MinGW
80416 	This results in the error message below for MinGW hosts:
80433 	I filed PR remote/29929 for this.
80496 	Delete a few files only used for obsolete targets, and tidy config,
80515 	sim: drop mention of & support for subdir configure
80551 	which automated the update of the copyright year range for all
80610 	Add markers for 2.40 branch
80617 	There's a command "disable probes", but SystemTap probes, for instance
80654 	For now, the command is only supported for SystemTap probes.
80671 	extended values in the same way as for enum values - e.g. a LF_ULONG
80685 	Updated Romanian translation for the binutils sub-directory
80689 	[gdb/python] Fix gdb.python/py-finish-breakpoint2.exp for -m32
80727 	problem out-of-scope for this patch. ]
80804 	Symbols already loaded for /lib/x86_64-linux-gnu/libc.so.6^M
80805 	Symbols already loaded for /lib/x86_64-linux-gnu/libpthread.so.0^M
80885 	[gdb/testsuite] Fix gdb.threads/dlopen-libpthread.exp for upstream glibc
81021 	displays the DWARF5 entry 0 for the program current directory rather
81022 	than "." as is done for pre-DWARF5.  I decided against displaying
81023 	DW_AT_comp_dir for pre-DWARF5 since I figure it is better for readelf
81029 		directory entry 0 for DWARF5.  Properly check directory index
81031 		unsigned int for n_directories and associated variables.
81043 	This commit makes CSR class handling for 'Smstateen' and 'Ssstateen'
81048 		* config/tc-riscv.c (riscv_csr_address): Simplify the logic for
81082 	Allocate input section memory for -z pack-relative-relocs if needed.
81107 	The gdb.gdb self-tests were timing out for me, which turned out to be
81113 	This patch adapts the two failing tests.  This makes them work for me,
81135 	Originally there was only one set of rules for generating code from
81158 	I spent a lot of time staring at this code, building for diff mips
81166 	for merging the itable logic among all ports, rename "multi_flags" to a
81197 	I think the test for table->files[file].dir being non-zero is wrong
81198 	for DWARF5 where index zero is allowed and is the current directory of
81204 	Also, there is no need to check for table->dirs non-NULL, the
81212 	Add support for x86_64-*-gnu-* targets to build x86_64 gnumach/hurd
81220 	sim: build: drop support for subdir distclean
81222 	to the top-level build, so we can drop support for this hook.
81235 	source buffer for the memcpy needs to point to the uint8_t/uint16_t sized
81273 	The igen tool sets up the SD & CPU defines for code fragments to use,
81283 	The igen tool sets up the SD define for code fragments to use, but
81300 	but this is a required first step for that.
81344 	      gdb/testsuite: new test for recent dwarf reader issue
81347 	of 'info sources' to figure out if the debug information for a
81350 	observed on some systems where the debug information for the
81365 	There's no need for these settings to be in sim-main.h which is shared
81378 	Use bool for dwarf2_has_info
81397 	this buffer for its usage.  This code is necessary when the target
81413 	I see this fail since commit 991180627851 ("Use toplevel configure for
81414 	GMP and MPFR for gdb"):
81428 	There's no need for these settings to be in sim-main.h which is shared
81436 	There's no need for these settings to be in sim-main.h which is shared
81441 	There's no need for these settings to be in sim-main.h which is shared
81446 	There's no need for these settings to be in sim-main.h which is shared
81451 	There's no need for these settings to be in sim-main.h which is shared
81456 	There's no need for these settings to be in sim-main.h which is shared
81461 	There's no need for these settings to be in sim-main.h which is shared
81483 	There's no need for these settings to be in sim-main.h which is shared
81488 	There's no need for these settings to be in sim-main.h which is shared
81493 	There's no need for these settings to be in sim-main.h which is shared
81500 	There's no need for these settings to be in sim-main.h which is shared
81520 	There's no need for these settings to be in sim-main.h which is shared
81532 	There's no need for these settings to be in sim-main.h which is shared
81539 	There's no need for these settings to be in sim-main.h which is shared
81548 	There's no need for these settings to be in sim-main.h which is shared
81557 	There's no need for these settings to be in sim-main.h which is shared
81567 	There's no need for these settings to be in sim-main.h which is shared
81579 	There's no need for these settings to be in sim-main.h which is shared
81587 		* dwarf2.c (concat_filename): Fix check for a directory index off
81595 	new APIs used here, and leave the test for their actual
81629 	Enable compilation of ld/pdb.c just for x86, as is done for bfd/pdb.c.
81641 	The common sim headers should define these for us already, so there's
81642 	no need for the ppc header to set them up.
81652 	be needed in other specific modules, but for now let's kick it out of
81709 	have to list the mips8000 bfd for it.
81713 	targets, so reuse that for mips64vr5* targets too.  This moves
81719 	RISC-V: Relax the order checking for the architecture string
81743 	    multi-keyword will possible be a single extension for the current parser.
81774 	The latter type matches the address size configured for this sim.
81782 	The latter type matches the address size configured for this sim.
81806 	sim: m32r: include sim-hw.h for sim_hw_parse
81815 	2) The size for the pdb name was incorrectly calculated.
81819 		(setup_build_id): Add size for the base name of pdb_name, not
81828 	targets, so reuse that for mips64vr43* targets too.  This moves
81838 	sframe: doc: update documentation for pauth key in SFrame FDE
81841 		* libsframe/doc/sframe-spec.texi
81845 	gas: sframe: testsuite: add testcase for .cfi_b_key_frame
81847 	generation for both the .cfi_negate_ra_state and .cfi_b_key_frame
81860 	objdump/readelf: sframe: emit marker for SFrame FDE with B key
81869 	gas: sframe: add support for .cfi_b_key_frame
81877 		(sframe_v1_set_func_info): Add new argument for pauth_key.
81886 	sframe.h: add support for .cfi_b_key_frame
81888 	pointers. There are two key for executable (instruction) pointers. The
81896 	FDE to indicate which key is used for signing the frame's return addresses:
81914 	gas: re-arrange listing output for .irp and alike
81918 	avoid producing a listing line for (non-existing) line 0 when the source
81970 	Like AVX-VNNI both VAES and VPCLMUL take AVX2 as a prereq, for operating
81975 	and KL take SSE2 as a prereq, for operating on packed integers. And
81982 	CPU_*_MASK for the 3rd argument of SUBARCH() - they need to use
81990 	  SUBARCH() (only extensions can be disabled, but unlike for Cpu*86 it
82032 	This drops support for the --enable-sim-float configure option,
82045 	Don't assume that the default bfd that we configured for is the one
82065 	objects for each target.  To avoid duplicating the list with the
82067 	a temporary hack until the top-level creates libsim.a for ports.
82081 	I've also changed find_abstract_instance to not use a temp for "name",
82095 	the #endif for the HAVE_LIBMPFR case.
82104 	Use toplevel configure for GMP and MPFR for gdb
82105 	This patch uses the toplevel configure parts for GMP/MPFR for
82106 	gdb. The only thing is that gdb now requires MPFR for building.
82109 	directory just like how it is done for GCC.
82114 	with GMP and MPFR in the toplevel (static library used at that point for both)
82137 		for gmp and mpfr.
82144 		for GMPLIBS.
82188 	Clang) do not show such a bug, so the test includes an XFAIL for gcc
82192 	multiple that all would need XFAILs for older GCCs (<= 4.3), and that
82199 	Updated Romanian translation for the BFD sub-directory.
82203 		* objdump.c (load_specific_debug_section): Check for excessively
82215 	While originally indeed used for register size checking only, the
82216 	attribute has been used for memory operand size checking as well already
82217 	for quite a while, with more such uses recently having been added.
82235 	consistently using `%pA' and `%pB'.  I'm no stickler for one style of
82238 	is emitted for multiple targets they all ought to use exactly the same
82283 	for the old sim_cpu_base layout.  There's a lot of noise here, so
82318 	sim: cgen: prep for inverting sim_cpu storage
82361 	the port uses the new arch_data field for its per-cpu state.
82371 	These headers define the register numbers for each port to implement
82387 	speeds up the build process and makes it easier for us to reason
82391 	generated spreg files.  It isn't a generalized tool for creating
82418 	libtool: install: Try `libtool --help --mode=install' for more information.
82426 	The discard of symbols should be performed whether the warning for
82513 	Use bool constants for value_print_options
82518 	quick_symbol_functions::relocated is only needed for psymtabs, and
82519 	there it is only needed for Rust.  However, because we've switched the
82521 	for this method at all.
82527 	PR mi/23170 for this.  I think it's finally time to remove this.
82555 	defines a post-hook for subcommand ("target testsuite").
82573 	New Romainian translation for the GOLD subdirectory.
82595 	gprofng/testsuite: correct names for signal handling tests
82597 	handlers, and hence for profile output to match anything in program
82603 	In order for so_syn.so and so_syx.so to be able to access the main
82614 	Cpu prefix isn't needed ther for disambiguation / name space separation.
82639 		checking for ld build directory.
82644 	This commit a new section for the next release branch, and renames
82678 	rawsize (the on-disk size for input sections) and size.
82714 	Commit 5aa0f10c424e added a per_xvec_warn array to provide support for
82715 	warnings from elf_object_p (and a later patch for warnings from
82726 	for the matching target.  If bfd_check_format_matches fails either due
82767 	sframe: doc: update spec for the mangled-RA bit in FRE
82770 		* libsframe/doc/sframe-spec.texi
82774 	gas: sframe: testsuite: add testcase for .cfi_negate_ra_state
82787 	objdump/readelf: sframe: emit marker for FREs with mangled RA
82799 	libsframe: provide new access API for mangled RA bit
82812 	gas: sframe: add support for .cfi_negate_ra_state
82823 		for mangled_ra_p.
82831 		(struct sframe_version_ops): Add a new argument for
82839 	sframe.h: add support for .cfi_negate_ra_state
82842 	as the "mangled RA" bit.  This bit is still unused for x86-64.
82884 	Fix previous delta to allow for compilation on 32-bit systems
82898 	     # Wait a bit, to give time for the threads to hit the
82906 	seconds (instead of 1) for the threads to start running, but only sleeping if
82917 	actually pretty hard for a user to find out more about that label.
82933 	goto label would not be an unreasonable thing for a user to do.
82936 	to provide a little context for why the following issue has probably
82939 	It turns out there is one way a user can access the symbol for a goto
82976 	After this asking for the value of a label symbol works just fine:
83036 		* dwarf.c (display_debug_addr): Check for corrupt header lengths.
83040 	gdb/testsuite: add test for Python commands redefining itself
83052 	[aarch64] Fix removal of non-address bits for PAuth
83076 	bits.  The hook is now responsible for removing the required non-address bits
83079 	While at it, make GDB and GDBServer share some more code for aarch64 and add a
83089 	While 6fdb723799e2 ("gas: re-work line number tracking for macros and
83095 	intended - it's being put there for processing during macro expansion
83102 	use a representation matching that of Intel SDM and AMD PM for the main
83158 	  /* We have a complete command line now.  Prepare for the next
83187 	to a location for output.
83211 		* sframe-api.h: Reorder fre_offsets for natural alignment.
83267 	wraps all the logic for creating a string that describes a target
83323 	empty (except for the ever present dummy_target).
83351 	switch_to_inferior_no_thread call as it is required for the
83417 	we risk creating multiple different gdb.TargetConnection objects for
83420 	To ensure that we have one gdb.TargetConnection object for each
83434 	wrong for us to be deallocating Python objects after the interpreter
83448 	If we take a look at quit_force (top.c) you can see that, for each
83451 	responsible for shutting down the Python interpreter.  The
83467 	In this commit I will provide a partial fix for the problem.  I say
83513 	test for this issue.  The test installs a listener and then causes
83546 	As the starting_up flag is initialized to false then, for the assert
83553 	Re: ld, gold: remove support for -z bndplt (MPX prefix)
83574 	I noticed after commit 8ad93045ed, "ld, gold: remove support for -z
83596 	different levels of verbosity for symbol-lookup debug.
83637 	gdb/testsuite: new test for recent dwarf reader issue
83638 	This commit provides a test for this commit:
83643 	      Add name canonicalization for C
83645 	Which resolves PR gdb/29105.  My reason for writing this test was a
83651 	The problem tested for here is already described in the above commit,
83660 	    for the name "int".  The "int" here is actually being looked up as
83661 	    the type for the result of the 'sizeof' expression,
83663 	  - In lookup_signed_type GDB first adds a 'signed' and looks for that
83667 	  - The problem is that 'signed int' is not the canonical name for a
83669 	    will then go to each object file in turn looking for a matching
83674 	    Remember, at this point GDB is looking for 'signed int', there
83683 	    'signed int' is just 'int', GDB then looks for any symbols with
83695 	progress far enough that the debug information for the library has
83701 	for the library to be fully expanded, while in the fixed version of
83720 	using the 'maintenance print objfiles' command, and looking for the
83721 	string 'faked for "readnow"' in the output.  This is implemented in
83737 	detection itself by checking $::GDBFLAGS for the readnow flag:
83742 	for "readnow"' string, as a consequence the testsuite can no longer
83752 	Next I have rewritten `readnow` to check the $GDBFLAGS for the
83754 	least for all the tests above, when using the readnow board, this is
83769 	RISC-V: Add string length check for operands in AS
83782 	        * config/tc-riscv.c (arg_lookup): Add string length check for operands.
83783 	        * testsuite/gas/riscv/vector-insns-fail-vsew.d: New testcase for an illegal vsew.
83790 	As Alan points out, ASAN takes issue with these constructs, for
83796 	ld, gold: remove support for -z bndplt (MPX prefix)
83824 		* ld.texi: Likewise.
83887 		* objcopy.c (copy_archive): Dup filename before closing bfd for
83904 	complicated thing for Wow64) seems better.
83924 	Refactor code to check for terminal sharing
83925 	This refactors the code to check for terminal sharing.
83938 	However, we believe this isn't likely to be an issue for gdb.
83942 	Use gdb::optional for sigint_ours
83989 	and that probably used to work for older kernels, but no longer does since
84061 	Dump of assembler code for function test:^M
84085 	gas: re-work line number tracking for macros and their expansions
84088 	be desirable for small macros, but often isn't for larger ones. As a
84092 	Note that macro invocation context is lost for any diagnostics issued
84093 	only after all input was processed (or more generally for any use of
84096 	intended workaround behavior for PR gas/16908, a new as_where() is
84098 	as_where() is renamed (and used in only very few places for now). Down
84106 	even in further cases .irp is more suitable for the purpose. Expand such
84108 	changed for code resulting from macro expansion.
84116 	is_nocall_function anticipates only being called for a function or a
84147 	static variables like mips_hi16_list are nasty for applications using
84231 	for PR20630, which can be reproduced (for an unfixed gdb) like this:
84278 	[gdb/testsuite] Fix gdb.base/write_mem.exp for big endian
84297 	If we print 4 bytes, we have for s390x:
84301 	and for x86_64:
84348 	The need for them on the operand-less string insns has gone away with
84357 	Having it in match_template() is unhelpful. Neither does looking for the
84381 	look for the next MOV template (in fact again also improving
84388 	supported in 64-bit mode" diagnostic as emitted for other 64-bit only
84399 	had no testcase whatsoever for these. Therefore such tests are being
84426 	for the MOVD variant. The test therefore is to avoid re-introducing such
84436 	x86: revert disassembler parts of "x86: Allow 16-bit register source for LAR and LSL"
84438 	register source for LAR and LSL"), adjusting testcases as necessary.
84502 	very little over half (not even accounting for any overhead
84504 	for the "start" slot of the subsequent one.
84513 	As requested by H.J., just for the sake of people potentially building
84538 	This also shrinks the number of relocations to be processed for
84548 	DWARF5 directory and file table allow more opportunity for fuzzers
84666 	gas: sframe: fine tune the fragment fixup for SFrame func info
84698 	sframe: gas: libsframe: define constants and remove magic numbers
84699 	Define constants in sframe.h for the various limits associated with the
84704 	Update the code in gas to use these defined constants as it checks for
84705 	these limits, and remove the usage of magic numbers.
84710 		(sframe_convert_frag): Do not use magic numbers.
84736 	[aarch64] Add TPIDR2 register support for Linux
84758 	enable it as is being done for the AArch64 Linux target.
84773 	The patch also adjusts the feature detection code for aarch64-fbsd, since
84791 	they apply to the addend for the next relocation rather than the
84827 	[gdb/testsuite] Fix gdb.guile/scm-symtab.exp for ppc64le
84836 	The problem is as follows: the instructions for the call to func2 are:
84853 	The test-case looks at the line numbers for two insns:
84879 		x32 IBT PLT for 64-bit.
84900 	[gdb/testsuite] Require debug info for gdb.tui/tui-layout-asm-short-prog.exp
84986 		* ld.texi (Output Section Type): Note that setting the output
85018 	PowerPC: Add support for RFC02655 - Saturating Subtract Instruction
85033 	PowerPC: Add support for RFC02656 - Enhanced Load Store with Length Instructions
85059 	Add KFAILs in test-case gdb.base/longjmp.exp for PR gdb/26967, covering
85081 		Only rename debug sections when decompressing for linker.
85097 		elf_section_data for non-ELF.
85122 		(bfd_convert_section_setup): Test obfd flags not ibfd for
85151 	bfd: Avoid signed overflow for new_size adjustment
85165 		for new_size adjustment.
85181 		* elf32-arm.c (cmse_scan): Check for NULL entries in the
85282 	x86: Remove unnecessary vex.w check for xh_mode in disassembler
85288 		* i386-dis.c (OP_E_memory): Remove vex.w check for xh_mode.
85293 	This flag also isn't needed, except for some sanity checks which we
85296 		* elf.c (elf_fake_sections): Don't set SEC_ELF_COMPRESS for
85316 	functions.  Renaming for ld input is simplified too.  Ld input object
85324 		input for linker.
85325 		(elf_fake_sections): Don't handle renaming of debug sections for
85371 		to zero for zlib-gnu case.
85443 	The UNRESOLVED for arrayptr.exp is fine, as GDB crashes in that test,
85497 	Use as many tabs as possible for indentation and pad with spaces to keep
85506 	Use tab for the first eight spaces of indentation, and align the gdb_printf
85517 	gas: add Dwarf line number test for .macro expansions
85532 	respective callers. Note that we need to compensate for the removed line
85537 	actually go look for the cause).
85544 	Arm: .noinit and .persistent are not supported for Linux targets
85556 	libopcodes/mips: add support for disassembler styling
85557 	This commit adds disassembler styling support for MIPS.  After this
85571 	All the gas, ld, and binutils tests still pass for me.
85575 	opcodes/mips: use .word/.short for undefined instructions
85576 	While working on disassembler styling for MIPS, I noticed that
85613 	Since commit 4bea06d73c04 COFF support for compressed debug sections
85641 	It works only for ELF targets.
85650 	x86: Allow 16-bit register source for LAR and LSL
85652 	of operand size, allow 16-bit register source for LAR and LSL, and always
85658 		* testsuite/gas/i386/i386.s: Add tests for LAR and LSL.
85676 		* i386-opc.tbl: Allow 16-bit register source for LAR and LSL.
85704 	rare that you will want to enable debug for one solib kind, and
85706 	instead of adding separate variables / macros / commands for each solib
85733 	x86: also use D for XCHG and TEST
85735 	and TEST templates we have. This way the reg <-> r/m (and reg <-> reg for
85742 	for powerpc64le") started using command "maint print architecture", which
85774 	source file was created for tests finish-reverse-bkpt.exp and
85781 	initial break point for the rest of the test on the function pointer call
85782 	for the function.
85819 	Add name canonicalization for C
85827 	every CU that has an entry for "int" -- i.e., nearly all of them.  A
85830 	for "signed int", it fails -- causing the loop to continue.
85832 	This patch fixes the problem by introducing name canonicalization for
85852 	lookup_signed_typename is simplified.  It used to search for two
85853 	different type names, but now gdb can search just for the canonical
85885 	While testing the fix for PR 29105, I noticed I couldn't ctrl-C my way
85911 	and thread_db_target::update_thread_list defers to that for any live
85915 	exited threads, but that is only used for non-live inferiors, where
85916 	threads can't exit anyway.  So the prune_threads call is not needed for
85959 	skip_compile_feature_tests checks for "Command not supported on this
85984 	    0000002e v000000000000000 v000000000000000 views at 0000002a for:
85992 		* dwarf.c (display_debug_loc): Adjust holes detections for
86014 	(Ab)using i386_opcode_modifier for this has been overkill, as the logic
86018 	bit in the loop for a simple comparison. Do the original compares inside
86023 	With LONG_DOUBLE_MNEM_SUFFIX gone there'salso no use for No_ldSuf
86027 	With the removal of its use for FPU insns the suffix is now finally
86033 	only need this pseudo-suffix for far branch handling. Stop "deriving" it
86034 	for floating point insns. (Don't bother renaming the now properly
86040 	[gdb/testsuite] Wait longer for core generation
86042 	file system, I run into timeouts due to core generation, like for instance:
86055 	[gdb/testsuite] Fix gdb.ada/float-bits.exp for powerpc64le
86064 	The problem is that we're using a hex string for the 128-bit IEEE quad long
86083 	and likewise for -mbig:
86094 	Note that for this patch to work correctly, recent commit aaa79cd62b8 ("[gdb]
86121 	[gdb/testsuite] Enable gdb.arch/s390-disassembler-options.exp for --enable-targets=all
86129 	the test for 'istarget "s390*-*-*"' with a test for 'get_set_option_choices
86149 	and all potential special cases for it aren't used anymore.  That also
86161 	So instead of looking at all sections names for each glob for each wild
86176 	This resets all section matches before updating for newly created
86190 		    if match: do action for S
86192 	And this process is done three or four times: for each top-level call to
86196 	So we iterate over all sections of all files many many times (for each
86202 	the matching process and memoizing results, trading a little memory for
86233 	reflect what the field is used for.  I also added a couple of
86254 	    /* Just print out one of them - this is only for diagnostics.  */
86287 	x86: clean up after removal of support for gcc <= 2.8.1
86295 	   generated output for these two commutative opcodes, and hence the
86315 	two templates - we can simply arrange the condition for setting
86320 	x86: extend FPU test coverage for AT&T / Intel mnemonic differences
86345 	GDB_SUPPORT_DIRS, similar to what was done for BINUTILS.
86357 	[gdb/testsuite] Fix gdb.base/vla-optimized-out.exp for ppc64le
86377 	When trying to evaluate DW_OP_GNU_entry_value, it looks for a call site
86406 	parameter i, for which we find location list entries:
86417 	Fix this by allowing <optimized out> for target powerpc and the gcc compiler.
86738 	will send gdb_stdlog output (among others) to the tee it makes for
86751 	for the convenience of the users.  In a subsequent patch, this will no
86752 	longer be convenient, so this patch moves the responsibility for
86757 	are generally bad, and there is no need for this one -- it can be a
86770 	Don't use auto for lambda parameter
86771 	Older gcc versions (here 4.9.2) can't handle auto for a lambda parameter:
86842 	Will compile just fine for C++11 and C++14 with GCC.  Clang on the
86855 	And for C++17 both GCC and Clang compile this just fine.
86862 	this macro expands to noexcept when compiling for C++17, but otherwise
86881 	code, will not be compiled with support for handling exceptions.  As
86885 	See bug gdb/29712 for an example of when this happened.
86904 …../../src/gdb/disasm.h:116:3: error: mangled name for ‘gdb_printing_disassembler::gdb_printing_dis…
86911 	manually check for that during review.
86919 	exception unwind information when compiling C code, for targets that
86977 	what we want is for this exception to propagate through GDB and appear
87022 	gdb.disassembler.builtin_disassemble.  I have no tests for this change
87057 	gdb: relax requirement for the map_failed stap probe to be present
87064 	In GDB, in solib-svr4.c, we have a list of probes that we look for
87067 	mechanism for detecting shared library loading.  The "map_failed"
87071 	always fall back to the non-probes based mechanism for detecting
87086 	the probe isn't actually required in order for GDB to correctly detect
87095 	for that same event, then GDB will stop when using the old style
87114 	system, GDB will once again use the stap probes for shared library
87158 	same limitation holds for tasks.
87167 	[gdb/testsuite] Fix gdb.ada/out_of_line_in_inlined.exp for ppc64le
87196 	sorting and have a fast path for insertion at end (aka rightmost tree
87200 	that uses it is avr (for 'SORT(*)(.ctors)'), and I believe even there it
87201 	was a mistake.  Either way, this adds a testcase for filename sorting as
87218 	We retain the implementation of match_simple_wild for the filename
87235 	did use gdb_start_cmd to start the inferior, for no good reason.
87259 	internally at AdaCore for a while.
87291 	When running the kill command, commit_resumed_state for the
87314 	ignore that for now)
87408 	request, we get to a thread of process 1 for which we haven't read
87441 	[gdb/testsuite] Fix gdb.opt/solib-intra-step.exp for powerpc64le
87518 	step-over for the conditional breakpoint in at least one thread.
87557 	inferior was the last one for that target.  It's the same rationale as
87558 	for patch "gdb: disable commit resumed in target_kill" that comes later
87559 	in this series, but for detach instead of kill.
87608 	We can work around this by marking variable a volatile.  Likewise for b.
87617 	[gdb/tdep] Fix gdb.base/msym-bp-shl.exp for ppc64le
87661 		* doc/binutils.texi (strings): Delete example of 7-bit encoding.
87693 	RISC-V: Better support for long instructions (tests)
87695 	for long instructions".
87708 	RISC-V: Better support for long instructions (assembler)
87738 	RISC-V: Better support for long instructions (disassembler)
87845 	The memory allocated for the target gdb_environ env variables is not released.
87866 	Use false/true for some inferior class members instead of 0/1
87874 	[gdb/server] Emit warning for SIGINT failure
87938 	FAIL: gdb.base/bt-on-fatal-signal.exp: SEGV: scan for backtrace (timeout)
87946 	seconds for a core file 50 times smaller than the one for gdb.
87963 	could not find '.gnu_debugaltlink' file for access-mem-running-thread-exit^M
87977 	the same result for the first and second file command.
88032 	Revert "readelf: Do not require EI_OSABI for IFUNC."
88048 		(riscv_csr_address): Add CSR classes for Smaia/Ssaia.
88095 		(DECLARE_CSR): Add CSRs for Smaia and Ssaia.
88097 	Changes for v3:
88098 	- Imply ssaia for smaia
88099 	- Imply zicsr for ssaia (and transitively smaia)
88103 	Changes for v2:
88115 	greater.  As such, it is not worthwhile to add requirement for a minimum
88122 		* libsframe/doc/sframe-spec.texi: Remove usage of
88203 	gdb/testsuite/gdb.base/break.exp: use proc_with_prefix for test_next_with_recursion
88205 	for consistency.
88234 	readelf: Do not require EI_OSABI for IFUNC.
88255 	bogus (for Intel Syntax) diagnostics referring to a wrong suffix (when
88257 	for insns where the template allows a register operand alongside a
88277 	of the templates for the assembler and separating decode of the
88291 	Mode/reg bits for these insns are 000 Dy, 001 Ay, and 111 100 for the
88295 		for move reg to macsr/mask insns.
88311 	and not just Mode and SPSEL bits for v8m targets without security
88324 	passed a NULL for "symbols".  Fix that too.
88354 	Document the memory_tagged argument for memory region callbacks
88401 	as we're not aware of any related failures, we declare this out of scope for
88416 	field for it.  That means, the high 2 bits could be other field and have
88419 	need the out-of-range check for R_RISCV_SUB6, and the overflow checks for
88442 	aarch64-fbsd: Use a static regset for the TLS register set.
88450 	arm-fbsd: Use a static regset for the TLS register set.
88459 	This is needed to permit using the helpers for register sets with a
88468 	fbsd-nat includes various helper routines for fetching and storing
88485 	this are the TLS register sets for the ARM and AArch64 architectures.
88500 	x86: Don't define _TLS_MODULE_BASE_ for ld -r
88505 		 _TLS_MODULE_BASE_ for ld -r.
88516 	Don't use "long" in readelf for file offsets
88552 	changes I had for the comments from Tomas in
88559 	Integrate back checks for fseeko{,64} into configure.ac, so
88568 	opcodes: Correct address for ARC's "isa_config" aux reg
88569 	This patch changes the address for "isa_config" auxiliary register
88576 		isa_config exists for ARC700 and ARCV2 and not ARCALL.
88582 	need to test for gcc in gdb.dwarf2/clang-cli-macro.exp and mark it as
88603 	This is necessary when building readelf for LLP64 systems, where a
88621 	Re: ld: Always output local symbol for relocatable link
88685 	Fix step-over-syscall.exp matching regexp for $bpnum.$locno matching
88686 	step-over-syscall.exp has some specific tests for gdbserver.
88705 	bin	* doc/binutils.texi (objdump): Note that the -m option supports
88711 	For targets with secext, msp and psp can be seen as an alias for one
88717 	For targets with secext, msp and psp can be seen as an alias for one
88723 	gdb/csky just return type from csky_vector_type() for vector resgisters
88724 	Some gdb stubs may not describe the type for vector registers in the
88727 	for vector resgisters.
88729 	gdb/csky return type int32 for float and vector pseudo regs
88731 	return builtin_type (gdbarch)->builtin_int32 for it.
88750 	on Solaris, at least as a workaround for GDB 13.
88752 	As Tom suggested in the PR, this is done using our infrastructure for
88789 	Simon's patch for PR build/29798).
88799 	With the addition of $gdb_prompt in the regexp testing for breakpoint hit,
88806 …Show locno for 'multi location' breakpoint hit msg+conv var $_hit_bbnum $_hit_locno PR breakpoints…
88846 	   for a breakpoint with a single location.
88848 	   they are set for silent breakpoints, and when several breakpoints
88867 	  - Use %s for the result of paddress
88870 	  - Add index entries for $bkptno and $locno
88871 	  - Added an example for "locno" in the mi interface
88906 		* testsuite/gas/riscv/ssstateen-csr.s: Test for 'Ssstateen' CSRs.
88954 	gdb_ps_prochandle_t structure, to avoid the need for a current process
89051 	work for those targets where we've selected a suitable register,
89060 	register structure (for the `this` pointer).
89062 	As the test is for a failure case, then we don't really care _which_
89063 	register the structure is in, and I take advantage of this for the
89125 	There's no particular reason for this change other than seeing the
89141 	When compiling with Clang though, the default is for no build-id.
89184 	These start/end labels are used for computing the function start, end,
89222 	for why the extra alignment is required.
89249 	support the -fdiagnostics-color=never option for the assembler, but
89250 	does for the preprocessor.
89273 	portable (see the comments in lib/dwarf.exp on function_range for
89286 	GAS fix alignment for aarch64-pe
89300 	Regen potfiles for sframe
89308 	[gas, aarch64]: fix build breakage for aarch64-pe
89309 	SFrame is supported for ELF only.  Keep the definitions and declarations
89354 	Support for printining non-trivial return values was recently added in
89361 	    PowerPC, fix support for printing the function return value for non-trivial values.
89388 	Use boolean literals for pagination_enabled
89410 	are striped.  elf_backend_output_arch_local_syms is defined only for
89438 	adjust the behaviour for multi-threaded inferiors.
89478 	seemed to work fine for my testing on x86-64.
89483 	escapes the '\' for us, thus we get '\\x' printed by 'maint packet'.
89494 	for me.
89498 	Fix call functions command bug in 64 bits programs for AIX
89499 	In AIX for 64 bit programs we need to zero extend variables
89513 	have a test for this, so this commit adds such a test.
89559 	  The warning is correct, so the code can lose support for the NULL
89664 	Breaking in the destructors for intrusive_list and frame_info_ptr shows that
89665 	in this configuration, the destructors for frame.c's statically-stored
89731 	Bug fix in commit for printing the function return value for non-trivial values
89738 	    PowerPC, fix support for printing the function return value for non-trivial values.
89771 	the check for the return buffer should be skipped.
89790 	this patch disables source and assembly code highlighting for the
89798 	completion limit for "complete set gnutarget":
89807 	Also use get_set_option_choices for "complete set architecture i386", which
89830 	PATH: gdb.arch/ppc64-symtab-cordic.exp: failed bzip2 for \
89862 		* libsframe/configure.ac: Check for makeinfo and set BUILD_INFO.
89864 		* libsframe/doc/sframe-spec.texi: Likewise.
89875 	binutils/NEWS: add text for SFrame support
89878 		* binutils/NEWS: Add item for SFrame support.
89892 	readelf/objdump: support for SFrame section
89893 	This patch adds support for SFrame in readelf and objdump. The arguments
89894 	of --sframe are optional for both readelf and objdump.
89902 		* binutils/Makefile.am: Add dependency on libsframe for
89905 		* binutils/doc/binutils.texi: Document --sframe=[section].
89906 		* binutils/doc/sframe.options.texi: New file.
89907 		* binutils/objdump.c: Add support for SFrame format.
89909 		* include/sframe-api.h: Add new API for dumping .sframe
89932 	entries in the .sframe section for those functions are also deleted.
89937 	This patch also adds support for generation of SFrame unwind
89938 	information for the .plt* sections on x86_64.  SFrame unwind info is
89939 	generated for IBT enabled PLT, lazy/non-lazy PLT.
89943 	will be generated for the linker generated sections like PLT.
89949 		* Makefile.def: Add install dependency on libsframe for libbfd.
89959 		(struct elf_link_hash_table): New member for encoded .sframe
89978 		.sframe section for .plt and .plt.sec.
89987 		(struct elf_x86_init_table): New members for .sframe
89992 		* ld/ld.texi: Update documentation for
90044 	The file include/sframe-api.h defines the user-facing APIs for decoding,
90098 	gas: testsuite: add new tests for SFrame unwind info
90101 	directives.  Splitting this out here for ease of applying and testing.
90138 	Currently supported for x86_64 and aarch64 only.
90148 	information.  These internal DWARF structures are read-only for the
90158 	that callee-saved registers other than FP are not needed for stack
90175 	necessary for generating SFrame unwind info:
90182 	generated for them.  Holes in instructions covered by FREs of a single
90185 	As few examples, following opcodes are not processed for .sframe
90194 	unwind information to be absent for SFrame FDEs that contain these CFI
90198 	functions for .sframe generation.  These provide gas with architecture
90202 	Lastly, the patch also implements an optimization for size, where
90208 	The optimization is on by default for both x86_64 and aarch64.
90250 		* gas/config/tc-xtensa.c (unrelaxed_frag_max_size): Add case for
90252 		* gas/doc/as.texi: Add .sframe to the documentation for
90271 		* gas/as.h: Introduce skeleton for --gsframe.
90272 		* gas/doc/as.texi: document --gsframe.
90280 	represent the minimal necessary unwind information required for
90291 	Re: [gas] arm: Add support for new unwinder directive ".pacspval".
90314 	incorrect thunk for the `configure' script.  This patch regenerates
90326 	for them with an autoconf macro resulting in an addition to LIBS.
90335 	  configure:28553: checking for ELF support in BFD
90360 	for a while, I am going to push it.
90371 	        * doc/c-i386.texi: Add znver4.
90432 	Currently for the target board remote-gdbserver-on-localhost we use the
90448 	[gdb/testsuite] Fix gdb.base/jit-elf-so.exp for remote target
90463 	[gdb/testsuite] Fix gdb.base/jit-reader-exec.exp for remote target
90476 	[gdb/testsuite] Fix gdb.base/info-shared.exp for remote target
90489 	[gdb/testsuite] Fix gdb.base/solib-vanish.exp for remote target
90502 	[gdb/testsuite] Fix gdb.base/infcall-exec.exp for remote target
90533 	[gdb/testsuite] Fix gdb.base/print-file-var.exp for remote target
90560 	number of test-cases fails with a remote target setup, for instance test-case
90566 	The problem is that the target board uses the same machine and user for
90605 	[gdb/testsuite] Fix gdb.base/info_sources_2.exp for remote target
90616 	[gdb/testsuite] Fix gdb.base/foll-exec.exp for remote target
90652 	The test-case checks for skip_gdbserver_tests and that one contains a check
90653 	for xml support:
90679 	Enable multi-process debugging for AIX
90693 	PowerPC, fix support for printing the function return value for non-trivial values.
90704 	to use the DW_OP_entry_value for the DWARF entries, when exiting the
90713 	zero by the new gdbarch method call for all architectures except PowerPC.
90776 	aarch64: Add support for Common Short Sequence Compression extension
90777 	This patch adds support for the CSSC extension and its corresponding
90783 	        * doc/c-aarch64.texi: Document new extension.
90798 		* aarch64-opc.c (operand_general_constraint_met_p): Update for new
90811 	converted from individual booleans to a single enum, as was done for a few
90814 	the criteria for folding).
90832 		Return 0 for pru.
90836 	[gas] arm: Add support for new unwinder directive ".pacspval".
90837 	This patch adds the assembler support for the new unwinder
90840 	vsp as modifier for PAC validation.
90846 	        * doc/c-arm.texi: Document directive.
90848 	        (md_pseudo_table): Add entry for pacspval directive.
90854 	[readelf] arm: Support for new pacbti unwind opcode 0xb5.
90855 	This patch adds readelf support for decoding the exception
90857 	as modifier for PAC validation as defined by EHABI
90900 	arm: Add support for Cortex-X1C CPU.
90901 	This patch adds support for Cortex-X1C CPU in Arm.
90915 	        * doc/c-arm.texi: Update docs.
90920 	[gdb/testsuite] Run gdb.arch/ppc64-symtab-cordic.exp for --enable-targets=all
90932 	Fix this by instead checking if powerpc:common64 is in the completion list for
90949 	would be a problem for something like:
91029 	for Cygwin (and looks like it shouldn't be, as appears to imply
91038 	Commit d08bae3d ("Implement target async for Windows") unconditionally
91054 	If the counter for LOOP instruction is provided by a register with
91078 	condition in extract_pcrel0 under which *invalid is set, but went for
91091 		for pla, paddi and psubi.
91095 	libctf: use libtool for link test in configure
91096 	The configure check for ELF support in BFD uses the AC_TRY_LINK.  If
91124 	use = for equality:
91138 	language_defn, that returns the right equality operator for the
91192 	Tested on x86_64-linux, using has_hw_wp_support for x86_64 in
91198 	The python code maintains a list of threads for each inferior.  This
91203 	We see this in ROCgdb[1], a downstream port of GDB for AMDGUP.  On
91223 	Except for the performance change, no user visible change is expected.
91241 	for it, and the situation is quite specific to the Arm target.
91251 	The problem is that writing to PC for the Arm target requires figuring
91259 	and, for safety, add an assertion to
91270 	gdb, btrace: Fix rn-dl-bind.exp for new icx remark.
91277 	The test doesn't seem to test something specifically for C++,
91286 	C++11, and Clang, for instance, does not feel the need to follow it.
91296 	for old gcc versions.  However, Clang does not fail in this test,
91305 	Since Clang chooses to not add any debug information for base types,
91317 	names to subprograms of those anonymous structs (for instance, the
91323 	specifications as DW_AT_name is optional for all DIEs, the test was marked
91327 	of the file explaining what it is testing for.
91333 	gdb/testsuite: allow for Clang style destructors on gdb.cp/m-static.exp
91359 	happens because Clang doesn't add accessibility information for typedefs
91361 	for more info). To help with Clang testing, an XFAIL was added to this
91368 	gdb/testsuite: account for clang's nested destructor calls on gdb.cp/mb-ctor.exp
91384 	another "continue" instruction is issued to account for this difference.
91392 	test fails to prepare with -Wnon-c-typedef-for-linkage like the
91406 …p/classes.exp: ptype class class_with_public_typedef // wrong access specifier for typedef: private
91432 	gdb/testsuite: ignore Non-C-typedefs for gdb.cp/class2.exp
91438 … non-C-compatible type given name for linkage purposes by typedef declaration; add a tag name here…
91445 …-gdb/gdb/testsuite/gdb.cp/class2.cc:58:3: note: type is given name 'Dbase' for linkage purposes by…
91449 … non-C-compatible type given name for linkage purposes by typedef declaration; add a tag name here…
91456 …-gdb/gdb/testsuite/gdb.cp/class2.cc:58:3: note: type is given name 'Dbase' for linkage purposes by…
91462 	This can be silenced by adding -Wno-non-c-typedef-for-linkage for Clang
91470 	While .linefile is generally intended for gas internal use only, its use
91476 	The need for IsString on the PadLock insns went away with the
91556 	Other arches use the .dc extension for the instruction decode table.
91559 	The parser for boolean rules fails to skip over the , separator in
91579 	memory operand for input/output port address in AT&T syntax and should
91581 	set i.input_output_operand to true for (%dx) and issue an error if (%dx)
91588 		(i386_att_operand): Set i.input_output_operand to true for
91592 		* testsuite/gas/i386/inval.s: Add tests for invalid (%dx) usage.
91647 	pspace-specific breakpoints (for example how the internal_breakpoint
91668 	to catch the bug, for instance if the scheduler decides not to schedule
91669 	inferior 1 for a long time, but it would be really rare.  If the bug is
91681 	GDB couldn't determine a compatible overload for a given function, but
91691 	  Downloading separate debug info for /lib/libxyz.so
91698 	  Downloading separate debug info for /lib/libxyz.so
91705 	  Downloading separate debug info for /lib/libxyz.so...
91710 	  Downloading 10.01 MB separate debug info for /lib/libxyz.so...
91714 	gdb: add special handling for frame level 0 in frame_info_ptr
91715 	I noticed this problem while preparing the initial submission for the
91737 	prepare_reinflate to force the computing of the frame id, for the same
91742 	special handling for frame 0:
91755 	for which frame_relative_level returns -1, so I have chosen the value -2
91756 	to represent "invalid frame level", for when the frame_info_ptr object
91760 	frame level is not 0.  It's fine to cache the frame id for the sentinel
91785 	technically, this change isn't needed.  But I don't think it's good for
91923 	do it here too for consistency.  I don't think it's absolutely necessary
91939 	compilers may not add complete information for given types as a way to
91959 	gdb/testsuite: allowed for function_range to deal with mangled functions
91962 	patch fixes this by allowing for mangled names along with the current
91985 	for the arelent pointer array, only to find a little later that the
91989 	We already do this for ELF targets, and while fixing the logic
92005 	be seen if the system does not have debug info for the libc:
92033 	Support for these files was dropped almost 30 years ago, but the ppc
92036 	sim: ppc: drop support for dgen -L option
92043 	statements for readonly or length fields whose values are also zero.
92070 	This saves a single line for the same result.  By itself, it's not
92113 	dynamic linker from function we do not have debug information for.  This
92184 	already has a mkdir module that provides this exact logic for us, so
92190 	Gdbserver unconditionally reports support for btrace packets.  Do not
92197 	Allow 'ptype/o' for assembly
92226 	never run.  We leave the rules in place for people who need to test
92247 		* objcopy.c (copy_archive): Don't call bfd_close for elements
92249 		Do the same for the archive itself.
92254 	Although the encoding for scalar and fp registers is identical,
92274 	ld: Always output local symbol for relocatable link
92277 		in SEC_EXCLUDE section for relocatable link.
92292 	nat/linux-osdata.c fails to properly fetch the core number for each
92372 	After that, we can for instance quit with confirmation:
92481 	[gdb/testsuite] Fix find_core_file for core named core
92523 	a log message for users at runtime instead of silent corruption.
92558 		* doc/c-i386.texi: Document .raoint.
92663 	- Makefile.in modified for EXEEXT = .exe.  It installs the binaries
92668 	- Cross build for aarch64-linux-gnu built to exercise
92680 	libstdc++, such as (wrapped for readability):
92716 	sim: .gdbinit: generate for all arch subdirs
92717 	This was being skipped for ports that had a recursive configure,
92718 	but we want it for them too.
92720 	sim: build: add a proper var for enabled arches
92734 	such a recent version this may imply that we disable ZSTD support for
92745 	OK for trunk?
92773 	there's no valid official ABI for RV32EF.  It means, even if we can assemble
92814 	immediately (though I did send a patch for that), instead let's
92815 	deprecate it in GDB 13 and then remove it for GDB 14.
92841 	common dir anyways, so might as well move linking now for a nice speedup.
92870 	We use uppercase for other variables, and are already turning it to
92874 	Nothing in the tree checks this option, or has checked for decades.
92896 	Update expected PR binutils/26160 test output for readelf out change
92923 	PowerPC update comments for the MMA instruction name changes.
92924 	The mnemonics for the pmxvf16ger*, pmxvf32ger*,pmxvf64ger*, pmxvi4ger8*,
92935 	    PowerPC: Add support for RFC02658 - MMA+ Outer-Product Instructions
92938 	            * config/tc-ppc.c (md_assemble): Only check for prefix opcodes.
92957 	gdb.reverse/ppc_record_test_isa_3_1.exp for backwards compatibility.
92963 	PowerPC fix for the gdb.arch/powerpc-power10.exp test.
92964 	The mnemonics for the pmxvf16ger*, pmxvf32ger*,pmxvf64ger*, pmxvi4ger8*,
92975 	    PowerPC: Add support for RFC02658 - MMA+ Outer-Product Instructions
92978 	            * config/tc-ppc.c (md_assemble): Only check for prefix opcodes.
93000 	for each binary value in the file gdb.arch/powerpc-power10.c is updated
93006 	Powerpc fix for gdb.base/unwind-on-each-insn.exp
93007 	The test disassembles function foo and searches for the line
93013 	 Dump of assembler code for function foo:
93062 	      opcodes/arm: add disassembler styling for arm
93088 	This is only needed for CGEN ports which RX isn't, so drop it.
93095 	automake now to do it all for us.  As a result, many of these vars
93100 	care of dependency tracking for us with the object files.
93104 	sim: don't hardcode -ldl for SDL support
93115 		* doc/c-i386.texi: Document .avx_ne_convert.
93149 	            * i386-opc.tbl: Rename <xy> template for VEX insn with x/y suffix to <Vxy>.
93150 		    Rename <xy> for EVEX insn with x/y suffix to <Exy>.
93166 		* bfd/elflink.c (_bfd_elf_default_action_discarded): Add checking for
93171 	gas/doc/internals.texi: fix typo
93172 		* gas/doc/internals.texi (md_emit_single_noop_insn):
93174 		* gas/doc/internals.texi (Hash tables):
93180 	We have configure tests for this in the top-level configure script
93182 	for specific ports.
93198 	sim: build: switch to libtool for linking
93199 	The top-level already sets up a libtool script for the host, so use
93231 	Let's switch to using / instead since it'll fail for a similar
93232 	reason (at least similar enough for what this test is testing).
93240 	This is used to allow for dangling \ in object lists, but these are the
93272 		* configure.tgt (ac_default_ld_warn_rwx_segments): Set to 0 for
93304 	macros/29034 was opened for GDB to keep track of this.
93306 	Seeing as there is no expected date for it to be fixed, add a workaround
93307 	for all current versions of Clang.  The workaround detects when
93312 	A test case was added to confirm the functionality, and the KFAIL for
93380 	sim: h8300: switch to cpu for state
93382 	for cpu state, pass down the active cpu that's already available.
93429 	RISC-V: Fixed the missing $x+arch when adding odd paddings for alignment.
93439 	Assembler adds $d for the odd .byte, and then adds $x+arch for the
93441 	$d and $x for the odd alignment, but accidently remove the $x+arch because
93455 	    for odd alignment, then we probably will remove the $x+arch by accidently
93475 		* doc/c-i386.texi: Document .msrlist.
93487 		(prefix_table): New entry for msrlist.
93505 	        * doc/c-i386.texi: Document .wrmsrns.
93517 		(rm_table): New entry for wrmsrns.
93529 	Add handler for more i386_cpu_flags
93545 		(build_modrm_byte): Add operations for Vex.VVVV reg
93547 		* doc/c-i386.texi: Document .cmpccxadd.
93585 		(i386_cpu_flags): Add cpucmpccxadd. Comment unused for it is actually 0.
93595 		* doc/c-i386.texi: Document avx_vnni_int8.
93640 	encoding for Intel IFMA instructions.
93646 		* doc/c-i386.texi: Document .avx_ifma.
93686 	      opcodes/arm: add disassembler styling for arm
93707 	      opcodes/arm: add disassembler styling for arm
93720 	the second argument is the one that is used for the switch table,
93722 	for this argument to take an invalid value.
93731 	opcodes/arm: add disassembler styling for arm
93732 	This commit adds disassembler styling for the ARM architecture.
93737 	The type for elements in each table can vary, but they all have one
93751 	the correct value for that instruction operand.
93755 	statement for operand handling.  As a result, every *_opcodes table
93756 	uses a different mapping for the operand escape sequences.  This means
93757 	that '%a' might print an address for one *_opcodes table, but in a
93762 	include comments within the assembler string, for example, also from
93790 	more than just a single operand being printed, for example, the '%q'
93794 	well as the text style for things like ',' between the different
93810 	   This simple state machine ensures that for simple instructions the
93811 	   basic parts, except for the operands themselves, will be printed in
93847 	    included a character for each style for completeness, though only
93855 	were two binutils tests for which I needed to force the disassembler
93866 	opcodes/arm: use '@' consistently for the comment character
93897 	libopcodes syntax styling support for ARM.
93935 	changed.  The number of hardware registers needed for a watchpoint can
93950 	gdb running on the binary for gdb.base/watchpoint.c.
93969 	are watched.  The val_chain contains the address for **global_ptr_ptr and 0
93989 	watched for the watchpoint **global_ptr_prt.  The list of addresses for the
93990 	breakpoint consist of the address for global_ptr_prt, global_ptr and buf.
94014 	call to setup each of the three address for breakpoint 4.  The slot
94015 	value returned for the third ptrace call is -1 indicating an error
94030 	PowerPC, add support for recording pipe2 system call.
94038 	This patch adds support for the missing pipe2 system call for PowerPC.
94047 	Earlier tidying still missed an opportunity: There's no need for the
94077 	gas/config/tc-i386.c:5039:16: error: too many arguments for format [-Werror=format-extra-args]
94086 	Use enum for gdbarch's call_dummy_location
94087 	This changes gdbarch to use an enum for call_dummy_location, providing
94112 …Updated Romainain translation for the binutils sub-directory and Swedish translations for the ld a…
94119 		* NEWS: Add support for Intel PREFETCHI instruction.
94121 		(md_assemble): Add warning for illegal input of PREFETCHI.
94122 		* doc/c-i386.texi: Document .prefetchi.
94167 	happens because Clang doesn't add accessibility information for typedefs
94169 	for more info). To help with Clang testing, an XFAIL was added to this
94182 		* doc/binutils.texi (objdump): Document the new option.
94203 	Pool section entries for DWP version 1
94311 	Likewise for target board remote-stdio-gdbserver.exp.
94379 	The usage for board remote-stdio-gdbserver.exp is advertised as:
94442 	objcopy copy_object may omit the call to bfd_copy_private_bfd_data for
94444 	will be NULL for the output file.
94468 	gas: NEWS: Note support for RISC-V Zawrs
94496 	RISC-V: Fallback for instructions longer than 64b
94505 		length up to 64-bit for now.  Make sure that required_bits does
94518 	RISC-V: Fix build failure for -Werror=maybe-uninitialized
94551 	We only consider the extended model field for family 0x6 and forget about
94559 	warning for a good reason.
94582 	    * elfxx-riscv.h (riscv_subset_list_t): Store arch_str for each subset list.
94592 	    generate $x+arch for MAP_INSN, and then store it into tc_segment_info_data
94594 	    (riscv_mapping_state): Decide if we need to add $x+arch for MAP_INSN.  For
94597 	    not add $x+arch for code alignment, since rvc for alignment can be judged
94620 	    * testsuite/gas/riscv/mapping-non-arch.s: New testcase for the case that
94627 	    for some specfic code region.
94639 	PowerPC: Add support for RFC02658 - MMA+ Outer-Product Instructions
94641 		* config/tc-ppc.c (md_assemble): Only check for prefix opcodes.
94658 	PowerPC: Add support for RFC02653 - Dense Math Facility
94753 	I found two silent timeouts responsible for this.
94779 	after which expect just waits for the timeout.
94808 	quit command to an mi interpreter, after which again expect just waits for the
94874 	RISC-V: Fix build failures for -Werror=sign-compare.
94882 	    failures for -Werror=sign-compare.
94890 	of the object laid out for the large section.  That means a large
94919 	thumb-plt and thumb-plt-got for nacl.  The first fails due to trying
94920 	to link against mixed-lib.so which isn't compiled for nacl.  The last
94931 		thumb-plt and thumb-plt-got for nacl.
94939 	gdb/testsuite: fix gdb.guile/scm-parameter.exp "wrong type argument" test pattern for Guile >= 2.2
95001 	So we should test for !exception_domain_is_secure instead of non-negated
95077 	therefore we do not know SP fixup for this frame.
95080 	To prevent problems terminate unwinding if PC contains the magic
95134 	The current logic limits itself to a maxdepth of 4 when looking for
95180 	for a "don't know" reloc.
95197 		* som.c (som_write_fixups): Allow for maximal som_reloc_skip.
95222 	("PR28824, relro security issues") we use max-page-size for relro
95234 	executables for a hello world (and even 6MB when linked with
95242 	for most x86-64 configs anyway, as most people won't configure with
95244 	"-z max-page-size" (with would have been required right now for a
95254 	This test fails quite reliably for me when ran as:
95275 	exp_continue, it's not really necessary.  And for consistency, do the
95285 	On openSUSE Tumbleweed I run into this for the dwarf assembly test-cases, and
95304 	$ for f in $(find gdb/testsuite/gdb.* -name *.S); do
95311 	Likewise for .s files, and gdb/testsuite/lib/my-syscalls.S.
95313 	The idiom for arm seems to be to use %progbits instead, see commit 9a5911c08be
95314 	("gdb/testsuite/gdb.dwarf2: Replace @ with % for ARM compatability"), so
95333 	ERROR: Timeout waiting for gdbserver response.
95364 	RISC-V: Should reset `again' flag for _bfd_riscv_relax_pc.
95366 	so we should reset 'again' flag to true for _bfd_riscv_relax_pc, while the
95376 	The riscv port does deletion and symbol table update for each relocation
95378 	for each relocation.  Compared to microblaze port, they record the relaxation
95385 	replace the unused relocation with R_RISCV_DELETE for the deleted bytes, and
95388 	should be O(m) for moving section bytes, and O(m*n^2) for symbol table update.
95391 	for updating symbol table, but it doesn't seem worth it for now.
95396 	    for memmove.
95399 	    or _riscv_relax_delete_immediate for deletion.
95403 	    (riscv_relax_resolve_delete_relocs): Delete the bytes for R_RISCV_DELETE
95407 	    (_bfd_riscv_relax_lui): Likewise, but reuse R_RISCV_HI20 for lui, and reuse
95408 	    R_RISCV_RELAX for c.lui.
95411 	    (_bfd_riscv_relax_pc): Likewise, but resue R_RISCV_PCREL_HI20 for auipc.
95415 	    (_bfd_riscv_relax_section): Set riscv_relax_delete_bytes for each relax_func,
95417 	    to delete bytes for DELETE relocations from a section.
95448 	With this done all the warnings when compiling lm32 are resolved for
95456 	to itself.  Clang gives a warning for this, which is converted into an
95474 	sim/ppc: fix for operator precedence warning from clang
95506 	call for the simulator, if the fstat is going to fail then we
95517 	successful call (except for the error code).
95585 		to skip for all targets without shared lib support.
95596 	Finally put in place similar tests for -mvexwig=1.
95609 	Finally put in place similar tests for -mvexwig=1.
95686 	iterations should be more than enough for when things are working.
95717 	gdb: check for empty offsets vector in inherit_abstract_dies
95777 	searching for methods, but by marking the type itself as a
95809 	packed arrays and a multi-dimensional packed array, and for the
95830 		(parse_args): Add support for -w and --no-warnings.
95833 		* ld.texi (options): Document new command line option.
95864 	available for unwinding, GDB defaults to the amd64 epilogue unwinder, to
95875 	This commit changes the frame_id calculation for the amd64 epilogue,
95886 	Updated Hungarian translation for the gprof sub-directory.
95891 	GDB/Python: Make `None' stand for `unlimited' in setting integer parameters
95892 	Similarly to booleans and following the fix for PR python/29217 make
95893 	`gdb.parameter' accept `None' for `unlimited' with parameters of the
95898 	for the special setting of `unlimited'.
95910 	verification for reading parameters via `<parameter>.value' in addition
95918 	Do not assert that a value intended for an integer parameter, of either
95958 		* NEWS: Add support for Intel AMX-FP16 instruction.
95960 		* doc/c-i386.texi: Document .amx_fp16.
96163 	a whole) have been disabled. This way the need for the PseudoVexPrefix
96178 	Enable debuginfod for this session? (y or [n]) y^M
96197 	The problem for both FAILs is that the output is parsed using
96207 	Re: aarch64-pe support for LD, GAS and BFD
96208 	Fix dependencies for eaarch64pe.c.  Generated files aren't handled
96216 	Second patch incorporates fixes for endian and UB issues in calc_hash, as per
96222 	See the remarks in rtld-step.exp for a description of what this
96240 	RUNTESTFLAGS="CC_FOR_TARGET=clang" on all of the above expect for
96252 	to be needed for FreeBSD (though since I never got it to work, I
96253 	don't know for sure.)  I've also left some declarations needed
96254 	for FreeBSD in rtld-step-rtld.c.  They're currently disabled via
96261 	At present, GDB does not allow for the debugging of the runtime loader
96285 	binutils/Makefile and it was intended for binutils/cxxfilt.man.  @PROGRAM@
96357 	Likewise for internal_warning.
96437 	      sim/ppc: fixes for arguments to printf style functions
96474 	Fix addr2line test for ppc64 elfv1 and mingw
96477 		symbol address for addr2line test.  Handle default executable
96555 	      aarch64-pe support for LD, GAS and BFD
96565 	aarch64-pe support for LD, GAS and BFD
96571 	Binutils: Adding new testcase for addr2line.
96595 	IBM zSystems: Issue error for *DBL relocs on misaligned symbols
96602 	gdb: check for groups with duplicate names in reggroups:add
96607 	To catch these, change the assert in reggroups::add to check for
96608 	duplicate names.  It's no longer necessary to check for duplicate
96639 	Update tests to use skip_hw_watchpoint_tests to test for HW watchpoint support.
96685 	test the changes.  The patch does not change the tests results for these
96695 	tentative fix for PR29697 I run into:
96713 	with a tentative fix for PR29697 I run into:
96716 	Cannot find thread-local storage for Thread 29613.29613, executable file \
96800 	    global symbols, which may result in xfers to read auxv for determining
96804 	    target to read AUXV in order to determine the debug base for SVR4
96809 	  - get_symbol_address() and get_msymbol_address() search objfiles for a
96816 	    be seen, for example, with gdb.base/dlmopen.exp when compiled with
96838 	for the special symbol "main".
96877 	When searching for standard exceptions for Ada, we lookup the minimal
96890 	namespace of gdb.current_objfile() for the search, which defaults to the
96954 	    Version number for this protocol.  It should be greater than 0.
96962 	    structure is for the default namespace.
96979 	namespace zero for a flat list of solibs from all namespaces.  Subsequent
96997 	Check for
97001 	and for
97011 	x86: generalize gas documentation for disabling of ISA extensions
97028 	kfail an Ada test for GCC < 12
97089 	This patch partially fixes the problem.  It arranges for Ada names to
97091 	linkage names for Ada are emitted, including the "main" name; names
97100 	The compiler will sometimes emit a linkage name for a type, like:
97147 	This is because clang 15 warns for something like this:
97155 	yynerrs is defined in yyparse and is there for actions to use.  Since
97189 	Allow explicit size specifier for predicate operand of {sq, uq, }{incp, decp}
97193 …This allows explicit size specifier, e.g. `decp z0.h, p0.h`, for predicate operand of these SVE in…
97202 		for decp, incp, sqdecp, sqincp, uqdecp and uqincp.
97211 		* testsuite/gas/aarch64/sve.s: Add sve testcase's instructions for
97236 	x86: properly decode EVEX.W for AVX512_4{FMAPS,VNNIW} insns
97237 	These require EVEX.W=0. Use %XS to facilitate the checking, even if for
97238 	the AVX512_4VNNIW ones this is kind of an abuse (as 's' there stands for
97241 	While there also correct the 3rd operand for the AVX512_4VNNIW entries:
97242 	Only the memory form is allowed (just like for AVX512_4FMAPS, where the
97249 	it do nothing for EVEX-encoded insns. This way the AVX-VNNI entries
97250 	can be re-used for AVX512-VNNI, at the same time fixing the lack of
97325 		SHF_COMPRESSED.  Set SEC_IN_MEMORY for compressed contents.
97423 	The problem is (as fixed for avr in commit df5b8876083 ("gdb/testsuite: better
97513 	We could try to make some generic way to set TERM on the host, but for the
97518 	so let's go with that for now.
97570 	machine subf instruction.  Do so for SPE evsubw and evsubiw too.
97590 	It has bothered me for a long time that we have disabled LSP (and SPE)
97595 	section with SHF_PPC_VLE for decoding when disassembling.
97600 	borne out by insn encoding, for example LSP "zvaddih" and SPE "evaddw"
97618 		* doc/binutils.texi: Update ppc docs.
97621 		* doc/c-ppc.texi: Document e200 and lsp.
97627 		PPC_OPCODE_LSP for e200z4 or vle.
97634 		* ppc-opc.c: Include libiberty.h for ARRAY_SIZE and use throughout.
97671 	flags list for the gdb_compile_shlib call.
97742 	current approach is to do the compilation hoping for the best, and if we find
97746 	That however does not work for hard-coded assembly nopie test-cases, which will
97815 	This commit adds such implications for existing privileged extensions that
97820 		* testsuite/gas/riscv/march-imply-h.d: New test, at least for 'H'.
97825 		implicications for privileged extensions 'H', 'Smstateen',
97876 	This commit takes care of improper spacing for code clarity.
97903 	RISC-V: Test DWARF register number for "fp"
97915 	for the disassembler, they may taint basic RVI instruction section.
97944 	gold has had --undefined-version for a long time.
97998 	("[gdb/testsuite] Fix 64-bit dwarf test-cases with -m32") for for instance
98023 	which is also true for target board unix/-m32 on x86_64-linux.
98063 	mismatch FAILs are generated for those.
98102 	there for SIMD registers.
98123 	There are two causes for this:
98124 	- the linker flags are missing --ctf-variables, so the information for variable
98189 	On openSUSE Tumbleweed (with ld 2.39) I get for test-case
98241 	sim/ppc: fixes for arguments to printf style functions
98246 	arguments being the wrong size, or type, for the printf format being
98349 	auxv data.  This gets cached for that inferior in `auxv_inferior_data`.
98353 	core, and for that asks the gdbarch to read a target description from
98359 	(empty) auxv data for that inferior, target_auxv_search searched that
98411 	 - Modify parse_auxv to accept a target_ops and gdbarch to use for
98420 	   current inferior.  The latter is for convenience, to avoid making
98429 	 - Same idea for arm_fbsd_read_description_auxv.
98468 		number for error reporting purposes.
98556 	__attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98568 	__attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98583 	__attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98595 	__attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98607 	__attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98619 	__attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98631 	__attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98637 	fix compressed_debug_section_names definition for "zlib"
98640 		* libbfd.c: Set COMPRESS_DEBUG_GABI_ZLIB for "zlib" value.
98708 	This commit adds support for INSN_CLASS_ZMMUL, and adds a test that
98724 	does not generate dirstamp file ($builddir/sim/moxie/.dirstamp) for it.
98727 	but fails because there's no rules for automake-generated dirstamp file
98730 	This commit adds its own rule for the directory stamp (modified copy of the
98758 	for which we get:
98766 	FAIL: capture_command_output for print 1
98772 	The second gdb_test_multiple then silently times out waiting for another prompt,
98786 	gprofng: no need to build version.texi
98792 		* doc/Makefile.am: No need to build version.texi.
98852 	the prompt, in which case the gdb_test used for "run &" won't match.  By
98865 	gdb_test_no_output for completeness.  Use it in
98880 	for the string concatenation "\0" "1", gdb will print "\000\061" --
98884 	for octal escapes, because there is a length limit of 3 for octal
98886 	this *is* needed for hex escapes, because those do not have a length
98919 	Andrew for the test case.
98941 	[gdb/testsuite] Fix error message for cmd with trailing newline
98975 	replaced with the base address for where the in-memory symbol file was
99033 	function calls.  I've added some basic debugging for what I think are
99058 	gdb/frame: Add reinflation method for frame_info_ptr
99059 	Currently, despite having a smart pointer for frame_infos, GDB may
99080 	As for performance concerns, my personal testing with `time make
99130 	this for a version of this series that I later abandoned; but since it
99193 	remote-stdio-gdbserver I have for gdb.server/connect-with-no-symbol-file.exp:
99226 	and because the regexp doesn't match, it triggers an implicit clause for
99254 	The regex for this test accounts for different situations (with /
99256 	backtrace shows execution under pthread_create.  However, for the
99283 	Then proc gdb_remote_download appends $xml_file (which for this particular
99305 	There's no need for such a warning, so remove it.
99409 	with FPCAR to identify if lazy FPU state preservation is active for
99411 	also ARM AN298, supported by Cortex-M4F architecture for details on
99412 	lazy FPU register stacking.  The same conditions are valid for other
99426 	the value of the D-registers for the SVC_handler frame and the
99429 	SVC_Handler frame, and the intermediate value (0x002..cee) for the
99430 	SysTick_Handler frame.  Now compare the D-register value for the
99439 	whether to issue the "cannot get low and high bounds for subprogram DIE at
99470 	const, and add a declaration for find_loc_num_by_location.
99498 	This commit fixes two minor typing-related issues for
99502 	2.  unsigned/signed int is not portable enough for max 32-bit immediates.
99603 	It didn't take long for the fuzzers to avoid size checks in
99648 	During symbol reading: cannot get low and high bounds for subprogram DIE \
99679 	During symbol reading: cannot get low and high bounds for subprogram DIE \
99681 	During symbol reading: cannot get low and high bounds for subprogram DIE \
99710 	gdb/riscv: Partial support for instructions up to 176-bit
99726 		* opcode/riscv.h (RISCV_MAX_INSN_LEN): Max instruction length for
99731 		* riscv-dis.c (print_insn_riscv): Increase buffer size for max
99736 	RISC-V: Renamed INSN_CLASS for floating point in integer extensions.
99737 	Just added suffix _INX for those INSN_CLASS should be enough to represent
99755 	[AArch64] Update FPSR/FPCR fields for FPU and SVE
99765 	Commit 2cac01e3ffff lacked support for objcopy changing compression
99788 	Enable zlib-gnu compression for .gnu.debuglto_.debug_*.  This differs
99789 	from zlib-gnu for .debug_* where the name is changed to .zdebug_*.
99798 		for zlib-gnu too.  Compress .gnu.linkonce.wi.*.
99848 	There's no need for such workarounds anymore now that we use C99
99854 	ignore DWARF debug information for -gsplit-dwarf with dwarf-5
99855 	Skip dwo_id for split dwarf.
99857 	* dwarf2.c (parse_comp_unit): Skip DWO_id for DW_UT_skeleton.
99865 	Fix self-move warning check for GCC 13+
99867 	but that warning is only checked for clang, resulting in:
99904 	we need to setup/account for the real registers first before going ahead and
99909 	This is in preparation to supporting pointer authentication for bare metal
99950 	This happens because searching for baseclasses only uses the macro
99952 	switch that macro to checking for typedefs, otherwise we wouldn't be
99953 	able to find the typedef'd name anymore. This is fixed by searching for
99955 	name after checking for typedefs.
99984 	RISC-V: Add testcase for DWARF register numbers
99985 	Although it had csr-dw-regnums.d (for CSRs), it didn't have DWARF register
99986 	number test for GPRs/FPRs.
99993 		for GPRs/FPRs.
100011 	The loop condition tests for "ret == EINTR" but waitpid signals EINTR by
100035 	  try "runtest --help" for option list
100072 	      tool           The tool (e.g. g++, libffi) for which to create a
100074 	                     is created for all tools.
100077 	                     variants in the files for <tool>.
100086 	      tool           The tool (e.g. g++, libffi) for which to create a
100088 	                     is created for all tools.
100091 	                     variants in the files for <tool>.
100125 	 just like we do for a parallel test run.  This makes the parallel and
100206 	for its comment character, however, gas and libopcodes use '#' as the
100207 	comment character, as gas uses ';' for an instruction separator.
100215 	than for comments, we can easily "fix" Pygments parsing of the
100217 	looks for an Error token with the value '#', we then change this into
100240 	I haven't included a test specifically for the above error case,
100247 	now if using Pygments for styling disassembly from every architecture
100267 	for styling all architectures, even if we know it might not be perfect
100274 	Pygments package for disassembly styling I noticed an issue in the
100280 	disassembly if, for some reason, the Pygments code isn't working.
100283 	disassembly styling using libopcodes, but this is only available for
100305 	      gdb: add support for disassembler styling using libopcodes
100323 	  Pygments for styling, and
100337 	gdb/testsuite: extend styling test for libopcodes styling
100397 	for the register name being nullptr in order to decide if a target
100399 	for the empty string.
100413 	I've added two new arguments for Functions and Methods (as declared in
100426 	gdb: check for duplicate register names in selftest
100428 	selftest to check for duplicate register names.
100436 	commit to check for duplicate register names, I didn't include this
100473 	now passes for all architectures.
100479 	never returns nullptr for any valid register number.
100492 	hit, for example, in alpha_register_name GDB checks for a register
100509 	for gdbarch_register_name.  Not every architecture is actually in
100543 	I noticed a test failure in gdb.base/completion.exp for RISC-V on
100549 	registers' and the completion list for 'info registers'.  The 'info
100556 	returns nullptr for some registers when it should return an empty
100591 	I added a self-test that, for each architecture, calls
100592 	gdbarch_register_name for every register number up to the
100600 	API for gdbarch_register_name is to return an empty string for
100616 	I noticed a test failure in gdb.base/completion.exp for RISC-V on a
100618 	reasons for the failure, this commit addresses one of them.  A later
100633 	The capture_command_output proc has some logic for skipping a prefix
100672 	gdb/mi: new options for -data-disassemble command
100673 	Now that the disassembler has two different strategies for laying out
100674 	the opcode bytes of an instruction (see /r vs /b for the disassemble
100675 	command), I wanted to add support for this to the MI disassemble
100703 	The two new options are only valid for mode 0, if they are used with
100728 	The argument documentation for -data-disassemble looks like this:
100738 	specification argument groups for the command, followed by a
100758 	uses for parenthesis: '( GROUP )*' and '( GROUP )+', in the first case
100789 	Here is an example for RISC-V before this patch:
100819 	It is still possible for a very long instruction to intrude into the
100824 	  Dump of assembler code for function main:
100836 	  Dump of assembler code for function main:
100845 	Most instructions are aligned, except for the very long instruction.
100846 	Notice too that for x86-64 libopcodes doesn't request that GDB group
100852 	equivalent, but for RISC-V, using /b gets the old layout back (except
100853 	that the whitespace for alignment is still present).  Consider our
100872 	always want to manually decode the instruction for some reason, and
100894 	then resized as needed, and filled with a single read_code call for
100901 	gdb/testsuite: new test for -data-disassemble opcodes format
100902 	Add another test for the output of MI command -data-disassemble.  The
100911 	The motivation for this test (besides more tests being generally good)
100950 	This commit adds certain test cases for 'Zfinx'/'Zdinx'/'Zqinx' extensions
100956 		* testsuite/gas/riscv/zfinx.s: Use different registers for
100958 		Add tests for instruction with rounding mode.  Change march
100970 	There is no need for casts to (signed/unsigned) long, as we can use
100975 	RISC-V: fallout from "re-arrange opcode table for consistent alias handling"
100979 	RISC-V: fix build after "Add support for arbitrary immediate encoding formats"
100982 	variable in the same function invocation. There's no need for the
100997 	RISC-V: re-arrange opcode table for consistent alias handling
101016 	newer). Note that now, for the opposite case to work (i386-tbl.h is
101018 	mentioning as a dependency somewhere: Add a fake dependency for
101035 	from ideal: The former results in "unsupported instruction" for 32-bit
101052 	possible need for the low byte/word opcode bit or an operand size prefix
101135 	just for toolchains (if full ISA string is given by a vendor, we can
101140 	only an architectural guarantee): 'Zkt' (constant timing guarantee for
101166 	for ppc64le"), the test-case fails with target board cc-with-debug-names, due
101178 	[gdb/c++] Print destructor the same for gcc and clang
101181 	With g++ (7.5.0) we have for "ptype A":
101237 	such that we have the same for both gcc and clang:
101246 	out-of-scope for this patch.
101335 		* gprof.texi (synopsis): Add -B.
101336 		(Output Options): Add entry for -B.
101345 	GDB fails to build for me, on Ubuntu 20.04.  I get:
101362 	configuring for is an ELF target.  GDB's configure thinks my system
101367 	 configure:17387: checking for ELF support in BFD
101412 		* doc/binutils.texi (size): Add -f.
101419 	Fix that by always manually forcing the warnings for it.
101429 	Multi-line patterns for grep are not supported on some old versions
101460 		* doc/as.texi: Document the --dump-config, --emulation,
101560 	zstd compressed debug sections for most tools.
101562 	* bfd: for addr2line, objdump --dwarf, gdb, etc
101565 	* objcopy: support ELFCOMPRESS_ZSTD input for
101572 	is too heavyweight, so don't do it for now.
101613 	wait for a timeout for the test to continue.  For instance, I currently
101633 	gdb/testsuite: bump duration for the whole test in do_self_tests
101643 	CUs.  selftest_setup does bump the timeout, but it's not for the whole
101647 	timeout for the whole duration of the setup and body.  On my optimized
101650 	build, so I think it's necessary to bump the timeout for that in any
101699 		back to relocs written.  Use better types for vars.
101729 	PKG_CHECK_MODULES for msgpack and jansson
101730 	Using AS_IF rather than shell "if" is recommended for conditionals
101774 	gdbserver: remove unused for loop
101783 	that the for loop after it was also unused.  After a period of smoke
101791 	elfcode.h can emit three warnings in elf_object_p for various things,
101794 	this is that the warning can be emitted for multiple possible targets
101802 	read_only, as is done for the "section extending past end of file"
101804 	warnings for object files in archives.  Besides that, it is just wrong
101813 	_bfd_check_format for the first element of the archive (to find the
101814 	correct target for the archive) will still be on the xvec at the point
101815 	that target is chosen for the archive.  However, target xvecs are
101816 	read-only.  Thus the need for per_xvec_warn to logically extend
101818 	than bfd_target_vector to provide one place for user code that makes
101825 		a new xvec.  Print warnings for the successful non-archive
101837 	Re: bfd_cleanup for object_p
101852 	entries to describe the location of the user stack for the initial
101861 	This patch adds support for the Zawrs ISA extension
101875 	The long name causes some particular redrawing that doesn't happen for
101891 	the last 2 failures for me.
101925 	"step", which makes the `wait_for` proc go in the "looking for the
101931 	then returns.  The state of the terminal is therefore correct for the
101966 	`wait_for` proc go in its "looking for the prompt" mode.  However,
101995 	The ideal way to fix this would be for `wait_for` to be smarter, to
102010 	test runs be more similar for everyone, such that there's less chance of
102011 	TUI tests randomly failing for somebody.  If some other change triggers
102027 	gdb/csky add cskyv2-linux.xml for cskyv2-linux.c
102028 	Add cskyv2-linux.xml for re-generating cskyv2-linux.c if needed.
102045 		(pdb_archive_p): Set up tdata for bfd_archive format.
102080 	  - GDB's replacement for default_target_compile assumes that the
102083 	In this situation, no one sets the C compiler for the board and as a
102098 	provide support for this language yet.
102126 	for the RISC-V toolchain conventions ([1]).
102134 	RISC-V: Add support for literal instruction arguments
102135 	This patch introduces support for arbitrary literal instruction
102138 	A typical use case for this feature would be an instruction that
102156 	for the RISC-V toolchain conventions ([1]).
102159 	(BU,HU,WU only for loads (zero-extend instead of sign-extend)):
102179 	in a PR for the RISC-V toolchain conventions ([1]).
102195 	in a PR for the RISC-V toolchain conventions ([1]).
102211 	in a PR for the RISC-V toolchain conventions ([1]).
102227 	in a PR for the RISC-V toolchain conventions ([1]).
102235 	RISC-V: Add support for arbitrary immediate encoding formats
102236 	This patch introduces support for arbitrary signed or unsigned immediate
102256 	for the RISC-V toolchain conventions ([1]).
102272 	for the RISC-V toolchain conventions ([1]).
102284 	displacement, therefore we have a different syntax for the arguments.
102286 	for Zicbom-style arguments in x-thead-cmo-fail.s.
102298 	RISC-V: Add generic support for vendor extensions
102311 	* Add test cases for all instructions
102312 	* Add MATCH*/MASK* constants and DECLARE_INSN() for all instructions
102418 	might cause confusion, for example, we allow '$' in window names,
102444 	explicit test for walking through the epilogue so we can safely remove
102490 	would not be easy to test for this behavior using steps and analzing
102527 	When using clang as the compiler for the target, gdb.base/jit-elf.exp
102534 	       Reading symbols from .gnu_debugdata for /lib64/libm.so.6...
102535 	       (No debugging symbols found in .gnu_debugdata for /lib64/libm.so.6)
102550 	       Reading symbols from .gnu_debugdata for /lib64/libm.so.6...
102551 	       (No debugging symbols found in .gnu_debugdata for /lib64/libm.so.6)
102562 	relative path, but seeing as testing the full path is not important for
102564 	positive, the regexp for checking where gdb has stopped was relaxed a
102585 	the test expects.  This approach does not work for the parts that use
102619 	difference is important for the testsuite, since the where GDB will land
102627 	ld/testsuite: allow to force another directory for gcc linker
102678 		     and a vendor may use this symbol for special purposes.
102684 	On such cases, we should vacate this room for the new operand type with
102732 	make -j bug, where the recipe for targmatch.h was being run twice in
102773 	Rename it fileio_error_to_host, for symmetry with host_to_fileio_error.
102782 	should contain a target fileio error number, for instance in
102788 	assign a value for which there is no enumerator.  I considered
102926 		elf_dynverref for empty sections.
102948 	PR29573, addr2line doesn't display file/line for local symbols
102951 	even though the language mangles names.  g++ does not for local
102956 	1) A demangler might not be available for the compiler/language.
102986 	non_mangled incorrectly returned "true" for Ada.  Correct that, and
102987 	add a few more non-mangled entries.  Return a value suitable for
103001 	problem of relocatable object files with the fix for PR2338, so this
103019 	To avoid invalid invocation of preprocessor for build environment, we
103031 	This patch support ZTSO extension. It will turn on the tso flag for elf_flags
103057 	RISC-V: Always generate R_RISCV_CALL_PLT reloc for call in assembler.
103058 	Since we have the same behaviors of CALL and CALL_PLT relocs in linker for now,
103064 	Therefore, we should always generate R_RISCV_CALL_PLT reloc for call, even if
103069 		* config/tc-riscv.c (riscv_ip): Always generate CALL_PLT reloc for
103094 	The direct cause for the looping was failing to test for error return
103097 	that for all subsequent calls.  (The object format has one set of
103098 	relocation records for all sections.)  If the first call fails, all
103126 	allows for the removal of some initialization code.
103140 	We currently have a single test for GDB's debuginfod support, this is
103151 	One change I made, for example, is the library offers functions to
103156 	code, and this test is still passing for me.  The only change in the
103171 	Stop strip from complaining about empty note sections when stripping a binary for a second time.
103175 	New Serbian translations for various binutils sub-directories.
103186 	.rela.* sections those would be merged into .rela.dyn, so the slot for
103204 	LoongArch: Don't write into GOT for local ifunc
103212 	So stop writing into GOT for local ifunc now.
103290 	hook for suppressing output of all but the first identical messages.
103292 	See the comment at the beginning of bfd-errors.exp for details about
103295 	I've tested this test for both 32- and 64-bit ELF files and also
103296 	on both little endian and big endian machines.  It also works for
103298 	it only works for ELF targets.
103303 	This commit adds a hook to the BFD error handler for suppressing
103333 	its utility.  Also, the BFD message printer has support for BFD-
103335 	in its map are sufficient for distinguishing messages from each
103385 	[gdb/testsuite] Fix gdb.dwarf2/dw2-dir-file-name.exp for aarch64
103413 	In contrast, for x86_64-linux, we have the breakpoint printed with instruction
103438 	  for the address compdir_missing__ldir_missing__file_basename_label, making
103466 	- gdb goes to wait for the next event
103467 	- expect times out waiting for "Quit", the expected reaction for ^C
103471 	The fix is only available for readline 8.x, if --with-system-readline provides
103594 		regexps to allow for output genreated by the Clang compiler.
103599 	mach-o.c doesn't sanity check mach-o-fat archives, making it easy for
103678 		* testsuite/ld-ctf/diag-wrong-magic-number.s: Likewise.
103706 	<UNPREDICTABLE> for S > 10.
103714 		* elf64-ppc.c (allocate_dynrelocs): Don't alloc space for relocs
103716 		(ppc64_elf_size_dynamic_sections): Use standard test for discarded
103718 		* elf32-ppc.c (allocate_dynrelocs): Don't alloc space for relocs
103720 		(ppc_elf_size_dynamic_sections): Use standard test for discarded
103729 	objdump: '-S' should trigger search for separate debuginfo.
103732 	'objdump -S' download missing files via debuginfod without the need for
103778 	explicitly test for stderr in gdb.base/dprintf.exp
103780 	program. Clang, for instance, prefers to add nothing from standard
103807 	The reason for implementing this interface is that we want to print
103823 	gdb/csky add unwinder for long branch cases
103824 	There are two sequences of instructions for long branch:
103843 	for csky_target::low_arch_setup(). later, it can be used for csky native gdb.
103845 	2. In gdb/features/cskyv2-linux.c file, create target_tdesc for csky, include
103895 	I went through all the uses of dynamic_cast<> in gdb, looking for ones
103902 	The -mfuture and -Mfuture options which are used for adding potential
103907 		* doc/binutils.texi: Document -Mfuture.
103911 		* doc/c-ppc.texi: Likewise.
103971 	fix gdb.base/access-mem-running.exp for clang testing
103977 	stops, however it was still testing for a specific location.  The clang
103978 	compiler emits different line information for epilogue, so GDB reports a
104007 	constant for the incremental growth of the array.
104009 	Use bool instead of int for boolean values.
104017 	Generally use unsigned integers for all array indices and sizes.
104032 	checking for duplicates when inserting new entries.
104034 	This is done in the same way as is done for exports and imports
104036 	based on the implementation for aligncomm).
104108 	[gdb/testsuite] Fix gdb.dwarf2/dw2-dir-file-name.exp for ppc64le
104120 	Setting a breakpoint on *$func effectively creates a breakpoint for the global
104148 	to cause problem with clang, as documented in the comment for proc
104157 	x86: avoid i386_dis_printf()'s staging area for a fair part of output
104160 	for typically far more than half of the overall output results in a 2-3%
104184 	error for them.  Perhaps we also need the similar checks for the
104195 	Besides, we also have similar changes for libgcc,
104196 	RISC-V: jal cannot refer to a default visibility symbol for shared object
104204 		of the cases here, so don't need the unresolvable check later for
104237 	that's only active for ada:
104244 	- marking the type as a stub for all languages, and
104283 	accessible for every vector subsets), current minimum vector subset 'Zve32x'
104285 	(fixed point arithmetic only) CSRs mandatory for such subsets.
104371 	[gdb/testsuite] xfail gdb.ada/O2_float_param.exp for aarch64 and gcc 7.5.0
104382 	expression for function entry values" (
104385 	Xfail the test for aarch64 and gcc 7.
104393 	[gdb/testsuite] Fix gdb.ada/access_tagged_param.exp for aarch64
104475 	Fix endianness handling for arm record self tests
104535 	Looking at the debug info for glibc for symbol __GI_munmap:
104546 	that's probably caused by this bit (or similar bits for other munmap aliases).
104549 	tag to DWARF DIEs generated for function symbols").
104551 	Work around this (for say gas 2.39) by explicitly specifying the prototype for
104554 	Likewise for getpid in a couple of other test-cases.
104573 	Add debuginfod support for objdump -S
104587 	the addition of a parameter for specifying the filename of a supplementary
104591 	support for ELF/DWARF2 .gnu_debugaltlink. For other targets this
104609 	There is a portable mechanism for disassembler options and used on some
104624 	Valid values for [ENUM_VALUE] must be predefined in
104625 	disasm_option_arg_t.values. For instance, for -M cpu=[CPU] in ARC
104638 		* gdb/disasm.c (set_disassembler_options): Add support for
104682 	Add test-case gdb.dwarf2/debug-names-bad-cu-index.exp, a regression test for
104707 	There is a portable mechanism for disassembler options and used on some
104722 	Valid values for [ENUM_VALUE] must be predefined in
104723 	disasm_option_arg_t.values. For instance, for -M cpu=[CPU] in ARC
104772 	      sim: fixes for libopcodes styled disassembler
104835 	xtensa: bfd: fix TLS relocations generated for PIE
104838 	in generation of wrong relocations for TLS entries. Fix that and add
104858 	objdump output for l32r opcode was changed in commit b3ea76397a07
104868 		* testsuite/ld-xtensa/tlsbin.dd: Adjust expected output for l32r
104871 		for named section symbols.
104872 		* testsuite/ld-xtensa/tlspic.dd: Adjust expected output for l32r
104875 		for named section symbols.
104887 	address space is used for I/O registers and corresponding symbols are defined.
104893 		* testsuite/gas/riscv/dis-addr-topaddr.s: New test for the top
104897 		* testsuite/gas/riscv/dis-addr-topaddr-gp.s: New test for
104917 	for JALR instruction (the initial bug is back in 2018).  This commit also
104984 	integer representation it corresponds to for integer parameters.
104992 	    checking for python... no
104993 	    checking for python3... /usr/bin/python3
104994 …e distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check P…
104998 …e distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check P…
105002 …e distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check P…
105006 	    checking for python... yes
105015 	python 3.2.  Given that support for python < 3.2 has been removed by
105017 	need to support both implementations for backward compatibility.
105035 	gdb_setup_readline doesn't check for the case where instream==nullptr.
105070 	tui_out_new is just a simple wrapper for 'new' and can be removed,
105087 	Remove the "for moment" comments
105088 	A few spots setting some gdb output stream variables have a "for
105103 	seem useful, even for documentation purposes.
105107 	not be registered with the event loop.  This is useful for the DAP
105113 	gdb/riscv: better support for fflags and frm registers
105123 	CSRs.  These CSRs are aliases for the relevant parts of the fcsr
105124 	register.  So fflags is an alias for bits 0 to 4 of fcsr, and frm is
105125 	an alias for bits 5 to 7 of fcsr.
105139 	for reading and writing floating point state only contains a copy of
105143 	So, we might expect that the target description for the RISC-V native
105149 	include an entry for fcsr, fflags, and frm.  This means that GDB
105155 	handled, this means that, for RISC-V native Linux, the fflags and frm
105170 	unreasonable to me, and so I had GDB check for these registers in
105178 	FreeBSD), and the target descriptions created for RISC-V native Linux,
105181 	the code in riscv-tdep.c continues to check for all three of these
105212 	in the next commit, I'm splitting it out into a separate patch for
105279 	not wrapped in the i18n markers for internationalisation, so I added
105292 	defined for all 8 values.  That GDB masks to 2-bits is just a bug I
105295 	Finally, the 'FRM' text for value 0x7 is wrong.  Currently we use the
105296 	text 'dynamic rounding mode' for value 0x7.  However, this is not
105303 	So, for the rounding-mode field of an _instruction_ the value 0x7
105307 	But it makes no sense for the FRM of $fcsr to itself be set to
105314 	And so, I propose changing the text for value 0x7 of the FRM field to
105316 	"INVALID[5]" and "INVALID[6]" for the two other invalid fields,
105321 	prints for the three registers related to this patch.  There is one
105322 	slight oddity with this test - for the fflags and frm registers, the
105333 	this check for <unavailable>.
105342 	gdb, dwarf: create symbols for template tags without names
105363 	So the DW_AT_name attribute for DW_TAG_template_type_parameter and
105367 	presence of a DW_AT_name for the DIE (an exception here is the case of
105370 	This patch makes the presence of the DW_AT_name for template value/type
105385 	names there is one for clang/icpx.  Consider the following example
105398 	The forward declaration for 'Foo' with the missing template type names
105424 	Befor this patch, GDB would not create any symbols for the read template
105450 	been added in the gdb.dwarf2 for template classes and structs.
105457 	When writing a dwarf testcase for some C++ code I wanted to use the
105464 	The reason for this is that in read.c::dwarf2_compute_name we call
105492 	  Dump of assembler code for function main(int, char**):
105499 	  Dump of assembler code for function _Z3fooif:
105506 	Note, that main is emitted with its arguments while for foo the linkage
105526 	  Dump of assembler code for function main:
105533 	  Dump of assembler code for function foo:
105540 	Note, for foo we did not get a linkage name emitted in DWARF, so
105581 	criteria for being considered a Microsoft import library was that
105582 	every archive member had the same name (no regard for exactly what
105586 	(in 2003) to allow for Microsoft import libraries with intermixed
105593 	members for linking against more than one DLL (built by merging
105598 	for doing the member renaming: If an archive member is named *.dll
105602 	This works for imports for any number of DLLs in the same library,
105618 …/home/simark/src/binutils-gdb/gdb/../gdbsupport/parallel-for.h:142:21: error: 'result_of<(lambda a…
105641 	for C++ >= 17 and std::result_of otherwise.  This way, it will be easy
105652 	Fix flush for sys.stderr
105656 	way to write a test for this.
105691 	Add a testcase for PR 29494.
105724 		(riscv_multi_subset_supports): Add handling for new instruction class.
105830 	support for S+core") removed support for the architecture.
105885 	c++11 && _GLIBCXX_DEBUG"), but for gdb::optional.
105977 	  >See 'help print' for more information.
105983 	  See 'help print' for more information.
105992 	of the aliased command.  In particular for cases such as pp10 example above,
106001 …cpustate.c:270:1: error: conflicting types for 'aarch64_get_CPSR_bits' due to enum/integer mismatc…
106014 	On x86, the PLT entry in executable may be used as function address for
106021 	On Solaris, linker issued an error for
106039 	GAS: Add a return type tag to DWARF DIEs generated for function symbols.
106045 		abbreviation numbers.  Generate an abbreviation for an unspecified
106049 		Reference the use when generating DIEs for functions.
106050 		* testsuite/gas/elf/dwarf-3-func.d: Update to allow for newly
106067 	gas: NEWS: Add the RISC-V features for 2.39
106069 	gas: NEWS: Add the RISC-V features for 2.38
106071 	gas: NEWS: Add the RISC-V features for 2.37
106073 	gas: NEWS: Add the RISC-V features for 2.36
106075 	gas: NEWS: Add the RISC-V features for 2.35
106077 	gas: NEWS: Add the RISC-V features for 2.31
106088 		for unaligned reloc target values.  Return bfd_reloc_overflow
106127 	Also make the check for .def consistent with the other ones, fixing
106135 	multiple statements.  This patch fixes the issue for all the cases
106145 	is slightly more helpful anyway.  Similar errors are generated for
106158 	to find the frame-id for a specific frame.
106183 	I don't think it makes any sense for a SHT_RELR section to specify a
106185 	There is no real need to specify sh_info either, SHT_RELR is not for
106215 		* doc/binutils.texi: Document the new options.
106230 	Implement target async for Windows
106231 	This implements target async for Windows.  The basic idea is to have
106242 	Windows to wait for a debug event in addition to other events.
106243 	Therefore, in order to implement target async for Windows, gdb will
106267 		* readelf.c (check_magic_number): New function.  Checks the magic
106269 		magic values, then attempts to generate a helpful error message.
106322 	symbols for bfd_simple_get_relocated_section_contents
106332 	except for symbols like "_gp".  So it mostly doesn't matter whether
106351 	Re: Missing linking test case for pe dll using a def file
106392 	for the amd64 binary, although this one was already position-independent
106404 	gdb, testsuite: Adapt gdb.base/callfuncs.exp for new clang warning.
106405 	Clang 15.0.0 enabled the warning for deprecated non-prototype functions
106415 	Removing the test for deprecated syntax would also be an option. But I will
106416 	leave that up for others to decide/implement.
106420 	gdb, testsuite: Enable testcases that suppress specific warnings, for icc/icx.
106430 	This patch adds the same option that already exists for clang for icx and
106449 	Like commit a9c09a3667cc, but for loongarch64.
106465 		* libcollector/collector.c: Add #if defined(GPROFNG_JAVA_PROFILING) for
106511 	I tried writing a test for this using the DWARF assembler, but I haven't
106521 	from the reproducer given in the bug (thanks to Pedro for suggestions on
106523 	and aarch64, I added versions of the test for these two architectures.
106538 	Doing some archaeology, it seems handling for adr/adrp in prologues was
106556 	Add test for AArch64 Scalable Vector Extension
106603 	This happens because the code that searches for a new gdbarch to match the
106612 	Missing linking test case for pe dll using a def file.
106642 	phase, a timer is then created for the given timeout in order to re-use
106657 	Emitting this warning for every insn, including ones having actual
106674 	GDB/testsuite: Fix PARAM_ZUINTEGER reported for PARAM_ZUINTEGER_UNLIMITED
106700 		(mmo_decide_section): Check for NULL return from mmo_make_section.
106725 	bfd: Define ___lc_codepage_func prototype for older MinGW-w64
106729 	Prior to version 9.0 of MinGW-w64, the function prototype for
106743 	bytes.  Define MAX_OPERAND_BUFFER_SIZE for operand buffer size and
106775 	The reason for this mismatch was that the assembler code that is
106785 	and making use of preprocessor macros to specialise the file for the
106809 	However, it missed updating this test case, which still tests for the
106870 	Many of the vector conversion insns come with X/Y/Z suffixed forms, for
106875 	To facilitate using a uniform name for both AVX and AVX512, further
106901 	The AVX2 gather ones are nicely grouped - do the same for the various
106916 	  what we already have for KMOVQ - the diagnostic is better this way for
106940 	  necessary for VMOVSD, and necessary for VMOVSS as long as we permit
106976 	gdb/csky add unwinder for sigtramp frame when kernel 4.x and later
107003 	about how we check for the fcsr, fflags, and frm registers within a
107039 	      [bfd] Ensure unique printable names for bfd archs
107053 	location_spec_to_sals is only ever called for code breakpoints, so
107084 	width is shown.  %#010x is not a good replacement for 0x%08x.
107090 	configure support for deciding the flavour of HOST_WIDEST_INT.
107214 	needed anymore for floating varobjs.
107216 	This commit proposes to remove this recreation process for floating
107254 	This patch makes sure that, as we do for breakpoints, we wait until
107312 	operands. Obviously zero is not supported for these operands. Whilst
107315 	not allowed. This patch adds a new flag, PPC_OPERAND_NONZERO, for this
107321 	This patch adds support for LibreSOC machine and SVP64 extension flag
107322 	for PowerPC architecture. SV (Simple-V) is a strict RISC-paradigm
107323 	Scalable Vector Extension for the Power ISA. SVP64 is the 64-bit
107335 	exception frames for m-profile targets.
107339 	it's an invalid state for the unwinder.
107360 	stashes the extra input for the next call.  That call never came
107377 		* input-scrub.c (input_scrub_include_sb): Add extra space for
107428 	   to use the fixed output for this without using the newer MI version.
107449 	The 256 extended-color support for --disassembler-color was broken.
107485 	This patch disables the year 2038 check for now, which makes things work
107488 	I'd consider this a temporary fix until we have proper bfd checks for the year
107502 	time, in order to skip emitting any data for the function if the value
107517 	be stubs for other local symbols so don't look for them.  The patch
107519 	only for ppc64 and a couple only for ppc32.
107525 		look for stubs when the symbol is an ifunc.
107527 		handling for relocs not valid for both 32-bit and 64-bit.
107531 	bfd: Add support for LoongArch64 EFI (efi-*-loongarch64).
107532 	This adds support for efi-loongarch64 by virtue of adding a new PEI target
107540 	However this target is not valid for use with gas but only with objcopy.
107542 	We should't limit addresses to 32-bits for 64-bit vma, otherwise there will be
107547 	Any magic number is based on the Microsoft PE specification [1].
107642 	value as a float, and then convert the value to an integer for
107686 	uint8 to make it easier for users to view the fcc register groups.
107714 		* doc/binutils.texi: Update description of disassmbler-color
107722 	Fix-for-multiple-thread-detection-in-AIX.
107723 	In AIX multiple threads were not added. This patch is a fix for the same
107796 	operand size" error when a size-less memory operand is specified for an
107797 	insn where register use alone isn't sufficient for disambiguation.
107838 	add splay tree for info_ptr -> CU mapping
107839 	While using perf top for MozillaThunderbird I noticed quite some slow
107853 	where linked list of CU is iterated when searing for where info_ptr
107856 	         : 3452   for (u = unit->prev_unit; u != NULL; u = u->prev_unit)
107865 	         : 3452   for (u = unit->prev_unit; u != NULL; u = u->prev_unit)
107883 		for a info_ptr.
107889 	dwarf: use find_abstract_instance for vars and DW_AT_specification
107941 		(scan_unit_for_symbols): Call find_abstract_instance for
107942 		DW_AT_specification for variables that can be in a different CU
107964 	gdb/csky support .reg2 for kernel 4.x and later
107978 	In addition, for fr0~fr15, each FRx is the lower 64 bits of the
108036 	Likewise for the case where the CU table is not sorted by increasing offset.
108042 	[gdb/testsuite] Add support for .debug_names in dwarf assembler
108044 	- support for a per-module .debug_names section in the dwarf assembler, and
108047 	A per-module .debug_names section needs to have an entry in the CU list for
108055 	- disabling the dummy CU generation for the test-case.
108093 	for a symbol error.  If the symbol name is the last string in its
108124 	error: shift exponent 299 is too large for 32-bit type 'int'.  We'll
108132 		don't set alignment_power for stupidly large alignments.
108210 	[gdb] Add unit test for gdb::sequential_for_each
108212 	drop-in replacement for gdb::parallel_for_each, but there's nothing making
108215 	Extend the unit test for gdb::parallel_for_each to test both.
108236 	$ for n in $(seq 1 10); do \
108273 	Parallel for: n_elements: 2818
108274 	Parallel for: minimum elements per thread: 1
108275 	Parallel for: elts_per_thread: 704
108276 	Parallel for: elements on worker thread 0       : 705
108277 	Parallel for: elements on worker thread 1       : 705
108278 	Parallel for: elements on worker thread 2       : 704
108279 	Parallel for: elements on worker thread 3       : 0
108280 	Parallel for: elements on main thread           : 704
108284 	Parallel for: n_elements: 2818
108285 	Parallel for: total_size: 1483674865
108286 	Parallel for: size_per_thread: 370918716
108287 	Parallel for: elements on worker thread 0       : 752   (size: 371811790)
108288 	Parallel for: elements on worker thread 1       : 360   (size: 371509370)
108289 	Parallel for: elements on worker thread 2       : 1130  (size: 372681710)
108290 	Parallel for: elements on worker thread 3       : 0     (size: 0)
108291 	Parallel for: elements on main thread           : 576   (size: 367671995)
108355 	for buffer overflow checks in the linker's generated .dynamic
108387 	compression type for ZSTD.") added the new ELF compression type but it
108388 	accidentally broke a GAS testcase.  Since testing for the section type
108439 	Add gold support for --package-metadata option.
108458 		* configure.ac: Check for jansson library.
108473 	Recognize the new ELF compression type for ZSTD.
108479 		* binutils/readelf.c (process_section_headers): Add support for
108509 	Use new and delete for gdbarch
108513 	This changes gdbarch to use bool for initialized_p.
108543 	That particular situation is handled for arm:
108552 	but not for any other targets so wpnum remains "", triggering the ERROR.
108554 	Possibly this has been fixed for powerpc by commit 8d4e4d13afb ("gdb Power 9
108555 	add test for HW watchpoint support."), but it's still possible for other
108572 	[gdb/tdep] Fix gdb.base/large-frame.exp for aarch64
108596 	- fixing the support for the first insn to extract the immediate operand, and
108597 	- adding support for the second insn,
108615 	known about this for a long time, but patches slip through review.
108618 	PRIu64, PRIx64 or PRIo64 and SCN variants for scanf.  The patch is
108627 	particularly for 32-bit builds where a number of tests using map files
108631 	to print 32-bit vmas for 32-bit targets.  So change %V back to be
108639 		* ldmisc.c (vfinfo): Use bfd_sprintf_vma for %V.  Tidy %W case.
108654 	MIPS: Use R_MIPS_REL16 for BFD_RELOC_16
108666 	elf: Reset alignment for each PT_LOAD segment
108667 	Reset alignment for each PT_LOAD segment to avoid using alignment from
108674 		alignment for each PT_LOAD segment.
108688 	that the condition for deleting the object is not the same as the
108814 	x86: also use D for MOVBE
108816 	has also been used for KMOV* and BNDMOV. Then simplify the condition
108817 	selecting which form if "reversing" to use - except for the MOV to/from
108839 	comments and callers were all updated for this change, but the actual
108888 	-- Updating tests for new relaxation criteria
108919 	and inspected for the difference accordingly.
108933 	arm: Add cfi expression support for ra_auth_code
108934 	This patch extends assembler support for the use of register names to
108935 	allow for pseudo-registers, e.g. ra_auth_code register.
108936 	This is done particularly with CFI directives in mind, allowing for
108950 	arm: Use DWARF numbering convention for pseudo-register representation
108957 	The mechanism for splitting the register list is also re-written to
109020 	ld: Add support for a new option, -exclude-symbols, in COFF object file directives
109082 	means that the output for 32-bit targets may be either 8 or 16 hex
109103 		* elf32-xtensa.c (print_r_reloc): Similarly for fprintf_vma.
109179 	choosing one of "l", "ll", or "I64" for BFD_VMA_FMT, and results in
109182 	Write a direct configure test for the printf int64_t style instead.
109263 	It's not clear why for ada we're using long long for the
109266 	Fix this by using unsigned long long for the fits-in-unsigned-long-long case,
109275 	gdb/testsuite: add macros test for source files compiled in various ways
109293 	will be tested no matter what the current target compiler is for a given
109302 	the new procs is based on what was done for rnglists and loclists.
109304 	To test against a specific compiler one can use this command, for
109319 	The thread for the patch that introduced this code is:
109357 	think it's preferable for these hacks to be located in the specific
109435 	find the appropriate macro scope for the symtab, and we can't print
109447 	"start_subfile" for the main subfile will correctly find the
109457 	get things wrong.  So in my search for a fix, it is important that given
109458 	some good debug info, we don't end up relying on that for things to
109471 	resulted in user-visible changes (for example, paths to source files in
109483 	for finding objects from the names used for presentation.  This field is
109484 	used for identifying subfiles, symtabs and macro_source_files
109486 	"most complete possible" path, as discussed above.  So for a given file,
109488 	symtab::filename field remains the one used for printing to the user, so
109498 	 - Make buildsym_compunit::start_subfile use "name_for_id" for looking
109499 	   up existing subfiles.  This is the key thing for making calls
109500 	   to start_subfile for the main source file look up the existing
109515 	   possible" name for the main symtab's "filename_for_id".  In this
109519 	 - Change dwarf2_start_subfile to build a name_for_id for the subfile
109523 	   representation as the macro code does, for the same file (since it
109547 	As we can see, there are two forms used for "test.c", one with a "." and
109554 	without a ".", and the line table for that file contains:
109565 	For instance, gcc uses "./test.c" for the DW_AT_name, which gives
109586 	dwarf_decode_lines that creates a symtab for each file entry in the line
109676 	start a subfile with the same filename_for_id, and there was no need for
109716 	that will already have access to the file_entry object for which they
109718 	only for line_header::file_file_name to re-lookup the same file_entry
109742 	header needs to know about the compilation directory.  Prepare for that
109744 	value down everywhere needed.  Add a second constructor for the special
109745 	case of building a line_header for doing a hash table lookup, since that
109810 	libopcodes/aarch64: add support for disassembler styling
109811 	This commit enables disassembler styling for AArch64.  After this
109819 	The entry point for the AArch64 disassembler can be found in
109826 	However, for most "normal" instructions, the instruction operands are
109844 	used for the i386 disassembler.
109856 	which mode should be used for each piece of text.  Back in
109879 	I've used the source files in gas/testsuite/gas/aarch64/ for testing,
109898 	It's possible for relax_delete_bytes to be called with section
109926 	for such arises, quite likely the only way to address this would be to
109946 	assembler instead of trying to hack around this for every target.
109999 	This commit adds `OP_V' (OP-V: vector instruction opcode for now
110050 	The old "free" callbacks took a parameter for the enclosing container
110091 	This patch was needed for the subsequent patch to rewrite the registry
110102 	Added nullchecks for Python object creations.
110115 	wrapped in a ref_ptr that handles that for us in blocpy_dealloc.
110126 	output of the MI-command "-break-list".  Added documentation for these attributes.
110131 	Refactored some code to use more c++-y style range for loops
110152 	for instance;
110158 	object requires it to be alive for as long as it is alive.
110160 	Thanks for your review, Tom!
110173 	query breakpoints for their installed locations,
110183 	The attribute for retrieving the currently installed breakpoint
110184 	locations for gdb.Breakpoint. Matches behavior of
110206 	like for instance when a new symbol file is loaded, at
110259 	gprofng: check for the makeinfo version
110264 		* configure.ac: Check for the makeinfo version.
110274 	Unfortunately, this interface is not implemented for writing in older
110291 	would not "bother for one word," but the effect is the essentially
110345 	(1) Put an introductory comment to explain the purpose for some functions.
110359 		* configure.tgt (ac_default_ld_warn_rwx_segments): Disable for
110478 	Updated translations for various sub-directories
110542 	for backward compatibility.
110551 	objfile's obstack.  It is possible for this objfile to be deleted (and
110562 	for example).
110575 	  used for similar purpose when replacing types of values kept in the
110608 	mi_make_breakpoint_pending proc for pending breakpoints.
110648 		generation of html for the disassembly where instructions
110682 	At present, GDB only checks for the existence of this environment
110696 	This commit also corrects the set/show command documentation for
110698 	of that for set/show python ignore-environment.
110701 	asked that the help text that I proposed for "set/show python
110740 	  Dump of assembler code for function main:
110744 …b/gdb/disasm.h:144:12: runtime error: load of value 118, which is not a valid value for type 'bool'
110752 	value for m_in_comment in disasm.h.  As we only ever disassemble a
110792 	packed that uses a gdb_byte array for internal representation, needed
110793 	for mingw+clang.  While adding that, I wrote some unit tests to make
110848 	files for the GDB sub-directories (gdb, gdbsupport, and gdbserver)[1],
110864 	you don't get spammed for errors on context lines that you haven't
110880 	extensions and for other Cortex-M targets, there are 2 different
110889 	As the register numbers for the alternative Arm SP registers are not
110914 	add GDB support for this style.  Fix this oversight in this commit.
110918 	libopcodes/ppc: add support for disassembler styling
110929 	are styled.  As best I can tell, this construct, used for example in
110954 	When adding libopcodes disassembler styling support for AArch64, it
110975 	LoongArch: Add testcases for new relocate types.
111038 	  dynamic relocation for R_LARCH_32_PCREL.
111040 	  Add New relocate type R_LARCH_32_PCREL for .eh_frame.
111095 	bfd: Add supported for LoongArch new relocations.
111116 	to cater for user silliness.
111120 	out at a higher address.  That's due to the address expression for
111122 	creates a bfd section) for .got before the .plt section is created.
111125 	and does cope with a missing bfd section by returning zero for its
111129 		* ldlang.c (exp_init_os): Don't create a bfd section for SIZEOF.
111162 	addition to the internal ones.  Note that there is still room for
111190 	.debug_types section (which is what you'd expect for dwarf 4).
111216 	names for each pass.
111231 	[gdb] Add empty range unit test for gdb::parallel_for_each
111240 	sbrk hasn't been used in binutils/ or ld/ for quite some time (so the
111245 		* configure.ac: Don't check for sbrk.
111250 		* configure.ac: Don't check for sbrk.
111256 	gdb/csky modify registers list for general_reggroup
111297 	i386: Don't allow GOTOFF relocation against IFUNC symbol for PIC
111298 	We can't use the PLT entry as the function address for PIC since the PIC
111299 	register may not be set up properly for indirect call.
111305 		relocation against IFUNC symbol for PIC.
111343 	in some cases, be used as a drop-in replacement for static_cast.  And
111374 	I built GDB for all targets on a x86-64/GNU-Linux system, and
111399 	target_ops::fetch_registers, which, for the x86-64 native target,
111418 	don't think that the correct solution for this problem is to detect,
111457 	gdb: select suitable thread for gdbarch_adjust_breakpoint_address
111473 	In these cases it is possible, and valid, for a user to have one
111496 	  is for when a local watch expression is created, which can only be
111550 	Consider building GDB for all targets on x86-64/GNU-Linux, then doing
111618 	are used as the callbacks for two set/show parameters.  These set/show
111621 	so, if I build GDB for all targets on an x86-64/GNU-Linux system, I
111724 	It's hard to produce a test-case for this, but let's try at least to trigger
111739 	Now override ull in dw2_debug_names_iterator::next for the DW_IDX_compile_unit
111760 	A somewhat similar issue for .gdb_index in dw2_symtab_iter_next has been filed
111776 	operand sizes for AVX512 scatter/gather") giving all AVX512F scatter
111778 	utilizing that there previously were two identical lines each (for no
111843 		for process_abbrev_set.  Return free_list if newly alloc'd.
111890 	support for older versions of Python, i.e. those before Python 3.8.
111900 	We could try to use the PyConfig API for Python versions as early as 3.8,
111903 	distributions should have support for Python 3.10.  This should be
111904 	more than adequate for testing the new Python initialization code in
111924 	deprecated in Python 3.12, it makes sense to disable their use for
111925 	gdb builds against 3.10 and higher since those are the versions for
111927 	includes different mechanisms for making the same settings afforded
111930 	Simon also noted that PyConfig_Clear() would not have be called for
111933 	PyConfig_Clear() will always be called, both for success and failure.
111938 	commit also initializes a struct for each module to import.  Both the
111970 	 Argument N means step N times (or till program stops for another reason).
111973 	doesn't re-resume them for the subsequent N-1 steps.  It's as if for
112035 	thread's thread_fsm::should_stop, which as we've seen, for the first
112036 	step returns false -- i.e., we need to keep_going for another step.
112082 	Since glibc 2.36 will issue warnings for copy relocation against
112088 		* elf32-i386.c (elf_i386_scan_relocs): Remove check for
112091 		(elf_x86_64_relocate_section): Remove check for
112093 		* elfxx-x86.c (elf_x86_allocate_dynrelocs): Check for building
112097 		* elfxx-x86.h (SYMBOL_NO_COPYRELOC): Remove check for
112102 		* testsuite/ld-i386/i386.exp: Expect linker error for PR ld/17709
112109 		* testsuite/ld-x86-64/x86-64.exp: Expect linker error for PR
112110 		ld/17709 test.  Add tests for function pointer against protected
112115 	x86: Make protected symbols local for -shared
112117 	2 noticeable effects for -shared:
112159 	Teach GDB how to dump memory tags for AArch64 when using the gcore command
112166 	own PT_AARCH64_MEMTAG_MTE segment. A section named ".memtag" is created for each
112197 	There is another patch for GDB that enables both reading
112208 	for that fact in the MTE testcases (gdb.arch/aarch64-mte.exp) and define
112275 	This patch adds a gdb.free_objfile event registry and arranges for an
112315 	Remove array typedef assumption for Ada
112317 	multi-dimensional array and an array of arrays by looking for an
112318 	intervening typedef -- that is, for an array of arrays, there will be
112357 		created_styled_output for ARC based targets.
112391 	gdb/python: look for python, then python 3 at configure time
112400 	Currently, when GDB configures, it looks for a 'python' executable.
112404 	This commit updates GDB's configure.ac script to first look for
112421 	encoded for the store form (which would again cause #UD).
112437 	Parallel for: n_elements: 7271
112438 	Parallel for: minimum elements per thread: 10
112439 	Parallel for: elts_per_thread: 1817
112440 	Parallel for: elements on worker thread 0       : 1817
112441 	Parallel for: elements on worker thread 1       : 1817
112442 	Parallel for: elements on worker thread 2       : 1817
112443 	Parallel for: elements on worker thread 3       : 0
112444 	Parallel for: elements on main thread           : 1820
112452 	That doesn't seem to matter much for this example, but for say 10 threads and
112459 	Parallel for: elements on worker thread 0       : 1818
112460 	Parallel for: elements on worker thread 1       : 1818
112461 	Parallel for: elements on worker thread 2       : 1818
112462 	Parallel for: elements on worker thread 3       : 0
112463 	Parallel for: elements on main thread           : 1817
112471 	Use set_sanitizer_default for ASAN_OPTIONS in lib/gdb.exp.
112498 	Fix this by only adding -fcf-protection=none for gcc 8 and later.
112510 	(gdb) FAIL: gdb.arch/i386-mpx.exp: verify size for bnd0
112529 	Parallel for: n_elements: 7271
112530 	Parallel for: minimum elements per thread: 10
112531 	Parallel for: elts_per_thread: 1817
112532 	Parallel for: elements on worker thread 0       : 1817
112533 	Parallel for: elements on worker thread 1       : 1817
112534 	Parallel for: elements on worker thread 2       : 1817
112535 	Parallel for: elements on worker thread 3       : 0
112536 	Parallel for: elements on main thread           : 1820
112576 	for an internal error being triggered as a PASS.
112587 	PowerPC: Add support for IEEE 128-bit format.
112603 	128-bit type support for PowerPC.
112630 	PR python/17291 asks for access to the current print options.  While I
112639 	particular the temporary ones in effect for just a single "print").
112646 	PowerPC: fix for gdb.base/eh_return.exp
112647 	Disable the Traceback Table generation on PowerPC for this test.  The
112651 	for every function by default.  The Traceback Table is defined in the
112691 	for the cooked index finalization to be done.
112712 	gdb: Document floating-point support for LoongArch
112714 	for LoongArch.
112730 	/usr/include/c++/4.8/atomic:208:13: error: no matching function for call to \
112736 	Fix this by adding the default constructor for packed.
112826 	Allows register names to appear in symbol assignments, so for example
112855 	Tighten gdb.threads/no-unwaited-for-left.exp regexps
112860 	 (gdb) PASS: gdb.threads/no-unwaited-for-left.exp: enable scheduler-locking, for main thread
112864 	 No unwaited-for children left.
112865 	 (gdb) PASS: gdb.threads/no-unwaited-for-left.exp: continue stops when the main thread exits
112868 …3    Thread 1251861.1251863 "no-unwaited-for" __pthread_clockjoin_ex (threadid=140737351558976, th…
112869 	   4    Thread 1251861.1251861 "no-unwaited-for" <unavailable> in ?? ()
112872 	 (gdb) PASS: gdb.threads/no-unwaited-for-left.exp: only thread 3 left, main thread terminated
112875 	"No unwaited-for children left.".  The "only thread 3 left, main
112886 	Fix for gdb.base/stap-probe.c
112893 	Where the source code for stap-probe.c is:
112901 	expected.  The #define for ATTRIBUTE_NOCLONE can be found in
112904 	This patch adds the missing include statement for the definition of
112912 	This patch adds the needed define ASM_REG for PowerPC.
112914 	The patch was run on a Power 10 system.  The gdb Summary for the run lists
112917 	Please let me know if this patch is acceptable for mainline.
112924 	Due to recent changes in the default value of -fcf-protection for gcc, the
112943 	to be "-fcf-protection=none" for the test to compile on Intel.
112946 	an error on other platforms.  A check for X86 is added so the test will
113067 	Fix this by not setting m_lang for partial units.
113100 	partial symtabs phase to the symtab expansion phase, for the benefit of a
113123 	Add missing support for recording of linux syscall getrandom.
113132 	This commit adds floating-point support for LoongArch gdbserver.
113135 	This commit adds floating-point support for LoongArch gdb.
113183 	Fix -fsanitize=thread for per_cu fields
113229 	Likewise for the write to addresses_seen in cooked_indexer::check_bounds and a
113230 	read from is_dwz in dwarf2_find_containing_comp_unit for test-case
113246 	during the parallel cooked index reading.  The same holds for
113247 	unit_type, and likewise for addresses_seen.
113251 	bitfields that currently precede it, for better packing.
113389 	Fix that.  Note that it is arguably wrong for ld to leave the output
113411 	gdb regs s0~s127 (pseudo regs for float and vector regs)
113434 	notification for threads.
113452 	centralize emitting thread exit notifications for the CLI, which is
113457 	notifications when tearing down an inferior, for most targets.
113460 	even for exit_inferior_silent.
113508 	   for (inferior *inf : all_non_exited_inferiors ())
113555 	Try a couple PAuth compilation flags for gdb.arch/aarch64-pauth.exp
113563 	gdb: add support for disassembler styling using libopcodes
113586 	need to do this.  But, this could be useful for testing, or, in some
113587 	rare cases, a user might want to override the Python hook used for
113593 	When libopcodes is being used for styling then the user can make use
113608 	these are aliases for:
113613 	respectively, and exist to make it easier for users to discover
113628 	the setting defaults to "on" for architectures that support libopcodes
113645 	now the setting is "off" for everyone, even if the user switches back
113653 	attempting to switch the setting "on" for an unsupported architecture
113701 	previously, for this class, the stream was nullptr.  With the change
113703 	are needed for gdb_non_printing_disassembler.
113755 	For now, allow for that exception.
113782 	Fix include guard naming for arch/aarch64-mte-linux.h
113855 		* as.h: Reorder hash.h after symbols.h for notes_calloc decl.
113872 		notes obstack for string hash table entries.
113906 	for arc, but a later patch will move all the string hash memory to the
113909 		* config/tc-i386.c (md_begin): Use notes_alloc for core_optab.
113920 		(ppc_setup_opcodes): Use insn_obstack for ppc_hash.
113944 	Currently md_end is typically used for some final actions rather than
113984 	So that the notes obstack can be used for persistent storage in
114017 	Use notes obstack for dwcfi_hash entries, and free table.  Freeing the
114032 	read.c assign_symbol: use notes obstack for dummy listing frag
114033 		* read.c (assign_symbol): Use notes_calloc for dummy_frag.
114035 	read.c s_include: use notes obstack for path
114036 		* read.c (s_include): Use notes obstack for path mem.
114040 	macro.c: use string hash from hash.h for macro_hash
114062 	read.c: use string hash from hash.h for po_hash
114063 	po_hash code duplicates the str_hash code in hash.h for no good reason.
114097 	Makes it a little easier to use the notes obstack for persistent
114112 	arm gas is only supposed to warn once per symbol for -mwarn-syms, but
114115 	NULL value for the key,value pair.  Let str_hash_insert do the job
114230 	functions for per_cu->lang/unit_type").
114251 	IWBN to have this working in all use cases, but for now, allow lang () and
114332 	libopcodes/s390: add support for disassembler styling
114353 	Add markers for 2.39 branch
114361 	gprofng: fix regression in testing for not yet installed version
114435 	At this point, waitpid has returned an "exited" status for some pid, so
114439 	wait for, waitpid then returns -1 so we get here:
114455 	for an inferior that exists.
114522 	... still passes cleanly for me after this change.
114526 	signed forms for DW_AT_decl_file/DW_AT_decl_line.
114530 	before/after fix for gdb.trace/unavailable-dwarf-piece.exp with that
114564 	GDB/testsuite: Add coverage for `print -elements' command
114565 	We currently have no coverage for the `print -elements ...' command (or
114626 		(riscv_multi_subset_supports):  Rewrite handling for new
114659 		* riscv-opc.c (riscv_opcodes): Change instruction classes for
114709 		for proper testing.
114725 	This patch enables the first support for the "gprofng display html" command.
114726 	This command works for C/C++ applications on x86_64. Using one or more gprofng
114734 		* gp-display-html/gp-display-html.in: implement first support for x86_64 and C/C++
114738 	elf: Copy p_align of PT_GNU_STACK for stack alignment
114752 		for stack alignment.
114756 	x86: make D attribute usable for XOP and FMA4 insns
114764 	Note that the .s suffix isn't being enabled to have any effect, for
114767 	anyway, regardless of order. Hence there is (as before) no way for the
114768 	programmer to request the alternative encoding to be used for register-
114773 	used for register-only insns. This has the slightly odd (but pre-
114802 	Descriptive DWARF operations dump support for DW_AT_rank
114807 	x86: introduce a state stack for .arch
114814 	For now require the same .code<N> to be in effect for ".arch pop" that
114815 	was in effect for the corresponding ".arch push".
114825 	disabling of all of them. Then we also have all data for a sub-arch in
114833 	Note that for Intel MCU "default" is merely an alias of "iamcu".
114901 	The basic support for LoongArch has been merged into the upstream Linux
114907 	cycle for merging LoongArch port into the upstream Linux kernel, so
114911 	To build upstream GDB for a kernel lacking orig_a0, it's necessary to
114918 	Support for location and range lists for split-dwarf and dwarf-5.
114919 	Adding support for location and range lists for split-dwarf and dwarf-5.
114921 	1. Display of the index values for DW_FORM_loclistx and DW_FORM_rnglistx.
114925 	        and DW_FORM_rnglistx for .dwo files.
114988 	memory.  However I thought it worth providing support for allocating
115004 	Modified changes for split-dwarf and dwarf-5.
115008 	        (load_separate_debug_files): Skip DWO ID dump for dwarf-5.
115014 		created_styled_output for AVR based targets.
115022 	[gdb/symtab] Add get/set functions for per_cu->lang/unit_type
115028 	Add get/set member functions for the two fields as a convenient location to
115045 	is in place for a memory operand (i.e. particularly excluding
115054 	template at the same time as Disp32. Unlike for non-64-bit mode,
115055 	templates don't specify displacements for both possible addressing
115064 	i386_finalize_displacement() entirely dead for AT&T mode, since for
115084 	relocation addends emitted for such branches. Correct both problems,
115123 	Both writes are called from the parallel for in dwarf2_build_psymtabs_hard,
115128 	    #3 operator() gdbsupport/parallel-for.h:163 (gdb+0x872380)^M
115142 	    #7 operator() gdbsupport/parallel-for.h:171 (gdb+0x8723e2)^M
115161 	say returning true for "per_cu.version () < 5" if "per_cu.version () == 0".
115175 	warning: Found custom handler for signal 7 (Bus error) preinstalled.^M
115176 	warning: Found custom handler for signal 8 (Floating point exception) \
115178 	warning: Found custom handler for signal 11 (Segmentation fault) \
115279 	Add `NUMBER' then as an available completion for such `set' commands:
115342 	[ I have not been able to reproduce this after it occurred for the first time,
115352 	In passing I noticed that the column headings for the table of MI
115357 	columns, this prevents the headers overlapping for me.
115430 	With errors given for bad commands such as `set annotate' or `set width'
115459 	The function aarch64_print_operand (aarch64-opc.c) is responsible for
115464 	though this (currently) only happens for the last operand of the
115468 	for AArch64, this will allow objdump and GDB[1] to syntax highlight
115473 	second buffer.  Any comments for the instruction are written into this
115507 	  ERROR: no fileid for gcc2-power8
115549 	we call skip_hw_watchpoint_tests for the first time on powerpc, GDB
115614 	stopped for a breakpoint, and since when going through the shell, no
115616 	only record the stop pc when the thread stopped for a breakpoint.
115680 …Fix the display of the idnex values for DW_FORM_loclistx and DW_FORM_rnglistx.  Correct the displa…
115685 		displayed for DW_FORM_loclistx and DW_FORM_rnglistx.
115692 	When the compiler doesn't properly arrange for foo's alignment, there's
115703 		* elf64-ppc.c (ppc_size_one_stub): Align plt_branch stubs as for
115706 		* testsuite/ld-powerpc/elfv2exe.d: Adjust for plt_branch changes.
115723 	It made sense before I started using separate fields for main type and
115732 	gdb:csky add pseudo regs for float and vector regs
115746 	use them for the dwarf registers.
115755 	used. This part is to prepare for the expansion of vector registers to 32
115758 	part is to prepare for the expansion of the vector register to 32.
115778 		* config/tc-riscv.c (enum riscv_csr_class): Add CSR classes for
115779 		'Sstc' extension. (riscv_csr_address): Add handling for new CSR
115811 		* config/tc-riscv.c (enum riscv_csr_class): Add CSR classes for
115812 		'Sscofpmf' extension. (riscv_csr_address): Add handling for new
115852 		* config/tc-riscv.c (enum riscv_csr_class): Add CSR classes for
115853 		'Smstateen' extension. (riscv_csr_address): Add handling for
115881 	handled for cleanliness.
115886 		handling for H.  Change handling on RV32.
115890 	Re: Disable execstack and rwx segments warnings for MIPS targets.
115930 	special requirements for both the host libiberty and host zlib, which has the
115989 	for me, of which 8 are GDBserver core dumps, 7 more than without this
116055 	TypeError: unsupported operand type(s) for %: 'bytes' and 'str'
116071 	[gdb/testsuite] Fix gdb.reverse/i387-env-reverse.exp for -pie
116072 	When running test-case gdb.reverse/i387-env-reverse.exp for x86_64-linux with
116089 	[gdb/testsuite] Enable some test-cases for x86_64 -m32
116090 	When trying to run test-case gdb.reverse/i387-env-reverse.exp for x86_64-linux
116131 	[gdb/testsuite] Skip gdb.fortran/namelist.exp for gfortran 4.8
116136 	Skip the test for gfortran 4.8 and earlier.  Do this using gcc_major_version,
116186 	Note that this happens to give the right answer for 32-bit dwarf and
116190 	Conversely, for 32-bit dwarf and addr_size == 4 (target board unix/-m32)
116192 	instead we get the wrong strings, like "func2" for DW_AT_producer and
116193 	"build/gdb/testsuite" for DW_AT_name of the DW_TAG_compile_unit DIE.
116197 	Add a FIXME that we should not parse this for every call.
116238 		* configure.ac: Build libiberty pic variant for gdbserver.
116243 	Disable execstack and rwx segments warnings for MIPS targets.
116246 		* configure.tgt: ... to here.  Add similar code for MIPS.
116247 		Move code for CRIS, MIPS and HPPA to block at start of file.
116288 	sections from the end of the relro segment.  So for example, a change
116355 	Similar to commit 4fb55bf6a9606eb7b626c30a9f4e71d6c2d4fbb2 for aarch64.
116388 	Detecting and compensating for this problem would probably be
116421 	exact duplicates, except for the downcast:
116435 	Since interp_ui_out() is a virtual method that also works for the CLI
116439 	too.  With that, the CLI observers will work for the TUI interpreter
116468 	there is now no longer any need for any test script to call
116485 	Having a new proc specifically for this task means that we have a
116486 	single consistent pattern for detecting gcc.  By wrapping this logic
116513 	being shoved somewhere by abrt, apport, or similar (as you should for
116572 	Above, we see a couple cores for "connect-with-no", which are the
116602 	changed, at least on development builds, but that would be for another
116630 	But that would only work for serial testing, as in parallel testing,
116640 	script approach for parallel testing, but that has the obvious
116642 	end, I settled on the script approach for serial mode too, which
116656 	After a testrun, I noticed that I have some kernel-produced cores for
116685 	them to delete the core file.  However, that isn't working for me,
116686 	because said code only looks for cores named exactly either "core" or
116690 	gdb.base/bigcore.exp, for a similar reason.  I get:
116794 	aarch64: Allow PC-relative relocations against protected STT_FUNC for -shared
116829 	Use std::string for interpreter_p
116849 	If an executable has copy relocations for extern protected data, that
116864 	PIE with copy reloc" which started to use direct access relocations for
116869 	copy relocations.  So for aarch64 we simply don't check
116874 	Binutils support for split-dwarf and dwarf-5
116880 		debug_information, do it for do_debug_info also, if its true.
116887 	This patch has been pending for almost a year...  However, I noticed that
116890 	but at least we can do this for the multi-letter extensions in binutils.
116897 	    tp reorder the prefixed extensions for now.
116920 	    (riscv_multi_subset_supports): Handle INSN_CLASS_H for hypervisor instructions.
116923 	    * config/tc-riscv.c (riscv_csr_class): Added CSR_CLASS_H and CSR_CLASS_H_32 for
116927 	    controlled by single h extension for now.
116952 	but discussion for software compatibility is made).
116956 		* elfxx-riscv.c (riscv_ext_canonical_order): Add 'H' for
116961 	RISC-V: Prepare i18n for required ISA extensions
116964 	This commit wraps such strings with the gettext macro (_) for
117062 	(discarding all but the last, but then looking for types in the earlier
117072 	ctf_link_in_out, which (for input dicts) points to the associated per-CU
117073 	output dict (if any), and for output dicts points to the associated
117111 		name for a new per-CU dict.
117130 		library, and expected results for the test.
117134 	Document how GDB searches for files when using -s, -e, and -se options
117140 	    for a program to run.
117142 	The same is true for files specified via commandline options -s, -e,
117145 	This commit adds a cross reference to the file command for these options.
117149 	Binutils support for dwarf-5 (location and range lists related)
117160 		* configure.ac (ac_default_ld_warn_execstack): Default to 'no' for
117165 		option to the command line when running execstack tests for the
117206 	copy_type only works for objfile-owned types, but there isn't a deep
117207 	reason for this.  This patch fixes the bug by updating copy_type to
117208 	work for any sort of type.
117217 	Fix the sorting algorithm for reloc entries
117256 	gdb/doc: Documentation for the new print command
117268 	group.  The motivation for this work is to enhance the readability of
117300 	Thanks Tom Tromey for your correction [1], sorry for that.
117312 	mix of allocation strategies it isn't possible for callers to free
117317 	the name is dup'd for no good reason as far as I know.
117352 	Fix this by not using aggregate initialization for struct line_offset.
117438 	Some constructors that are used for cloning location_specs, like:
117454 	Currently, GDB internally uses the term "location" for both the
117456 	an address location), and for actual resolved locations, like the
117476 	  /* The base class for all an event locations used to set a stop event
117482 	and even that is incorrect...  Location specs are used for finding
117520 	and likewise for all the other mpx tests.
117624 	While at it fixed format string for time-related types.
117628 	Check for listeners in emit_exiting_event
117642 	gdb/arm: Make sp alias for one of the other stack pointers
117653 	aliases for one of the 4 real stack pointer registers.
117663 	Same goes for "psp".
117719 	Further, I noticed that some architectures, for example, ARM, require
117723 	And so, if we ever use gdb_buffered_insn_length for ARM, then GDB will
117730 	gdb_buffered_insn_length.  As I run the test for all architectures, I
117731 	do indeed see GDB crash for ARM.
117758 	The motivation for this commit was to provide an API by which the user
117805 	  as a disassembler, either for one specific architecture, or, as a
117806 	  global disassembler for all architectures.
117834 	This commit is setup for the next commit.
117837 	calls within GDB, each print_insn call is responsible for
117839 	will be possible for a user to write Python code that either wraps
117846 	for a print_insn hook.  There's a new callback added to 'struct
117847 	extension_language_ops', which is then filled in with nullptr for Python
117862 	The motivation for this change is an upcoming Python disassembler API
117867 	for my new class to inherit from gdb_disassembler.
117891 	dis_asm_fprintf functionality for printing.
117905 	The reason for adding the additional layer to the class hierarchy is
117919 	removes the need for manual reference count management, and allows the
117928 	counts, so this is good preparation for that upcoming change.
117938 	[gdb/build] Fix build for gcc < 11
117959 	The problem is that the warning -Wstringop-overread has been introduced for
117979 		(read_indexed_string): Use uint64_t for str_offset.  Sanity check idx.
117980 		(read_attribute_value): Clear u.str for indexed string forms when
117987 	on hppa produces a spurious warning for stringop-overread in
117988 	debuginfod_is_enabled for url_view. Just always suppress it on all
118004 	gprofng docs: provide help for <rate> == <interval>
118008 	info, including reasons for caution.
118061 	Implement lazy FPU initialization for ravenscar
118067 	indicating whether the FPU has been initialized for this task.
118075 	for ARM as well, but GDB doesn't yet have an arm-ravenscar-thread.c.
118080 	Currently, the ravenscar-thread implementation for each architecture
118093 	file for this runtime had the wrong offsets in comments, which GDB
118094 	took to be correct.  However, those comments didn't account for
118107 	but there's no good reason for this.  This patch removes the error.
118239 	Debug support for global alias variable
118255 	MIPS should not be using BFD_RELOC_16 for its R_MIPS_16 relocation,
118262 	md_apply_fix for cases where the fixup can be applied at assembly
118298 		and "end" after checking for missing section.
118308 	in order to ensure gas state is saner for oss-fuzz.
118357 	[gdb] Avoid warnings in cooked_{read,write}_test for m68hc11
118373 	Likewise for regcache::cooked_write_test.
118387 	so look for the end of the sequence and put the breakpoint there.
118394 	checking for X... no
118404 	gdb:csky add support target-descriptions for CSKY arch
118407 	2. 16 ars (alternative gprs used for quick interrupt)
118482 	for callers to pass in a style).
118498 	By changing the values used for "artificial" prefix values,
118536 	arrange for no such declaration to be needed in the first place.
118551 	needed now.  It was introduced in ancient times as an optimization for
118555 	Use malloc for mutable addrmaps
118564 	addrmap::create_fixed is just a simple wrapper for 'new', so remove it
118579 	Privacy for addrmap_mutable
118582 	Privacy for addrmap_fixed
118586 	Use inheritance for addrmap
118598 	Prior to c6ca3dab dropping support for Cygwin 1.5, __USEWIDE was not
118599 	defined for Cygwin 1.5.  After that, it's always defined if __CYGWIN__
118603 	Prior to c6ca3dab dropping support for Cygwin 1.5, cygwin_buf_t was
118604 	defined as char for Cygwin 1.5.  After that, it's always wchar_t, so
118652 	The PowerPC ioctl value for ioctl_TCSETW is 0x802c7415.  The variable
118655 	unsigned long value tmpulongest to a negative integer value for
118658 	This patch changes the declarations for the ioctl_* values in struct
118663 	the gdb record_linux_system_call() if statement for the ioctl TCSETSW
118670 	PowerPC, correct the gdb ioctl values for TCGETS, TCSETS, TCSETSW and TCSETSF.
118675 	The current PowerPC values for TCGETS, TCSETS, TCSETSW and TCSETSF are
118685 	The definition for the PowerPC termios structure is given in:
118690 	This patch changes the hex digits for the size of the PowerPC termios size
118691 	in the ioctl values for TCGETS, TCSETS, TCSETSW and TCSETSF to 0x2c.
118735 	globals, but that seems overkill for now.
118751 	With gcc-12, I get for test-case gdb.base/vla-struct-fields.exp:
118769 	Multiple matches for value^M
118846 	As a consequence we will return an AArch64 gdbarch object for our ARM
118868 	similar change for store_registers.
118897 	gdb/arm: Simplify logic for updating addresses
118944 	for the rest of the dejagnu run.
118947 	get_compiler_info was for the C++ language then compiler_info would be
118949 	get_compiler_info was for the C language then compiler_info would be
118976 	for each test script, hence, if a test script just checks on the C
118991 	then the global will not be redefined and would be missing for later
118998 	And this is where things get interesting for us.  The library
119013 	supported languages, and the values will be the compiler version for
119016 	Now, when we call get_compiler_info, if the compiler information for
119025 	This means that, for a single test run, we will compute the compiler
119026 	version just once for each language, this result will then be cached
119066 	gdb/testsuite: make 'c' default language for get/test compiler info
119067 	This commit is a minor cleanup for the two functions (in gdb.exp)
119074 	handles "c" and gives an error for unknown languages.
119102 	same cleanup throughout the testsuite, but I'm leaving that for
119224 	When looking for how to apply styling I guess the ideal solution would
119240 	buffer (see below for details).  After this the code can continue to
119253 	is currently true, and hopefully will remain true for the foreseeable
119269 	The next source of content are immediate operands.  The text for these
119284 	result, we never check this particular output for styling escape
119302 	The following commit changes the output format for the isel instruction on
119339 	the new expected output for the isel instruction.
119355 	testing for Linux, try arm-linux-gnueabi-gcc,
119366 	r_length ecoding, but somehow went wrong for 64-bit relocs (which
119418 	The "HOWTO size encoding" patch put 1 as the HOWTO size arg for
119482 	Define a helper macro for HOWTO.
119541 	This changes windows_process_info to use virtual methods for its
119553 	for Windows.
119576 	Introduce wrapper for CreateProcess
119577 	This is a small refactoring that introduces a wrapper for the Windows
119594 	[gdb/rust] Add missing _() for error call
119635 	PR mi/14270 points out that mi-break.exp has some tests for an
119636 	unimplemented "-r" switch for "-break-insert".  This switch was never
119652 	By now I know that A6 is an arc architecture, but for others that's less
119776 	      gdb/python: improve formatting of help text for user defined commands
119779 	call to skip_python_tests.  As a result, this test would fail for any
119851 	the same fix is needed for pascal, take the conservative approach and keep
119852 	behaviour for decimals unchanged.
119863 	the same fix is needed for go, take the conservative approach and keep
119864 	behaviour for decimals unchanged.
119880 	$ for arch in i386:x86-64 i386; do \
119903 	Currently we have (decimal for 0x80000000):
119909 	According to C language rules, unsigned types cannot be used for decimal
119914 	The next interesting case is (decimal for 0x8000000000000000):
119947 	negative decimals for language modula-2.
119988 	Though this fixes the error for me, due to PR29160 I get only FAILs, so I can't
120038 	Use bool for evregpy_no_listeners_p
120046 		intopt.size and remaining bytes in section for reginfo.
120064 	warning: A handler for the OS ABI "GNU/Linux" is not built into this
120068 	and likewise for execute_cfa_program::i8086 and
120080 	This causes a regression in the print_one_insn selftests for the ARC
120128 	The commit introduced regressions for an --enable-targets=all build:
120136 	So, revert the patch in preparation for a simpler solution.
120157 	Similarly for the elf mips support.
120168 	has too.  Which means we can't find output_bfd for __gp.  Also, may as
120169 	well test directly for output_bfd == NULL.
120226 	ODR warning for "main"
120236 	ODR warnings for "struct coff_symbol"
120244 	ODR warnings for "struct insn_decode_record_t"
120253 	ODR warnings for "struct insn_info"
120270 	ODR warning for "enum string_repr_result"
120278 	ODR warning for "struct find_targ_sec_arg"
120286 	ODR warning for "struct stack_item"
120294 	ODR warning for "struct instruction_type"
120302 	ODR warning for struct ext_link_map
120310 	ODR warning for struct field_info
120318 	ODR warnings for struct nextfield
120326 	ODR warnings for struct symloc
120371 	std::sort ().  When there are a lot of objfiles, for example, when
120398 	nat/windows-nat.c").  Update code under ifdef __CYGWIN__ for globals
120402 	Fix Cygwin build after fcab5839 ("Implement pid_to_exec_file for Windows
120405 	includes for parts of that code under ifdef __CYGWIN__.
120442 	evident in the temporary malloc'd buffer for do_scrub_chars output,
120457 	It is possible for sb_scrub_and_add_sb to not consume all of the input
120458 	string buffer.  If this happens for reasons explained in the comment,
120459 	do_scrub_chars can leave pointers to the string buffer for the next
120461 	that the behaviour for an empty string buffer is also changed,
120503 	warning: A handler for the OS ABI "GNU/Linux" is not built into this
120507 	and likewise for execute_cfa_program::i8086 and
120534 	[arm] Don't use special treatment for PC
120536 	just like other base registers, so there is no need for a special
120539 	[arm] Add support for FPU registers in prologue unwinder
120540 	The prologue unwinder had support for FPU registers, but only to
120562 	before the dummy frame created for the signal handler in gdb).
120566 	[arm] Cleanup: use hex for offsets
120581 	for funtions described below:
120617 	value is only known at run-time, set pointer_equality_needed for IFUNC
120625 		for IFUNC function pointer reference in PDE.
120636 	i386: Ajdust more tests for opcodes/i386: remove trailing whitespace
120669 	Use unique_ptr for objfiles
120684 	gdb/testsuite: fixup common-block.exp for intel compilers
120694 	gdb, testsuite, fortran: fixup mixed-lang-stack for Intel/LLVM compilers
120695 	When value-printing a pointer within GDB by default GDB will look for
120729 	symbol for it.
120731 	Since the behavior for Intel/LLVM is actually expected I adapted the
120732 	testcase at this point to be a bit more allowing for other outputs.
120733 	I added the optional "<SYMBOLNAME>" to the regex testing for g.
120735 	The given changes reduce the test fails for Intel/LLVM stack by 4 each.
120754 	Reason for this is that in mixed-lang-stack.cpp in mixed_func_1f an
120776 	For example, in this test the linkage name for var_a in ifx is
120815 	I want to emphasize: for Fortran (and also C/C++) the complete command
120817 	is look for any symbol (in the minimal symbols, partial symbols etc.)
120820 	output for the gfortran compiled executable.  For this look at the
120853 	I think that in the given test the output for gfortran only looks nice
120871 	The given patch improves test performance for all three compilers
120888 	  p typeinfo name for void
120889 	  p typeinfo name for void const*
120890 	  p typeinfo name for void*
120891 	  p typeinfo name for wchar_t
120892 	  p typeinfo name for wchar_t const*
120893 	  p typeinfo name for wchar_t*
120895 	  (gdb) p typeinfo name for void*
120917 	This patch is only about making the referenced test more 'fair' for the
120924 	testsuite, fortran: fix info-types for intel compilers
120930 	variable of that type in the test.  Still, gfortran emits it for every
120934 	argc and argv arguments for command line argument passing and the argv
120971 	Ifx and flang do not emit any debug info for a wrapper main method so
120986 	As adding a type would have a) not solved the problem for ifx and would
120988 	check for this character type was chagened to optional with the
120989 	check_optional_entry to allow for the symbols's absence and to allow
120992 	Second, the line checked for s1 was hardcoded as 37 in the test.  Given
120994 	ifx) it even seems wrong.  The line check for s1 was changed to actually
120995 	check for 41 and a gfortran bug has been filed here
120999 	The test is now marked as xfail for gfortran.
121001 	Third, the whole test of checking for the 'Type s1' in info types seemed
121005 	The 'info types' command checks for types stored in the GLOBAL_BLOCK,
121013 	so for gfortran, the type shows up in the output of 'info types'.  For
121017 	been opened for the gfortran scoping issue:
121021 	While the most correct change might have been removing the check for s1,
121022 	the change made here was to only check for this type in case of gfortran
121030 	testsuite/lib: add check_optional_entry for GDBInfoSymbols
121031 	There was already a similar functionality for the GDBInfoModuleSymbols.
121033 	later commit to make a testcase less GNU specific and more flexible for
121040 	they test for symbols that are not actually required to be emitted.  The
121046 	check for types that are either not used in the source file (character1)
121054 	In order for ifx and ifort to emit all debug entries, even for unused
121064 	performance for different compilers.  For ifx and gfortran I do not see
121073 	a bug and there is an open gcc ticket for this here:
121082 	gdb/testsuite: disable charset.exp for intel compilers
121083 	The test specifically tests for the Fortran CHARACTER(KIND=4) which is
121087 	test for the unsupported compilers.
121092 	The name for icx and icpx in the testsuite was earlier set to 'intel-*'
121103 	the testsuite, similar to the existing one for C/C++.  Before this
121104 	change, the options and version for the Fortran compiler specified when
121122 	As most/nearly all Fortran compilers have a mechanism for preprocessing
121124 	existed for C/CXX.  We let GDB preprocess a file with the compilers
121139 	identification mechanism for Fortran compilers in the compiler.F90 file.
121141 	We added identification for GFORTRAN, FLANG (CLASSIC and LLVM) IFX,
121142 	IFORT, and ARMFLANG for now.
121148 	enough yet for running the testsuite we still thought it would be a good
121149 	idea to include it already.  For this we added a case for the fortran_main
121176 	procedure do recursively test for the compiler version to e.g. set
121177 	certain flags, at several places gdb_compile there are checks for the
121182 	again and again looking for getting_compiler_info in the procedure
121197 	gdb/testsuite: Fix fortran types for Intel compilers.
121204 	gdb/testsuite: Use -module option for Intel Fortran compilers
121228 	inconsequent to only implement this for f90 but, on the other hand, f77
121229 	seems deprecated.  So, with this commit we remove the remaining lines for
121258 	SYMBOL_REFERENCES_LOCAL can return true for undefined symbols.  This
121302 	Ajdust more tests for opcodes/i386: remove trailing whitespace
121336 	whitespaces for the regexp.
121362 	The issue here is that "location" isn't really correct for most of
121364 	placeholder that represent an umbrella term for all of the
121410 	- Goes through the manual, and where "@var{location}" was used for a
121425 	Special thanks goes to Eli Zaretskii for reviews and rewording
121468 	Fix failing test for armeb-gnu-eabi
121471 	FAIL: Unwind information for Armv8.1-M.Mainline PACBTI extension
121473 	This patch adjusts the expected output for big endian.
121513 	This also removes some unused variables, and deletes support for the
121533 	use the same opcodes, thanks for Nelson's works.
121566 	gdb/python: improve formatting of help text for user defined commands
121606 	The same problem can be observed for gdb.Parameter objects in their
121609 	In this commit I aim to improve the "help" output for commands and
121641 	gdb: use gdb::unique_xmalloc_ptr<char> for docs in cmdpy_init
121669 		* src/Experiment.cc (write_header): Fix argument for ctime.
121695 	  for (i = strlen (ins->obuf) + prefix_length; i < 6; i++)
121738 	However, 'nop' is actually an alias for 'xchg %rax,%rax', so,
121744 	for 'nop', and adjust the buffer to this:
121759 	The fix for this is pretty easy, I can change NOP_Fixup to adjust
121772 	I've left in the fix for NOP_Fixup, I think updating mnemonicendp is
121776 	expected patterns to account for the change in whitespace.
121788 	the type only needs to be large enough for a 32-bit integer or a
121797 	uint64_t, and similarly for bfd_int64_t, BFD_HOST_U_64_BIT, and
121821 	Sadly the split out function, at least for the time being, needs to cast
121851 	Acceptance of the original {1to<n>} operand suffix is retained both for
121879 		__collector_getpc): Adapt for build with -mx32
121913 		for cris*-*-*.
121923 	This fixes the build on older FreeBSD systems without support for
122062 	The core of the issue is that GDB never loads the psymtab for the
122067 	before the new indexer was activated, the psymatb construction for the
122074 	        for (partial_symtab *ps : require_partial_symbols (objfile))
122084 	when calling the quick functions.  The general pattern for calling the
122087 	    for (auto *iter : qf)
122109 	happens if the aranges for a CU claims a PC, but the symtab that is
122128 	While this step is run in the background, gdb will wait for the
122148 	doesn't) change.  Instead, a simple way to make gdb wait for the
122181 		true for arm and nacl.
122198 		(s_arm_unwind_save): Simplify logic for simple/mixed register saves.
122236 	bfd: Add Support for DW_FORM_strx* and DW_FORM_addrx*
122257 	Re: Add bionutils support for DWARF v5's DW_OP_addrx
122285 	left side of the source window, with "b-" for a disabled breakpoint.
122291 	Add bionutils support for DWARF v5's DW_OP_addrx.
122315 	See previous commit's log for more info.
122317 	In addition to looking for DUPLICATEs, I also looked for cases where
122358 	emit PASSes for each iteration, we run into the situation where
122431 		* config/tc-ppc.c (insn_validate): Use ppc_opindex_t for operands.
122436 		* ppc-dis.c (skip_optional_operands): Use ppc_opindex_t for
122472 	test-case, and it would work only for clang and not other compilers that
122508 	Note that the test-case intends to check the handling of debug info for
122520 	due to reserved 11 for extension in glibc, otherwise when execute:
122537 	AArch64: add support for DFP (Decimal Floating point)
122538 	This small patch adds support for TYPE_CODE_DECFLOAT in
122540 	so that GDB for AArch64 knows how to pass DFP parameters and how to
122552 		* dfp.m4 (enable_decimal_float): Enable BID for AArch64.
122566 		(read_and_display_attr_value): Don't attempt to check for .dwo
122587 	Tweak the std::hash<> specialization for aarch64_features.
122598 	Fix loongarch_iterate_over_regset_sections for non-native targets.
122599 	Define a constant for the number of registers stored in a register set
122616 	  FAIL: gdb.base/auxv.exp: load core file for info auxv on native core dump
122640 	commit-resumed for target native, no resumed threads^M
122743 	resulting in an offset_to_top for gcc 8:
122748 	and for gcc 7:
122857 	wouldn't be super great for us, IMO, given we think of every type of
122896 	To look for code paths that lead to create_breakpoints_sal creating
122951 	that are always necessary for momentary breakpoints.
122960 	exit/_exit, for example.
122999 	class for code breakpoints).
123004 	I inlined new_single_step_breakpoint into its only caller exactly for
123008 	that turned out unwieldy for this patch.
123031 	sal it would ultimately use the breakpoint's gdbarch for the
123056 	returns false for bp_loc_other, which is in accordance with we
123057 	document for bp_location::address:
123059 	  /* (... snip ...)  Valid for all types except
123106 	new_breakpoint_from_type for internal_breakpoint breakpoints.
123216 	Thus, the only thing init_raw_breakpoint is needed for, is to add the
123233 	A patch later in the series will move this to base_breakpoint, but for
123250 	suffix for the instruction when in fact it is the following instruction.
123267 	together followed by the prefix instructions for clarity.
123290 		(main): Do not enable dwarf section dumping for -WK or -WN.
123291 		* readelf.c (parse_args): Do not enable dwarf section dumping for
123323 	it should be removed until RV128 support for GNU Binutils is required
123358 	(for inline-detection purposes) for each and every sample. In Chromium
123363 	compilation unit spaces; for content_shell, which is 1.6 GB when some
123365 	0.006 ms (6 µs) for each lookup from address to compilation unit, a 1000x
123370 	between 2–3 GB for a medium-size profile); for smaller binaries with few
123392 		* ld.texi: Typo fixes.
123404 	The current assembler accepts system registers FPCXTNS and FPCXTS for Armv8.1-M
123435 	The example for 'info pretty-printer' in the manual passes an
123524 	resolved (albeit later, hence this being a separate issue). As for the
123527 	spelled out individually for each of them in md_apply_fix().
123531 	COFF: use hash for string table also when copying / stripping
123548 	Fill the timestamp field suitably for _bfd_XXi_only_swap_filehdr_out().
123566 	This involves first of all clearing D_PAGED for images when section and
123582 	anymore, and hence a binary could change in that 2nd step for no actual
123637 	block of case labels leading to a return of 1. While not of interest for
123650 	oops - forgot changelog entry for the previous delta.
123652 	arm: Add unwind support for mixed register lists
123662 		* testsuite/gas/arm/unwind-pacbti-m.s: Expand test for mixed
123678 	[AArch64] Return the regnum for PC (32) on aarch64
123680 	for the return address from the link register.
123681 	Such usage, although uncommon, is valid and useful for signal frames.
123704 		* doc/binutils.texi: Document new feature.
123756 	number appropriately for a given language.
123787 	AArch64: Enable FP16 by default for Armv9-A.
123788 	In Armv9-A SVE is mandatory, and for SVE FP16 is mandatory.  This fixes a disconnect
123810 	decimal digits for the line part of the contruct). Since the scrubber
123820 	implementation defined signal), but for now makes the assumption that
123822 	aliases) is defined in bfd.h for the BFD64 case I cannot really see a
123850 	gas: tweak .irp and alike file/line handling for M68K/MRI
123851 	In commit 2ee1792bec22 ("gas: further adjust file/line handling for .irp
123898 	gdb, btrace: Throw an error for empty recordings when replaying starts.
123938 	gdb.base/skip.exp abuses gdb_test's support for answering a GDB
124030 		and zicsr for zfh.
124031 		(riscv_supported_std_z_ext): Added default v1.0 version for zfh.
124038 		* testsuite/gas/riscv/float16-be.d: New testcase for .float16.
124041 		* testsuite/gas/riscv/fp-zfh-insns.d: New testcase for zfh.
124044 		* opcode/riscv-opc.h: Added MASK and MATCH encodings for zfh.
124045 		* opcode/riscv.h: Added INSN_CLASS and pseudo macros for zfh.
124175 	Implement pid_to_exec_file for Windows in gdbserver
124176 	I noticed that gdbserver did not implement pid_to_exec_file for
124190 	a bit closer, and allows for the removal of a const_cast as well.
124194 	It's better, when at all possible, for test files to end up in the
124199 	Do not double-read minimal symbols for PE COFF
124202 	but at least for my mingw builds of gdb, this seems to be the case.
124276 	table.  Still, we had no testcase for that yet.  In fact, we have no
124315 	The same for gcc 8.2.1, but it passes with gcc 9.3.1.
124338 	Fix this by adding the missing typedef for gcc version 5 (the first version to
124362 	spurious warning for stringop-overread in debuginfod_is_enabled
124363 	for url_view. Also suppress it on powerpc64.
124374 	being used. While the results are OK for i387 128-bit long doubles, it
124375 	is not correct for IEEE quad 128-bit long doubles.
124378 	be available at all. And it may be the case that the compiler for a 64-bit
124396 	- Use long double values appropriate for the long double format.
124447 	cgen: increase buffer for hash_insn_list
124448 	As was done for hash_insn_array in commit d3d1cc7b13b4.
124457 		* ar.c (main): Properly handle libdeps for zero file_count.
124463 	output to 32 bits for 32-bit targets.  The test was faulty anyway,
124506 	nm: use -U as an alias for --defines-only, in line with llvm-nm
124543 	  - once for exec maint, and
124544 	  - once for "Object file system-supplied DSO".
124562 	test for supported targets using istarget, like so:
124613 	Fix this by adding support for recording syscall statx.
124686 	The GDB style is to write 'if (readbuf != nullptr)', and the same for
124700 	This patch fixes this build by introducing a compatibility wrapper for
124725 		 print it as "struct foo" or as "bar"?  Pick the latter for
124750 	expanding the typedefs for -- in the example in question, the
124779 	for a specific language, so we just hardcode the language.
124807 	GDB that only makes sense if the program is built for the pre-C++11
124820 	Itanium ABI mangling scheme has a shorthand form for std::string (and
124854 	GDB first replaces "uint32_t" for its underlying type, and then sets a
124876 	replace the std::string typedef for its underlying type using the same
124877 	mechanism I mentioned for the "f(uint32_t)" example above, then GDB
124880 	as the function symbol GDB knows about for that function, given no
124884 	names has an exception for std::string (and other standard
124899 	for "std::string" anymore, it always demangles as:
124905 	exception for "std::string" and doesn't expand it, so the breakpoint
124912 	So to fix things for C++11 ABI, clearly we need to remove the
124923 	standard abbreviation for "std::string" as "std::basic_string<char,
124949 	gdb/testsuite: fix testsuite regressions for unix/-m32 board
124953 	Reason for the failures was, that on a 32 bit machine the maximum
124954 	array length as well as the maximum allocatable memory for arrays
124958 	behavior is compiler dependent and can differ for different compiler
124962 	The affected tests check for GDB's overflow behavior when using KIND
124965 	result, an overflow is expected.  This was done for 1, 2, and 4
124975 	respective compilers for while (e.g. C_SIZEOF is available since
124982 	fit into 4 byte signed integers for some of the arrays, as it was
125009 	does not work with ifx (or flang for that matter, they behave similarly
125070 	type exists.  This reduces the size of a -O0 -g3 build for me by
125147 	2. The allowed range for these operands is [-(1 << 32), (1 << 32) - 1],
125165 	In bug PR gdb/29036, another failure was reported for the test
125180 	pattern that checks for the first command a little.  With this fix in
125245 	gdb: fix for gdb.base/eof-exit.exp test failures
125255 	the Ctrl-D is sent while GDB is waiting for input at a prompt.
125293 	[gdb/tdep] Support catch syscall pipe2 for i386
125347 	[gdb/tdep] Handle pipe2 syscall for amd64
125365 	There is already support added for syscall pipe2 for aarch64 (which only has
125366 	syscall pipe2, not syscall pipe), so enable the same for amd64, by:
125595 	This patch includes a test for this issue as well as a back-port of
125601 	      fix for setting RL_STATE_EOF in callback mode
125616 		for negation.
125636 	PowerPC fix for gdb.server/sysroot.exp
125646 	starting immediately after the printf.  The test now works for PowerPC
125658 	This introduces a catchpoint class that is used as the base class for
125679 	Disable copying for breakpoint
125719 	works_in_software_mode is only useful for watchpoints.  This patch
125749 	kernel changes involving the vdso for PowerPC have been made changes to the
125778 	The above changes for PowerPC signal handler, causes gdb to stop in the
125801 	make[2]: *** Waiting for unfinished jobs....
125834 	Consequently, the address for foo determined by get_func_info doesn't match
125845 	gdb: use gdb::function_view for gdbarch_iterate_over_objfiles_in_search_order callback
125848 	capture, and eliminating the need for the untyped pointer.
125907 	Don't define ARCH_cris for BFD64
125914 	Various packages (glib and gtk4 for example) produces data-only objects
125932 		(MASK_RRF_R0RER): Define mask for new instruction type.
125933 		* s390-opc.txt: Use RRF_R0RER for mgrk and RXY_RERRD for mg.
125968 		LDPR_PREVAILING_DEF for __real_SYM reference.
126005 	Fix build failure for aarch64 gdbserver
126011 	For some reason g++ 11.2.1 on s390x produces a spurious warning for
126012 	stringop-overread in debuginfod_is_enabled for url_view. Add a new
126030 	tests for aarch64-linux.
126032 	We started seeing the following internal error for
126033 	gdb.multi/multi-target-continue.exp for example:
126063 	 1 - The probe-based breakpoint mechanism failed (for some reason) so ...
126113 	process on initial connection, and this would send a qSymbol for only
126117 	packet for each one.
126139 	I was able to see qSymbol being sent for each inferior:
126159 	this scenario, more things that need to be done for each discovered
126160 	inferior instead of just for one.
126244 	      [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target remote
126245 	      [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target remote
126256 	      [infrun] handle_vfork_done: not waiting for a vfork-done event
126265 	      [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target remote
126266 	      [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target remote
126277 	   space to be deleted, which clears the symtabs for that program space,
126284 	let the remote side ask for symbol addresses.  The problem is that the
126287 	for a stop reply.  It can't send any packets in the mean time.  That
126295 	invoked for a change in inferior 2's program space (inferior 2's program
126298 	pruned).  It doesn't make sense to try to send a qSymbol packet for a
126313 	qSymbol packet for inferior 1 in reaction to a change in inferior 2's
126351 	As already done for PowerPC64, fix dynamic relocs for absolute symbols.
126358 		Rearrange tests for dynamic relocs, handling absolute symbols.
126359 		(allocate_dynrelocs): Don't allocate dynamic relocs for locally
126383 	NEWS: Add a note for TLS support on FreeBSD/arm and FreeBSD/Aarch64.
126391 	Fetch the NT_ARM_TLS register set for native FreeBSD/Aarch64 processes.
126401 	Fetch the NT_ARM_TLS register set for native FreeBSD/arm processes.
126411 	fbsd-nat: Add helper routines for register sets using PT_[G]SETREGSET.
126414 	helper routines provide helpers to check for a register set's
126415 	existence, fetch registers for a register set, and store registers to
126469 	  WARNING: Timed out waiting for EOF in server after monitor exit
126519 		* libdep_plugin.c (get_libdeps): Check for overflow when computing
126538 	with a call to 'mi_gdb_start' - just for consistency.
126596 	look for some expected output on each, however, as there is no CLI
126667 	The problem for the 'run failure detected' test is that we end up
126668 	in gdb_expect looking for output from two spawn-ids, one from
126669 	gdbserver, and one from gdb.  We're looking for one output pattern
126670 	from each spawn-id, and for the test to pass we need to see both
126693 	checks the gdbserver spawn-id for additional output, and so never sees
126695 	pattern from gdb to be seen, and for the test to pass.
126706 	Starting with gcc 12.1 / gcc 11.3, for test-case gdb.cp/align.exp we run into:
126749 	    replacement for free (see gnulib/import/m4/free.m4).  In that path,
126792 	The breakpoint C++-ification series introduced a regression for Ada
126812 	No unwaited-for children left.^M
126841 	Currently, the get_disassembler() implementations for riscv, csky, and
126842 	rl78--and mep_print_insn() for mep--access ELF variants of union fields
126845 	(the "binary" BFD, for example).  Fix that.
126857 	allocate_bp_location is just a small wrapper for a method call, so
126893 	This patch merges the two cases, just as was done for breakpoints.
127025 	eventually be removed, but in the meantime is is useful for helping
127055 	series.  Spot-checking the resulting index for gdb itself, it seems
127059 	roughly the same (it's worth noting that, for gdb itself, the index no
127085 	looks for DW_TAG_structure_type.
127157 	      [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target native
127158 	      [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target native
127159 	      [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target native
127181 …[infrun] maybe_set_commit_resumed_all_targets: not requesting commit-resumed for target native, no…
127190 	After handling the EXITED event for inferior 2, inferior 2 should have
127226 	Random note: the thread_info object for inferior 2's thread is never
127233 	thought it would be good to mention it, in case somebody has an idea for
127247 	    for that thread.
127250 	    process), the step/signal request is for inferior_ptid, and PTID
127256 	  - step/signal are always for inferior_ptid.
127286 	previously used for free.
127300 	used for function reference due to function pointer reference.
127306 		pointer_equality_needed nor check non-canonical reference for
127348 	breaking most tests, e.g. gdb.base/break.exp is failing for me.
127360 	So, before the commit we checked for the block ranges being nullptr,
127387 	always located in .rela.iplt - even for non-static case.
127399 	No dynamic relocs are needed for TLS defined in an executable, the
127408 		instead of bfd_link_pic for TLS.
127455 		* testsuite/ld-ctf/conflicting-typedefs.d: Adjust for ordering
127476 		* testsuite/lib/Makefile.skel: Search parent dir for libs too.
127489 	addrmap parameter.  This helps for the following patch, where getting
127526 	Replace with range for loops.
127598 	of a "long" type, and this isn't currently accounted for in
127602 	4 bytes for x86_64.  This causes the following FAIL's:
127618 	architectures show "unsigned int" for both 32-bit and 64-bit integers
127619 	and 64-bit architectures show "unsigned int" and "unsigned long" for
127625 	Here's what we get for aarch64:
127641 	And for arm:
127676 	Fix gdbserver build for x86-64 Windows
127690 	Create pseudo sections for NT_ARM_TLS notes on FreeBSD.
127698 	This patch makes use of the support for several stack pointers
127720 	gdb/arm: Add support for multiple stack pointers on Cortex-M
127731 	This patch is a preparation for the rest of the series and adds two
127735 	gdb/arm: Define MSP and PSP registers for M-Profile
127743 	While working on adding support for Non-secure/Secure modes unwinding,
127744 	I noticed that the prologue analysis lacked support for vpush, which
127745 	is used for instance in the CMSE stub routine.
127748 	for vpush of D-registers.
127790 	supported for non-ELF targets, and isn't needed since we now prune the
127809 	GDB PowerPC record test cases for ISA 2.06 and ISA 3.1
127822 	Add recording support for the ISA 3.1 PowerPC instructions.
127823 	This patch adds support for the PowerPC ISA 3.1 instructions to the PowerPC
127825 	number of the existing routines for recording the 32-bit word instructions.
127876 …PowerPC: Update expected floating point output for gdb.arch/altivec-regs.exp and gdb.arch/vsx-regs…
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
127910 	gdbsupport/pathstuff.h: #include <array> explicitly for std::array<>
127942 	gdb/fortran: Support for assumed rank zero
127945 	not support the case for assumed rank 0.  This patch provides support
127946 	for assumed rank 0 and updates the testcase as well.
127996 	  all threads just to stop them right away for a step over breakpoint.
128007 	As for infrun-related things, I am never completely sure I did not miss
128036 	is not always acceptable, see this mail for more details:
128044 	Then, for MS-Windows hosts, we don't call setbuf for terminals, this
128097 	   for (auto *target : all_non_exited_process_targets ())
128106 	   waiting for a stop reply, so it can't send packets to update the
128112 	condition where some target reports a breakpoint hit for a thread and
128191 	this thread for more details:
128202 	Please read that commit for a full description of the bug, and why is
128218 	The reason for this is that, in rl_deprep_terminal, readline will
128233 	now always print "quit\n" and this works for all cases.
128242 	command_line_handler for printing 'quit', however, this code is only
128294 	This commit alone does not fix the PR cli/28833 issue, for that see
128348 	readline 7, for example 'Ubuntu 18.04'.  Then run the test
128381 	Most of the time, GDB will get and process the exit event for inferior 1
128384 	exit quickly, such that GDB collects from the kernel the exit events for
128386 	at random, which can be the event for the parent.  This will result in
128390 	After expect has seen the "exited normally" notification for inferior 1,
128395 	the "no thread" test fail.  If the test waited just a bit more for the
128396 	"exited normally" notification for inferior 11, then the list of threads
128400 	notifications for all inferiors before proceeding, that should ensure we
128408 	FSM for the continue command completed when inferior 1 exited.  At that
128455 	but it's much simpler to use a for-each loop.  This allows for the
128463 	.gdb_index would have the wrong fully-qualified name for a method.
128468 	was not updated for this container.
128472 	RISC-V: Add missing DECLARE_INSNs for Zicbo{m,p,z}
128473 	The recently added support for the Zicbo{m,p,z} extensions did not
128474 	include DECLARE_INSN() declarations for the instructions.
128484 	Fix for gdb.base/solib-search.exp test.
128505 	Without the patch, we have the Intel backtrace for the bad libraries:
128549 	for both the good and bad libraries.
128557 	Now with the patch the backtrace for the bad library on PowerPC looks
128565 	And the backtrace for the good libraries on PowerPC looks like:
128580 	the dynamic linker works and what the default size is for the data and
128590 	actually my original fix for the program until I spoke with Doug Evans
128600 	up in the binary for the correct or incorrect library on Intel or PowerPC.
128601 	With the patch, RIGHT gets defined as originally intended for the test on
128629 	mi_continue_to_line, for example:
128666 	symbol" implementations, there's no reason for this approach -- it's
128667 	safe and easy for all symbol readers to reuse the per-BFD data when
128683 	  Support for the `p' packet is auto-detected, currently unknown.
128696 	  Support for the `X' packet is auto-detected, currently unknown.
128734 	(for example, when the right hand side is a Windows path with a drive
128765 	We currently only test decimal and hexadecimal for the
128766 	gdb.Value.format_string() interface, this patch adds testcases for
128774 	The gdb_test_multiple pattern for the "notice empty URL" test in
128788 	  Enable debuginfod for this session? (y or [n])
128815 		(run_dump_test): Call prune_warnings for ld and objcopy output.
128818 		around test for absent .note.GNU-stack
128838 	out_of_range exception during the printing of URLs for the first
128888 	Use array_view for symbol_impls
128889 	It seemed to me that using array_view for symbol_impls would give a
128893 	Add accessors for symbol's artificial field
128898 	The dwarf2_per_bfd object has a separate field for each possible kind
128907 	Some generic code in the DWARF reader has a special case for older
128918 	This introduces dwarf_scanner_base, a base class for all the index
128929 	if it were from OBJF_READNOW.  However, this trick is only done for
128930 	gdb_index, never for debug_names -- see dwarf2_initialize_objfile.
128948 	So far an SAE-only specifier was accepted for static-rounding insns,
128952 	than globally via -mevexrcig=. But for now make things match the SDM.
129010 		(xcoff_link_add_symbols): Save rawsize for XTY_SD.
129024 		for stubs.
129074 	of a symbol.  However, I think it's better for all users to call
129079 	Add linker warning for when it creates an executable stack.
129115 	for all architectures supported by GDB.  It is used in many _initialize_*
129153 	latest possible moment.  This is intended for situations where GDB needs
129175 	x86: don't mistake ordinary immediates for SAE / rounding control
129177 	the need for separate templates in the first place), and expressing the
129186 	for insns allowing for SAE is a prereq for planned further work.
129190 	sizes, hence there are no pairs of operands to check for consistent
129201 	It's not just REX.W which is ignored with opcode 0x90. The same goes for
129208 	ins->address_mode for mode_64bit also is unnecessary, as "rex" can be
129217 	gdb/testsuite/dwarf: don't automatically add directory and file entry for DWARF 5
129290 	offset of 0, the cast would work -- for example, one of the two new
129343 	This patch fixes only compilation error, for example:
129435 	Implement value_print for Rust
129439 	a test for the bug that inspired this patch, because I only know how
129450 	representation for unsized types.  Fixing this is PR rust/21466; but
129464 	added for it.  However, once val_print was removed, it became
129559 	 - The prepare_to_access_memory machinery was added for non-stop mode.
129589 	... is incorrect for /proc/PID/mem does allow that.
129593 	threads for the duration of the memory access, via
129613 	The next patch in this series adds a common helper routine for both
129659 	gdb::byte_vector (which is a specialized std::vector).  It's valid for
129698 	I've patched an existing test to provide a regression test for this.
129732 	Implement thread_name for gdbserver
129737 	approach for setting thread names, but gdbserver does not.  This patch
129739 	preparation for adding this support to gdbserver.
129752 	This makes it more consistent for the eventual merger with gdbserver.
129785 	The issue is that when doing the test for "return 35", the DejaGnu test
129817 	approach that was used for gdb::optional, but that didn't work, so
129830 	     warning: Could not load shared library symbols for WOW64_IMAGE_SECTION.
129832 	     warning: Could not load shared library symbols for WOW64_IMAGE_SECTION.
129834 	     warning: Could not load shared library symbols for NOT_AN_IMAGE.
129836 	     warning: Could not load shared library symbols for NOT_AN_IMAGE.
129875 	vertical space for easier reading in info), fixes a typo, adds some
129919 	Currently, the configure check for std::thread relies on pthreads
129920 	existing.  However, this means that if std::thread is implemented for
129929 	This configure change fixes this problem and enables threading for
129958 	On openSUSE Leap 15.3, mpx support has been disabled for m32, so I run into:
130148 	gdb: use std::vector for temporary linetable_entry array in arrange_linetable
130159 	Change subfile::name to be a string, for easier memory management.
130162 	both at the same time.  There are various NULL checks for both fields
130174 	memset-ing it to 0.  Use a unique_ptr for the window after a subfile has
130202 	gdbsupport: use result_of_t instead of result_of in parallel-for.h
130205 …for-selftests.c:22:                                                                             /h…
130240 	Moving this patch around is how I got separate numbers for the
130304 	to wait for this process to complete.
130325 	for the new index -- that is, when the "enable the new index" patch is
130337 	"info"-related sections.  This is done for the main file, but also any
130345 	Introduce thread-safe handling for complaints
130372 	I did a bit of performance testing for this patch and a few others.  I
130385 	Implement quick_symbol_functions for cooked DWARF index
130386 	This implements quick_symbol_functions for the cooked DWARF index.
130393 	different; see expand_symtabs_matching for the gory details.
130418 	name as is done for partial symbols.
130424 	Some special code is needed for Ada, because GNAT only emits mangled
130439 	Update skip_one_die for new abbrev properties
130447 	the text for the .debug_names section, disregarding the bugs in the
130452 	abbrevs imply a static size for the DIE data, and additionally that
130453 	for many abbrevs, the sibling offset is stored at a constant offset
130466 	The replacement for the DWARF psymbol reader works in a somewhat
130469 	CU and reads them all.  This approach is used for both intra- and
130488 	for that CU need only be computed a single time.
130497 	Specialize std::hash for gdb_exception
130498 	This adds a std::hash specialization for gdb_exception.  This lets us
130510 	10 elements.  However, when indexing, it's fine for a thread to handle
130544 	package components for them.  In order for this to work out properly,
130556 	addresses have been seen for this CU.  This is then set by the
130578 	However, there's no deep reason for this, and during review we found
130583 	thread (for example if it is configured to have no threads in the
130591 	After the thread-pool change, parallel-for.h no longer needs any
130617 	regression test for this particular case.  I'm checking this in.
130635 	Require GNAT debug info for some Ada tests
130659 	for them. As a result in a number of case function parameter aren't used
130664 	gas: further adjust file/line handling for .macro
130676 	Note that from_sb_is_expansion's initializer was 1 for an unknown
130690 	gas: further adjust file/line handling for .irp and alike
130726 		* src/QLParser.yy: Adapted for bison 3.04 or later.
130767 	Add a getter and a setter for a minimal symbol's type.  Remove the
130809 	When working on the files I noted that there was no actual test for a
130810 	COMPLEX built from two INTEGERS.  I added that now for completion.
130819 	Additionally, the one argument overload for the CMPLX intrinsic function
130822 	This patch adds overloads for all above mentioned functions to the
130847 	gdb/fortran: Change GDB print for fortran default types
130864 	Similarly, GDB would print the default integer type for the underlying
130877 	what the internal underlying type for the default type is - but I think
130923 	This patch changes the outputs for the REAL and INTEGER default types to
130926 	The new behavior for the above examples is:
130938 	The currently implemented intrinsic type handling for Fortran missed some
130941 	consistent.  As an example for what this patch does, consider the
130958 	   unsupported kind 1 for type integer
131000 	new behavior.  Tests for formerly missing types have been added.
131009 	storage, and so the default type for logical expressions in
131028 	were possible in GDB, which seems confusing for a user.  The reason
131032 	COMPLEX type the kind parameters usually (at least for GNU, Intel, Flang)
131042 	a few tests for this new behavior as well.
131087 	[gdb/testsuite] Fix gdb.dwarf2/dw2-lines.exp for m32 pie
131105 	  for the prologue part of the function, so consequently gdb uses the i386
131139 	Don't run pr27228 test for hppa
131144 		* testsuite/gas/elf/pr27228.d: Change xfail to notarget for hppa.
131159 	And disable the new test gas/elf/size.s for alpha which uses its own
131160 	.set, for hppa*-*-hpux* which does not allow .size before declaration.
131164 	gprofng: fprintf_styled_func not inizialized for disassembler
131216 …../../src/gdb/valarith.c:1365:15: runtime error: shift exponent 64 is too large for 64-bit type 'l…
131260 	  too-large shift).  So for that language GDB does the shift and
131264 	  For shift by a negative count, for Go, this is a hard error.  For
131340 	Debug info for function in Windows PE binary on wrong instruction
131369 	    checking for libdebuginfod >= 0.179... no
131392 	(because gdb/configure has changed, for example), the PKG_CONFIG_PATH
131428 	I was confused for a while, I was trying to load the binary in GDB
131451 	for the extended type.
131456 	gdb/fortran: add support for accessing fields of extended types
131543 	      gdb: add support for Fortran's ASSUMED RANK arrays
131545 	Added support for Fortran assumed rank arrays.  Unfortunately, this
131586 	redundant code, and make it easier to add support for a new compiler.
131589 	falls back to -g3 otherwise (which works for gcc).  Other compilers can
131595 	compilers to notice something is wrong and maybe add support for their
131659 	Same idea as previous patch, but for symtab::pspace.
131666 	Same idea as previous patch, but for symtab::objfile.  I find
131692 	compilation time.  At least for DWARF, if the symtab's filename is
131711 	I wrote this for a downstrean GDB port,  but thought it could be
131765 	vector containing all the reggroups for an architecture.
131773 	for loops instead of the old style look using reggroup_next.  There
131810 	of default_groups in gdb/reggroups.c for details on this.
131827 	description will mention additional groups, e.g. groups for special
131834 	register groups for every architecture, always.  This change is in
131849 	  thing, there's something to be said for having some consistent
131857 	  Obviously, for the architectures that didn't previously add all the
131964 	This commit makes the 'struct reggroup *' argument const for the
131990 	expect, except for the very last line:
132051 	I wondered how to solve this problem for a while, however, I don't
132057 	looking for it.
132084 	Add support for COFF secidx relocations
132087 		(coff_pe_i386_relocation_section): Add support for R_SECTION.
132088 		(coff_i386_reloc_type_lookup): Add support for
132092 		(coff_pe_amd64_relocation_section): Add support for R_SECTION.
132093 		(coff_amd64_reloc_type_lookup): Add support for
132100 		(md_pseudo_table): Add support for secidx.
132105 		* symbols.c (resolve_symbol_value): Add support for O_secidx.
132125 	information for functions marked as such and having their size
132141 	cover for insn size differences).
132145 	Arm64: arrange for line number emission for .inst
132149 	Arm32: arrange for line number emission for .inst
132153 	RISC-V: add testcase to check line number emission for .insn
132158 	IBM zSystems: Add support for z16 as CPU name.
132166 		* doc/as.texi: Add z16 and arch14 to CPU string list.
132167 		* doc/c-s390.texi: Add z16 to CPU string list.
132222 	simplifies the code a little.  This was useful for another patch I'm
132255 	entirely optimized out, for example on exit of
132260 	This wasn't a problem for value_copy before, because it was calling
132265 	we copied bytes for an entirely optimized out value (i.e. meaningless
132280 	a buffer for an entirely optimized out value.  It's even a bit less
132293 	In this patch, I opt for choice #2, since I think it is a better
132307 	Fix for v850e divq instruction
132308 	This is the last of the correctness fixes I've been carrying around for the
132320 	Testcase for the simulator is included.  It has a trivial dependency on the
132325 	Fix "bins" simulation for v850e3v5
132326 	I've been carrying this for a few years.   One test in the GCC testsuite is
132334 	That seemed better than using 1UL for the constant (on a 32bit host unsigned
132347 	gdb: LoongArch: prepend tramp frame unwinder for signal
132349 	frame unwinder for signal on LoongArch.
132382 		(read_and_display_attr_value): Add support for DW_FORM_loclistx
132385 		(display_loclists_list): Add support for DW_LLE_base_addressx,
132391 		(display_debug_rnglists_list): Add support for
132402 	This set of changes enable support for the ARMv8.1-m PACBTI extensions [1].
132413 	- Extend the prologue analyser for 32-bit ARM to handle some instructions
132421 	- Adds support for DWARF pseudo-register RA_AUTH_CODE, as described in the
132431 	supported for bare metal targets.
132517 	scheduling being what it is, it is possible for the parent to un-freeze
132519 	exit events for both processes are available.  And then, GDB may chose
132520 	at random to return the one for the parent first.  This is what I
132565 	Note that for test "frame 5", we are showing a pthread frame (on my
132571 	And for test "frame 6", it's ok to _not_ expect a hex prefix (what the
132577 	they are stopped.  If the scheduler chooses so, it is possible for the
132600 	or it is that way for historical reasons.
132608 	I see there are lots of other cases of undocumented number format for error
132618 … fork_func=fork: target-non-stop=auto: non-stop=off: displaced-stepping=auto: i=2: next to for loop
132622 	(some lines omitted for brevity).  We do the next:
132660 	However, for the vfork case, where we are waiting for the
132723 … fork_func=vfork: target-non-stop=on: non-stop=off: displaced-stepping=auto: i=14: next to for loop
132739 	for 2742805 is indeed a vfork event:
132757 	It's then all downhill from there, stop_all_threads eventually asks for
132766 	already in event_child->waitstatus (in the case of fork/vfork, for
132779 	The intent of this branch is, for example, when we sent SIGSTOP to try
132796 		 but, it stopped for other reasons.  */
132848 	  1. Receive "vfork" event for the parent
132853 	  5. Wait for and receive "vfork done" event for the parent
132858 	Resuming the parent at step 4 is necessary in order for the kernel to
132860 	for a thread that is ptrace-stopped.  But the theory behind this is that
132863 	waiting for the child to exec or exit.  So it doesn't matter for that
132883 	on/off, schedule-multiple on/off), but for this patch I restrict the
132887 	The code paths and behaviors for when we don't detach the child are
132890 	The guiding principle for this patch is that all threads of the vforking
132903 	   This is the thread that will be waiting for vfork-done.
132961 	that inferior is waiting for a vfork-done event.  Subsequent patches
132962 	will need to know which thread precisely is waiting for that event.
132970 	the parent process is waiting for its vfork child to exec or exit, we
132972 	actually waiting for a vfork-done event anymore.  And since that flag is
133018 	a separate debug file was passed as the objfile for a shared library
133020 	also be passed for TLS variables in the main executable.  In addition,
133029 	The previous patch added support for the DWARF prologue-end flag in line
133045 	gdb: Add support for DW_LNS_set_prologue_end in line-table
133046 	Add support for DW_LNS_set_prologue_end when building line-tables.  This
133056 	The need for this support came from a problematic usecase generated by
133068 	Looking at the line-table for this location, we have:
133079 	For comparison, let's look at llvm-dwarfdump's output for this CU:
133106 	This commit proposes to add support for the prologue_end flag in the
133132 	indicate that the is_stmt flag should be set for this particular record.
133133 	As a later commit will add support for new flags, instead of adding a
133134 	parameter to record_line for each possible flag, transform the current
133139 	this would require a lot of changes across the codebase for no practical
133224 	sim: fixes for libopcodes styled disassembler
133255 	The clients still have a global for the current process.  That is,
133286 	and a new type that holds exactly what's needed for the Windows code.
133297 …breakpoint.c:377:11: runtime error: load of value 999, which is not a valid value for type 'bptype'
133336 	token to represent other ".<identifier>" forms.  However, for
133345 	Implement completion for Ada attributes
133346 	This adds a completer for Ada attributes.  Some work in the lexer is
133358 	field names for some sub-expression, or tag names (like "enum
133359 	something").  The data for each kind was combined in single structure,
133364 	responsible for implementing completion.  This way, new completion
133368 	objects are defined for use by the completion code.  This moves much
133373 	Enable "set debug parser" for Ada
133377 	Because this is rarely useful, and pretty much only for maintainers, I
133493 	This commit adds partial support for disassembler styling in the i386
133518 		created_styled_output for i386 based targets.
133535 		created_styled_output for riscv.
133564 	I don't currently have a plan for converting every single target
133589 	people to suggest new colors, or wait for this commit to land, and
133595 	for now.
133600 		* doc/binutils.texi (objdump): Describe --disassembler-color
133641 	I found another more place that still had a workaround for Python 2.
133660 	The KFAILs are setup for pre-gcc-12, but apparantly the fix has been
133676 	gdb: add support for Fortran's ASSUMED RANK arrays
133683 	for this tag has been added to dwarf2/read.c.
133689 	responsible for resolving each rank of the array, while the now outer
133690 	resolve_dynamic_array_or_string is responsible for figuring out the
133714 	Finally, support for assumed rank arrays was only fixed very recently
133715 	in gcc, so you'll need the latest gcc in order to run the tests for
133791 	In the next commit this is going to change.  As we add support for
133819 	This allows for a small cleanup, replacing an if/then/else with an
133837 	passed as the testname for the second build_executable_own_libs call.
133839 	mistake, the 'test' variable is setup for the previous test.  I
133870 	The reason for this is the ordering of build rules and make variables
133895 	the etags program ends up looking for these files in the wrong
133980 	Notice that initially, the windows were balanced, 8 lines each for the
133996 	out the delta in increments of 1 to each window (except for the window
134020 	The problem is that the maximum height is restricted, for the cmd
134076 	for example, 'list main', then we see corruption in the cmd window as
134083 	sizes for all windows within a tui_layout_split.  However, there's a
134084 	special case for the cmd window.
134110 	a completely different placement for the cmd window, instead of sizing
134112 	understand this though, and tried to retain the full width for the cmd
134122 	The fingerprint for a layout is represented as a string, the string is
134232 	later commit, so, for now, we're accepting the 20 lines.
134302 	changes are huge, it's just a line or two (or column for width) moved
134372 	Now, hopefully, the code shouldn't look like it only applies for
134426 	Given that we already have 'winheight' and have done for years, it
134436 	wrong during resizes, off by 1 type things.  This is true for height
134447 	really needed for winheight, as there are always multiple windows on
134451 	As for the changes in gdb itself, I've mostly just taken the existing
134471 	only reach for vertical layouts, so the new code is not actually being
134482 	and makes it easier for a later commit to add a new
134493 	Having them at the top level means less typing for the user, which is
134499 	e.g. I'll make 'layout' an alias for 'tui layout'.
134504 	for example, the help output, e.g.:
134583 	to do it for gdb.
134624 	Use pseudosections for NT_FREEBSD_X86_SEGBASES core dump notes.
134626 	as support for writing out a core dump note from a pseudosection.
134631 		* elf.c (elfcore_grok_freebsd_note): Add pseudosections for
134639 	Recognize FreeBSD core dump note for x86 segment base registers.
134641 	and %gs segments for both i386 and amd64 core dumps.  It is primarily
134661 		* elf.c (elfcore_grok_freebsd_note): Remove checks for namesz.
134803 	info symtabs".  If you are looking for a given CU in the list, that's
134806 	it is for debugging purposes (and "maint info symtabs" exists for
134904 …45:31: runtime error: member call on misaligned address 0xbebebebebebebebe for type 'struct builds…
134924 	C++, but I am going for the obvious fix here).
134947 	2. Enable PKU for x32 to fix:
134963 	is the current inferior.  The vfork-done event we receive could be for
134964 	any inferior.  If the vfork-done event is for a non-current inferior, we
134976 	in the test for more details.
134992 	    No unwaited-for children left.
135031 …  [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target extended-remote
135032 …  [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target extended-remote
135033 …  [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target extended-remote
135055 …  [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target extended-remote
135056 …  [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target extended-remote
135057 …  [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target extended-remote
135098 	      [threads] wait_for_event_filtered: exit (no unwaited-for LWP)
135130 	we will eventually get thread exit notifications for both of our
135137 	exit event for it.  Here's the GDBserver logs with the fix applied:
135227 	aarch64: Relax check for RNG system registers
135252 	the reason for stopping all threads.  This helped me understand the
135269 	doesn't seem tested at all (at least, I don't find it if I grep for "Can
135270 	not resume the parent process").  Add a simple test for that.
135276 	Accept the + character as part of filenames for MRI scripts.
135288 	 3303 |   for (char *arg : built_argv)
135302 	gdb/testsuite: add tests for Term
135304 	bug in the handling of a CSI, but I had no way to know for sure.  So I
135305 	thought it would be useful to have unit tests for the handling of
135349 	new code.  This patch arranges for the QUIT macro to only work on the
135380 	Fix for MUL instruction on the v850
135422 	There is no longer any need for ui_out_flag::unfiltered_output --
135479 	implementation remains in utils.c for the time being, because there
135494 	  I investigated all such calls by searching for:
135501 	    save_trace_state_variables.  These are used for "save" commands
135562 	Only have one API for unfiltered output
135580 	be replaced by a scoped assignment to pagination_enabled, but for the
135587 	might be weird for an annotation-based UI to use the pager, it's not,
135655 …[infrun] maybe_set_commit_resumed_all_targets: not requesting commit-resumed for target native, no…
135656 	  [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target extended-remote
135691 	are waiting for a stop event that will never happen.  The PID in
135698 	     threads, use the magic number.  */
135750 	issue for which the above commit is part of the solution.
135755 	present, and this is only true for readline 8+.  With readline 7 the
135791 	What we're checking for is that symbols 'foo' and 'bar' show up in the
135792 	correct inferior, and that (as this test is for a Python API feature),
135841 	If the frame cache is deleted for any reason then the frame_info
135845 	This was leading to random test failures for some folk, see:
135866 	here a 2nd time for the same "addr". And indeed passing the same address
135867 	twice on addr2line's command line would resolve the function for the 2nd
135868 	instance, but not for the 1st (if this code path is taken). (This,
135871 	binaries, for example.)
135873 	gas/Dwarf: special-case .linefile only for macros
135877 	"invocation" point which may be of interest to record (for, as said
135914 	Add Rust parser check for end of expression
135924 	Currently, timestamps for logging are done by looking for the use of
135930 	It seems better, instead, for timestamps to be a property of the
135933 	This patch changes gdb to use the new timestamped_file for gdb_stdlog
135973 	whether this is even useful for MI.
135989 	I didn't write a standalone test for this as it seemed excessively
136011 	code.  (It's hard for me to be completely certain.)  The bug is that
136045 	to be a method of this type.  This is a preparatory refactoring for
136095 	contains a path (but not using the clipped value for anything else),
136140 	  Downloading 7.5 MB separate debug info for /lib/libxyz.so.0
136143 	transfer.  However this header is not guaranteed to be present for
136205 	still a lot for me to learn here.
136254 	Now, we look for the first command output with no regard to what is
136255 	before, or after the command.  Then we look for the first mi prompt to
136283 	for ctf_write_mem, with thresholding, and once each for
136378 	This is a little fiddly.  We relied on compiler assistance for data
136382 	Rather than wait for a suitably adjusted compiler that does the same for
136409 	The test for -gctf support in the compiler is used to determine when to
136415 	So, instead, ask the compiler to emit assembler output and grep it for
136418 	support for non-ELF platforms that don't dot-prepend their section
136453 	Support for Python 2 is a maintenance burden for any patches touching
136460 	See this thread for an example:
136483 	configure code that checks for Python, so I kept that for later.
136492 	an equate of a register (or resolved to reg_section for any other
136512 	Perhaps right from its introduction in 4d1bb7955a8b it was wrong for
136515 	That's relevant only for all other callers of parse_register().
136521 	registers, i.e. fully matching what parse_register() needs it for).
136535 	No need to emit the same string a 2nd time for file 1 in this case.
136542 	(indicating that part of the comment was wrong). Finally for there to be
136589 	lot of effort for little gain to actually support this.
136596 	the course of determining the values for the respective formal
136605 	intended to mean; elsewhere (e.g. for .ascii) it represents two
136612 	make sense when taking into account that for quite a while gas has been
136689 	trace about why a test run doesn't support spawning for attach.
136699 	Add support for hardware breakpoints/watchpoints on FreeBSD/Aarch64.
136702 	ptrace op, use an unordered_set<> to track the "dirty" state for
136721 	fbsd-nat: Add helper routine to fetch siginfo_t for a ptid.
136726 	This class includes platform-independent target methods for hardware
136731 	register holding the address for a breakpoint hit must be fetched in a
136743 	Move non-Linux-specific support for hardware break/watchpoints from
136753 	  debug register changes for a given debug register state.  This does
136754 	  not use the indirection of a 'low' structure as is done for x86.
136756 	- The handling for kernel_supports_any_contiguous_range is not
136758 	  this could perhaps be implemented as new 'low' routines for the
136779 	Add an x86_fbsd_nat_target mixin class for FreeBSD x86 native targets.
136783 	While here, remove #ifdef's for HAVE_PT_GETDBREGS in FreeBSD-specific
136792 	exist for a given process rather than creating new state.
136797 	Remove USE_SIGTRAP_SIGINFO condition for FreeBSD/x86 debug regs support.
136842 	architecture for the current inferior.  However, a user can also
136847 	In order to format an address for a different inferior.
136851 	In py-arch.c I extended arch_object_to_gdbarch to add an assertion for
136907 	PR gdb/27570: missing support for debuginfod in core_target::build_file_mappings
136918 	If there is a mismatch, attempt to query debuginfod for the correct
136924 	needed for core file generation so debuginfod queries will slow down
136929 	gdb: Add soname to build-id mapping for core files
136934 	soname to build-id for each shared library referenced in the core file.
136937 	libraries for core files and to facilitate downloading shared libaries via
136944 	TARGET_WAITKIND_STOPPED, but instead some event for which there's a
137053 	Notice that for both of these probes, the first argument is a uint64_t
137134 	The first approach I considered for solving this problem was to try
137150 	like we already do in stap_parse_register_operand.  But, for x86
137152 	name, then do the default action to read the register.  Finally, for
137161 	using vector registers for probe arguments, those architectures would
137166 	different target description, with different field names for xmm
137220 	consider how to generate an agent expression for the new operation
137238 	  Enter actions for tracepoint 1, one per line.
137267 	otherwise failing. But thinking about it, reporting overflows for
137292 	then calls the pretty printer, and uses the saved pointer for different
137329 	   wasn't overridable, and was a bit misnamed for the new purpose.
137363 	Add support for readline 8.2
137374 	Move the csr-check and arch items inside the table for the .option directive.
137391 		* read.c (read_a_source_file): Calculate known size for sbuf
137401 	This commit a new section for the next release branch, and renames
137426 	  *  disas-jirl-32.d: New test case for LoongArch32.
137427 	  *  disas-jirl-32.s: New test case for LoongArch32.
137429 	  *  macro_op_32.d: New test case for LoongArch32.
137430 	  *  macro_op_32.s: New test case for LoongArch32.
137509 	LoongArch: Use functions instead of magic numbers.
137510 	  Replace the magic numbers in gas(tc-loongarch.c) and
137540 	The motivation for this patch is the fact that py-micmd.c doesn't build
137557 	Python object for this.
137580 	   rather than waiting for insert_mi_cmd_entry to fail.  Change the
137626 	Implement gdbarch_stack_frame_destroyed_p for aarch64
137660 	but it's also worth noting that this test passes for aarch64 in some
137690 	common one), this is good enough for all templates we have, or which
137701 	no pairs of operands to check for consistent size.
137704 	Like for AVX512VL we can make the handling of operand sizes a little
137714 		* elfxx-riscv.c (riscv_multi_subset_supports): Add handling for
137737 		* elfxx-riscv.c (riscv_multi_subset_supports): Add handling for
137742 		* config/tc-riscv.c (riscv_ip): Add handling for new operand
137743 		type 'f' (32-byte aligned pseudo S-type immediate for prefetch
137757 		* riscv-dis.c (print_insn_args): Add handling for new operand
137766 		as for a non-reg_section symbol.  Simplify array bounds check.
137815 	The cases for TARGET_OBJECT_LIBRARIES and TARGET_OBJECT_LIBRARIES_AIX
137817 	TARGET_OBJECT_SIGNAL_INFO) if gdbarch methods for the requested data
137823 	gdb: Remove support for S+core
137824 	GCC removed support for score back in 2014 already.  Back then, we
137836 	Add another test for Ada Wide_Wide_String
137852 		has set module->func_table for DST__K_RTNEND.  Check return
137882 	${target} in configure.ac should be the canonical target, so that for
137943 	only for documentation purposes (and slight reducing of overhead), as
137949 	There's no need for the arbitrary special "unknown" token: Simply
137963 	extensions can be enabled via .arch for IAMCU, and that the base
137980 	- avoid calling the function for extentions (which would never have the
138020 	is not present in this version of readline, see below for why.
138025 	for GDB is that the escape sequence to disable bracketed paste mode
138026 	includes a '\r' character at the end, see this thread for more
138131 	Reimplement array concatenation for Ada and D
138132 	This started as a patch to implement string concatenation for Ada.
138135 	concat_operation: Ada and D.  So, in addition to implementing this for
138142 	eval_op_concat has code to search for an operator overload of
138147 	dead for a very long time.  This patch removes it and hoists the
138153 	Ada support for wide strings
138154 	This adds some basic support for Wide_String and Wide_Wide_String to
138176 	Powerpc fix for gdb.base/ending-run.exp
138180 	looks as follows for the test case:
138183 	at the closing bracket for main.  The message printed is:
138194 	The test fails as the output does not match any of the options for the
138211 	Type "apropos word" to search for commands related to "word"...
138232 	"normal" output for Powerpc when the debug-info is not available.
138244 	dlltool: Use the output name as basis for deterministic temp prefixes
138375 		AC_SUBST for -Wno-format-truncation.
138376 		(GPROFNG_NO_SWITCH_CFLAGS): New AC_SUBST for -Wno-switch.
138393 		New AC_SUBST for -Wno-nonnull-compare.
138401 	Define ATTRIBUTE_FALLTHROUGH to __attribute__ ((fallthrough)) only for
138451 	I think it would be useful for readelf to be able to display the content
138457 	Add configury to binutils to optionally check for the msgpack C library
138496 		* configure.ac: Add --with-msgpack flag and check for msgpack
138548 	The flags for the "HSA" OS ABI are properly versioned and documented on
138551 	encode their flags the same way as HSA v3.  For example, for PAL:
138555 	So for those other OS ABIs, we read them the same as HSA v3.
138561 		(get_machine_flags): Handle flags for EM_AMDGPU machine type.
138597 	There isn't an actual opcodes implementation for the AMDGCN arch (yet),
138615 	Add support for the AMDGCN architecture to BFD.
138631 	The ELF format for this architecture is documented here:
138635 	The flags for the "HSA" OS ABI are properly versioned and documented on
138638 	encode their flags the same way as HSA v3.  For example, for PAL:
138676 	Updated Serbian (for binutils/) and Russian (for gprof/) translations
138755 	As for PowerPC64, move instructions to the main opcode table.
138808 		to operand->insert for PPC_OPERAND_PLUS1 when calculating mask.
138855 	install for users who already have an earlier one installed.
138871 	doing, we're checking either for the regexp, or for no output, hence
138886 	gprofng: Add a configure test for clock_gettime and a use of the test in getthrtime.c
138925 	similarly to what is possible for Python CLI commands.
138927 	A new subclass of mi_command is defined for Python MI commands,
138929 	for Python MI commands.
139038 	also (IMHO) risky, its too easy for someone to later add a use of the
139052 	I have also changed how the memory is managed for the command name.
139056 	the memory for the name.
139059 	hold the memory for the name within the Python object, as the lifetime
139067 	install (make the command available for use) and uninstall (remove the
139087 	mentioned - we already generate comments for some fields saying that
139096 	  "Otherwise, the check is done against 0 (really NULL for function
139110 	 True, this should perform a check for the field of gdbarch still
139130 	believe the only one of these that is required to be set for all
139133 	And so, for all of the other fields, I've changed the property
139140 	validation, in which case, it is find for an architecture to not set
139144 	this commit.  Certainly for all fields except register_type, all I've
139155 	gdb/gdbarch: remove the predicate function for gdbarch_register_type
139159 	everywhere it is used, for example in
139162 	My claim is that the gdbarch_register_type function is required for
139167 	gdbarch-components.py for the 'register_type' field, and regenerate
139198 	the case.  In Ada, for example, one has subranges of character and
139208 	When running gdb.cp/non-trivial-retval.exp, the following shows up for
139222 	fetch a pointer to the memory location from X8 for aarch64 and r0 for armhf.
139236 	contents of this struct correctly. This has always been incorrect for
139268 	rustc changed to emit a bit more debug info for unsized types.
139288 	    | warning: Could not load shared library symbols for /lib64/ld64.so.1.
139298 	other hand, it is what was asked for -- while the test does set
139314 	I don't have a good setup for testing this using dejagnu, so I don't
139425 	Same as the previous patch, but for GDBserver.
139431 	won't get an event for that exit (which we won't in some scenarios,
139435 	though for the (real) parent process, the exit code that counts is the
139438 	Like for GDB, the solution here is to:
139440 	   - only report whole-process exit events for the leader.
139453 	event for that exit (which we won't in some scenarios, but not in this
139464 	   threads, and then waits for two stop or exit events, one for each
139469 	   waiting for a second event that will never come.
139472 	exiting, as opposed to just the leader (with pthread_exit(), for
139473 	example), we _will_ get an exit event shortly for the leader, after we
139475 	another way, we _always_ get an event for the leader after we see it
139481 	report the whole-process exit status for the leader thread, not for
139483 	(or exec) event for the leader, and when the race triggers, we're not
139488 	I thought of making GDB call waitpid/WNOHANG for all non-leader
139490 	would be an exit event pending for each of them waiting to be
139494 	hit that race window all the time, which avoided trading one race for
139496 	help either, the threads are still in running state for a bit, for the
139500 	stop and wait for the stop for each of the non-leader threads.  For
139509 	to convince myself that this would really work (and it would, for the
139510 	scenario I considered), that I realized I had failed to account for
139539 	all the handling for events for LWPs not in the LWP list is together.
139550 	handling for events for LWPs not in the LWP list is together.  This
139560 	If we make GDB report the process EXIT event for the leader thread, as
139576 	for the leader thread before reaping the other thread, because in
139581 	exercising plays out.  Also, run the program to completion for
139591 	added as a fix for
139603 	If we make GDB report the process EXIT event for the leader thread,
139610 	This is a testcase race -- the main thread does not wait for the
139613 	SIGUSR1.  With the change to make GDB report the EXIT for the leader,
139641 	for the leader thread before reaping the other thread, because in
139645 	Fix it by making the main thread wait for the child to exit.  Also,
139646 	run the program to completion for completeness.
139662 	resulting in, for example:
139680 		* doc/binutils.texi: Document the new options.
139681 		* doc/debug-options.texi: Describe the new options.
139689 		* testsuite/ld-plugin/pr28849.d: Adjust for powerpc64 function
139746 	checking for x86_64-pc-linux-gnu-gcc... gcc
139749 	checking for library containing tgetent... -ltermcap
139750 	checking for readline in -lreadline... no
139797 	gdb: Try searching for auto-load script using .gnu_debuglink
139827 	To fix this, use the debuginfod cache path as the fullname for debuginfod-
139833 	Fix for PR gdb/20684.  When invoking MI commands with --thread and/or
139880 	This caused problems for frontends that provide access to CLI because UI
139881 	may silently change the context for CLI commands (as demonstrated above).
139909 	gdb/testsuite: add new test for comparing char types in Python
139920 	It is worth noting that for any particular compiler implementation (or
139923 	information by using the Type.is_signed property.  However, for
139933 	Add a new read-only property, Type.is_signed, which is True for signed
139936 	This property should only be read on types for which Type.is_scalar is
139937 	true, attempting to read this property for non-scalar types will raise
139949 	Add a new read-only property which is True for scalar types,
139959 	This new option matches the existing option of the same name for the
139989 	To maintain backward compatibility, for the CLI add-inferior command,
139993 	Unfortunately, this same backward compatibility is missing for the MI.
140006 	deprecating it for GDB 12, and then removing it in GDB 13.
140034 	Implement real literal extension for Ada
140097 	byte, it uses a "U" followed by the hex for the character.  So, for
140109 	and for all characters in non-Unicode character sets, lower case is
140135 	Test cases for UTF-8, Latin-1, and Latin-3 are included.  This
140142 	rust-parse.c has a #define for the host-specific UTF-32 charset name.
140144 	to charset.h for easier reuse.
140153 	I looked at all calls to these functions that pass a 1 for the
140163 	string as we go.  This turns out to be useful for a subsequent patch.
140166 	ada-lex.l uses "%option case-insensitive", so there is no need for
140175 	MIPS/opcodes: Fix alias annotation for branch instructions
140176 	Correct issues with INSN2_ALIAS annotation for branch instructions:
140178 	- regular MIPS BEQZ/L and BNEZ/L assembly instructions are idioms for
140181 	- microMIPS 32-bit BEQZ and BNEZ assembly instructions are idioms for
140184 	- regular MIPS BAL assembly instruction is an idiom for architecture
140189 	new entry for BAL for the MIPSr6 ISA, correcting a disassembly bug:
140204 	Parts for regular MIPS BEQZ/L and BNEZ/L instructions from Sagar Patel.
140231 		for "bal", "beqz", "beqzl", "bnez" and "bnezl" instructions.
140232 		* micromips-opc.c (micromips_opcodes): Likewise for "beqz" and
140304 	Downloading 0.01 MB separate debug info for /tmp/system-supplied DSO at 0x7ffff7fc9000
140309 	Downloading 0.01 MB separate debug info for system-supplied DSO at 0x7ffff7fc9000
140328 	GDB prints the wrong type for typedefs in case there is another typedef
140329 	available for the same raw type (gdb/16040).  The reason is that the
140333 	The original output of GDB for a program like
140414 	RISC-V: make .insn actually work for 64-bit insns
140426 	to this one, and is run uniformly for all ELF targets anyway.
140456 	Adjust ld ctf test for 32-bit targets
140458 	0x4" for this test.
140476 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 0: can spawn for attach (got interactiv…
140477 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 1: can spawn for attach (got interactiv…
140478 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 2: can spawn for attach (got interactiv…
140479 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 3: can spawn for attach (got interactiv…
140480 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 4: can spawn for attach (got interactiv…
140481 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 5: can spawn for attach (got interactiv…
140482 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 6: can spawn for attach (got interactiv…
140483 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 7: can spawn for attach (got interactiv…
140484 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 8: can spawn for attach (got interactiv…
140485 …FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 9: can spawn for attach (got interactiv…
140492 …(gdb) FAIL: gdb.base/gdb-caching-proc.exp: can_spawn_for_attach: 0: can spawn for attach (got inte…
140506 	r_offset final addresses calculated in ppc64_elf_size_stubs for use by
140523 	configure: Stop checking for PT_GETXMMREGS.
140540 	FreeBSD recently added a real vDSO in its shared page for the amd64
140545 	via the kinfo_getvmmap function for native targets (fetched from the
140549 	finding symbols for the vdso:
140551 	warning: Could not load shared library symbols for [vdso].
140558 	when generating code.  'sh' is unavoidable for build-time generation,
140559 	but for other things, let's use Python.
140599 	only really useful for in-tree builds anyway -- out-of-tree I simply
140661 	It is better to make can_spawn_for_attach to return false for this case.
140690 	The patch series "gdb: Add basic support for LoongArch" has been
140742 	message for the "During startup..." error message when running with gdbserver.
140746 	for the later).  This should make the log output clearer about why the test failed.
140778 	bracket sequences.  This patch adds support for these for character
140780 	types, so for the time being these continue to be excluded -- but an
140795 	encoding, which is used for characters outside the base plane.
140798 	value for an enum character constant:
140836 	for the thread, or None, if target_extra_thread_info returns nullptr.
140839 	this attribute is only really useful for echoing straight through to
140874 	ERROR: failed to extract expected results for lbound
140892 		* config.bfd: Update error message for obsolete configurations.
140964 	Additionally debuginfod is not needed for gdb-add-index since the
140972 	gdb: add operator+= and operator+ overload for std::string
140973 	This commit adds operator+= and operator+ overloads for adding
140978 	I've also added a self test for gdb::unique_xmalloc_ptr<char>, which
141014 		 surely removed for MI3, and may be removed even earlier.  */
141062 	RISC-V: Fix mask for some fcvt instructions
141074 	This patch adds support for wild template parameter list matches, similar
141130 	Unit tests for strncmp_iw_with_mode
141131 	This patch attempts to make a start at adding unit tests for
141165 	Thanks to Andrew for writing the test case.
141214 	for me on Ubuntu 20.04 amd64.
141220 	gdb: use a range based for loop when iterating over an array
141221 	Make use of a range based for loop to iterate over a static global
141234 	previously accounted for: to signal the WIFSTOPPED condition in the
141253 	test does not expect (my bad for not testing before pushing).
141264 	The test passes on FreeBSD, because the test looks for four hex numbers
141294 	for (a non-NULL terminated view on a string).  No changes in behavior
141307 	comparing two overloads, one might be better than the other for
141411 		used to return the extension string for each INSN_CLASS_*.
141424 	Currently we report errors as "invalid CSR 'fscr' for the current ISA"
141429 	'fscr' for the current ISA, CSR 'fscr' needs 'f' extension".
141459 	different versions of debug specs for now, so only supporting the latest one is
141493 	* Testcases for most CSRs added on the Privileged
141534 	RISC-V: Reorganize testcases for CFI directives
141554 	inf-ptrace: Add an event_pipe to be used for async mode in subclasses.
141562 	async_file_mark) for use in target methods such as async.
141575 	the threads were running (for example when using schedule-multiple=on
141584 	since it is helpful for debugging async target support and not just
141601 	WNOHANG and uses sigsuspend() for synchronous operation.
141614 	  pipe for an event that has already been reported.  If the event was
141622 	Previously this returned a TARGET_WAITKIND_SIGNALLED event for
141645 	  no unwaited for children (either they have exited or are stopped).
141648 	  do_target_resume before waiting for the next event.
141704 	gdb: fix detection of compilation and linking flags for source-highlight
141755 	- Use `*ext` rather than `*ext != NULL` for checking is reach end of
141823 	While this is not the case for true MI command:
141830 	Less output makes for simpler patterns to match against.
141834 	between.  This is not really needed, for the first command I can look
141835 	for just the ^done,value="\"FIRST COMMAND\"" string, then I can start
141836 	looking for the output of the second command.
141871 	We already have some protection for this case, look (in
141874 	complaint.  However, for whatever reason, in both 'f' and 'F'
141891 	I don't have any tests for this change, I have no idea how to generate
141892 	weird stabs data for testing.  The original binary from the bug report
141901 	where making use of std::string would remove the need for manual
141915 	gdb: Only paginate for filtered output in fputs_maybe_filtered
141917 	fputs_unfiltered) ended up triggering pagination.  The backtrace for this was:
141922 …#26 0x0000558394587454 in gdb_readline_wrapper (prompt=0x7ffd907712d0 "--Type <RET> for more, q to…
141984 	Fix typo in ld.texi
141986 		* ld.texi (Output Section Type): Fix typo in @code syntax.
141999 	Updated Serbian translations for the bfd, gold, ld and opcodes directories
142018 	    * ld.texi: Document new output section type.
142041 	Much of the gas source and older BFD source use "long" for function
142045 	all that is required.  Due to allowing longs, it was possible for
142075 	pei-aarch64-little apparently lacks support for BFD_RELOC_RVA.
142136 	i386: Update I386_NEED_DYNAMIC_RELOC_TYPE_P for DT_TEXTREL
142137 	Update I386_NEED_DYNAMIC_RELOC_TYPE_P to allow R_386_TLS_IE for relocation
142157 	wasn't set for other than the primary target, which means
142160 	"global_cc_os": no such variable" when e.g. configuring for
142186 	It is possible for a compiler to optimize a function in a such ways that
142194 	  > conventions, and it may not be safe for the debugger to call this
142199 	returned, and so on.  For this reason, it is unsafe for GDB to try to do
142211 	Note that it is still possible for someone to use a vendor specific
142212 	value for the DW_AT_calling_convention attribute for example to indicate
142240 	x86-64: Use MAXPAGESIZE for the relro segment alignment
142249 	to use MAXPAGESIZE for the end of the relro segment alignment, like other
142302 	Unfortunately, compilation failures for C tests run by the
142310 	program can find itself.  It's undecided whether argv[0] for
142315 	for this commit.
142323 	sim: Add sim_dump_memory for debugging
142334 	broke for the "primary target", like when testing a release-tarball.
142340 	"sim: testsuite: setup per-port toolchain settings for multitarget
142343 	for single-target builds, as set up by the toplevel Makefile.
142348 	step, for each X to find a value for $(<X>_FOR_TARGET).  N.B.: in-tree
142355 	pointing out that the variable may be empty).  If it hadn't been for
142360 	actually used by sim at test-time, for the "primary target".
142362 	Using $(CC) for "example-" targets CC_FOR_TARGET is not changed, as
142381 	commit 34cf51120683, building for cris-elf fails as
142384 	A cris-elf simulator configured for --enable-sim-hardware
142404 	simoption --cris-900000xx" for all tests using that option.
142405 	This allows a clean test-suite-run for a build with
142423 	The immediate need was to check for presence of a simulator
142445 	outputs.  Curiously, that doesn't happen for the other
142456 	sim/testsuite/cris/c: Use -sim3 but only for newlib targets
142457 	Commit a39487c6685f "sim: cris: use -sim with C tests for cris-elf
142458 	targets" caused " -sim" to be appended to CFLAGS_FOR_TARGET for
142462 	the baseboard-file cris-sim.exp uses "-sim3" so for consistency use
142466 	checks" caused " -sim" to be appended for *all* targets, which just
142467 	doesn't work.  For example, for crisv32-linux-gnu, that's not a
142471 	While cris-sim.exp appends "-static" for *-linux-gnu, further changes
142477 	continuing test-run (possibly for other targets).
142481 		with " -sim3", but do it conditionally for newlib targets.  Save
142504 	in run_sim_test, mentions progos as intended only for C
142509 	Allowing it to be used for assembler tests makes it usable
142510 	for e.g. an always-false predicate and in expressions in
142513 	With this patch, global_cc_os is set to "", just as for "unknown OS".
142521 	sim/testsuite/cris: Assembler testcase for PRIx32 usage bug
142522 	Several C test-cases exposed the bug, but let's have one for
142540 	for some C programs, like some of the ones in the sim/cris/c
142581 	This commit moves the two Python functions that are used for styling
142585 	The motivation for this change is purely to try and reduce the clutter
142597 	I propose in this patch could break things for that user, however,
142618 	extension language hook, which is then implemented for Python.  This
142619 	hook is very similar to the existing hook for source code
142625 	performed identically for all architectures.
142640 	escape sequences, though I don't check for specific colours; the
142654 	I don't know how much of an issue this will be for people.  There's
142655 	already some precedent for this in GDB when we look at source styling.
142732 	hardware paging is always COMMPAGESIZE of 4k.  Use COMMONPAGESIZE for
142758 	The linker's MAXPAGESIZE variable gives the page size for these layout
142765 	address 0x10000 and data at 0x20000 for a total of two 64k memory
142775 	pages for a data segment of 1k!  If the data segment instead started
142784 	the dynamic loader.  Page granularity for memory protection means that
142796 	MAXPAGESIZE on x86 is for reasons other than the demand paging and
142801 	Always end the relro segment on a MAXPAGESIZE boundary, except for
142806 	fixed address mod MAXPAGESIZE.  So for relro the linker can't play
142811 	plus one page, it was sometimes introducing page gaps for no reason.
142869 		shared libraries for GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS.
142897 	This adds initializers to bound_minimal_symbol, allowing for the
142902 	gdb/fortran: support ptype and print commands for namelist variables
142914 	This commit is to make the print and ptype commands work for namelist
142935 	would fail for this reason.
142940 	  10:	for (i = 0; i < 10; ++i)
142975 	for a different source line.  As a result, GDB stops and returns
143020 	allow for the new output format.
143031 	This commit adds Makefile, configure and NEWS for LoongArch.
143034 	This commit adds initial native Linux support for LoongArch.
143037 	This commit adds initial Linux target support for LoongArch.
143040 	This commit adds initial baremetal support for LoongArch.
143043 	This commit adds initial target description support for LoongArch.
143048 	It's not clear what this was meant for, but it's not used by anything,
143053 	gdb/linux: remove ptrace support check for exec, fork, vfork, vforkdone, clone, sysgood
143054 	I think it's safe to remove checking support for these ptrace features,
143062 	to test whether ptrace reports an event for the fork by the child.  This
143104 		headers if there is an extension field for e_phnum in first
143129 	Add a test for commit 7c4643efe7be, which fixed --only-keep-debug for ELF
143141 	RISC-V: Stop reporting warnings for mismatched extension versions
143187 		* testsuite/ld-elf/pr24718-1.d: Don't xfail for hppa64.
143246 	we do for all the styling tests.  I'm now running all of the C tests
143306 	without waiting for and answer to each command, eclipse plans to
143315 	observe, and (for me at least) I'm happy that what I'm seeing, if a
143367 	wait for more input to arrive.
143382 	aiming for is to have the first command be longer than glibc's
143385 	However, for this discussion, lets imagine that glibc's buffer is just
143440 	for mi commands, and is a consequence of this commit:
143445 	      Fix for using named pipes on Windows
143448 	times, once each for stdin, stderr, and stdout.  After this commit we
143449 	open the tty just once and reuse the FILE object for all three roles.
143460 	file.  To correct for this glibc tries to do an lseek call to
143495 	However, I've not done that in this commit for a couple of reasons:
143514 	The test for this issue sends two commands in a loop, with the first
143528 	than I see on my real hardware; glibc asks for 1024 bytes, but only
143538 	So, for testing, I check cases where the first command is just a few
143540 	characters.  Hopefully, this should mean we hit the problem case for
143544 	mentioned earlier.  That commit was intended to provide support for
143554 	same FILE for in, err, and out streams.  In contrast, in a vanilla C
143555 	program, I would expect different FILE objects for each stream.
143571 	will not print anything (used for figuring out the length of
143624 	but this does not work for all the streams.  In particular, CLI
143652 	'normal_stop', that can be used for checking if printing normal stop
143661 	Convert the suppress_notification flag for the CLI from int to bool.
143718 	Add a getter and a setter for a symbol's line.  Remove the corresponding macro
143726 	Add a getter and a setter for a symbol's type.  Remove the corresponding
143734 	Add a getter for a whether a symbol is a C++ template function.  Remove
143742 	Add a getter and a setter for whether a symbol is inlined.  Remove the
143750 	Add a getter and a setter for whether a symbol is an argument.  Remove
143758 	Add a getter and a setter for whether a symbol is objfile owned.  Remove
143766 	Add a getter and a setter for a symbol's domain.  Remove the
143779 	Add a getter for a symbol's "impl".  Remove the corresponding macro and
143787 	Add a getter and a setter for a symbol's aclass index.  Remove the
143831 	Add a getter and a setter for a symtab's language.  Remove the
143839 	Add a getter and a setter for a symtab's linetable.  Remove the
143847 	Add a getter and a setter for a symtab's compunit_symtab.  Remove the
143859 	Add a getter and a setter for a compunit_symtab's macro table.  Remove the
143867 	Add a getter and a setter for a compunit_symtab's epilogue unwind valid flag.
143875 	Add a getter and a setter for a compunit_symtab's locations valid flag.
143883 	Add a getter and a setter for a compunit_symtab's block line section.  Remove
143891 	Add a getter and a setter for a compunit_symtab's blockvector.  Remove
143899 	Add a getter and a setter for a compunit_symtab's dirname.  Remove the
143907 	Add a getter and a setter for a compunit_symtab's producer.  Remove the
143915 	Add a getter and a setter for a compunit_symtab's debugformat.  Remove
143925 	over all filetabs, for example, those cases would use compunit_filetabs,
143982 	gdb: add getter/setter for compunit_symtab::objfile
143991 	Rust 1.53 (quite a while ago now) ungated the support for non-ASCII
144014 	new exp_opcode enumeration constant just for this.  IMO this doesn't
144189 	gdb/doc: update docs for 'info win' and 'winheight' commands
144190 	This started by noticing that the docs for 'winheight' are out of
144196 	valid names for themselves at run time (by using 'info win').  That,
144200 	Finally, I noticed that the docs for 'win info' don't explicitly say
144236 	Don't abort for undefined symbol when finishing DT_RELR.  Instead, skip
144244 	Tweak assembler invocation for pr28827-1 test
144252 	for PR28743 (commit 2f83249c13d8 and c804c6f98d34).
144270 	Detect .eh_frame_hdr earlier for SIZEOF_HEADERS
144271 	Current code detects the need for PT_GNU_EH_FRAME using a field set by
144287 	sim: mips: Add simulator support for mips32r6/mips64r6
144311 		(load_word): Allow unaligned memory access for MIPSR6.
144318 		(nal, beq, bal): New definitions for *r6.
144324 		(check_fpu): Select IEEE 754-2008 mode for R6.
144358 		* hilo-hazard-3.s: Skip for mips*r6.
144373 	sim: Add partial support for IEEE 754-2008
144378 		(sim_fpu_max): Add variant behaviour for IEEE 754-2008.
144417 	This used to be controlled by a macro that was only defined for MIPS.
144434 		for legacy MIPS.
144478 	alias for a CORE_ADDR) that includes the address of the code entry in
144494 	for this.
144635 	treat SHN_ABS symbols for cases like glibc's _nl_current_LC_CTYPE_used
144645 		(ppc64_elf_edit_toc): Don't remove entries for absolute symbols
144647 		(allocate_got): Don't allocate space for got relocs against
144651 		(ppc64_elf_size_dynamic_sections): Likewise for local got.
144653 		(ppc64_elf_size_stubs): Don't allocate space for relr either.
144679 		* dwarf2.c (read_section): Change the heuristic that checks for
144684 	gdb: fix formatting for help set/show extended-prompt
144685 	The formatting of the help text for 'help set extended-prompt' and
144698 	Notice that the line for '\[' is indented more that the others.
144728 	While working on the fix for PR cli/28665 (see previous couple of
144730 	code.  Specifically, I was thinking about whether the spec_string for
144759 	here, see the commit message for the previous commit.
144765 	So, that's what this commit does.  I've also added some tests for this
144804 	However, parse_linespec is not intended to be passed a nullptr, for
144843 	I've reused the same "Junk at end of line specification." error for
144847 	second bug PR gdb/28797 was raised.  This was for a very similar
144863 	check for junk at the end of the line - after parsing (or failing to
144868 	I've added tests for this case too.
144898 	Fix this by checking for the first character of ARG being '\0' before
144908 	This patch came about while I was working on fixes for PR cli/28665
144909 	and PR gdb/28797.  The actual fixes for these two issues will be in a
144915 	Because this patch only changes the nature of the failure for the
144942 	Updated French translation for the ld/ and gold/ sub-directories
144975 	It's better for the rule to fail such that the .c file is not updated.
144977 	handier for debugging syntax errors.
144995 	gdb/python: fix gdb.Objfile.__repr__ () for dynamically compiled code
145070 	gdb, testsuite, fortran: adapt info symbol expected output for intel compilers
145077 	generated appendix for mangling.
145089 	of XXXX over XXXX.NUMBER for info symbol on gfortran symbols.
145093 	other demangler for that matter) and thus printed as is.
145139 	In trying to find a testcase for PR28827, I managed to hit a linker
145141 	being too large for the output .branch_lt.
145189 	objcopy's --only-keep-debug option has been broken for ELF files since
145228 	FreeBSD x86 nat: Use register maps for GP register sets.
145233 	$fs, and $gs) for both 32-bit and 64-bit processes.
145237 	handling (for $fs_base, $gs_base, and XSAVE state) from these files.
145243 	cache the result for the future similar to the way the status of XSAVE
145245 	the proper xcr0 mask (X87-only) for old kernels or systems without
145255 	FreeBSD x86: Use tramp-frame for signal frames.
145259 	frame for both amd64 and i386 and permits fetching additional segment
145272 	Use register maps for gp regsets on FreeBSD/x86 core dumps.
145283 	registers are 16 bits, but the GDB registers for those are 32-bits).
145290 	short registers).  Upcoming patches also require these semantics for
145297 	FreeBSD x86: Remove fallback for detecting signal trampolines by address.
145302 	December 2016.  The fallback only works for native processes and would
145304 	use tramp_frame for signal frames.
145306 	Remove support for pre-5.0 FreeBSD/i386 signal trampolines.
145345 	since I need to juggle with different whitespace settings for different
145349 	Some editors have native support for reading these files, while others
145353 	I added rules for the kinds of files I edit most often, but more can be
145354 	added later.  I assumed that the rules were the same for GDB and the
145365 	Updated French translation for the gas sub-directory.
145374 		for __ehdr_start.
145411 	stub section size is smaller.  The previous larger size is kept for
145563 	useful for GDB to work around this.  I did the obvious simple thing, if
145565 	added a producer check to only apply this fixup for GCC 11.  The idea is
145639 	section offsets will all be the same.  So for those ABIs, it doesn't
145641 	ABI, will have different offsets for the various sections.  Thus, for
145647 	this->get_address (); get_address is a getter for m_address in
145654 	(Thanks to Tom Tromey for this observation.)
145675 	iterated thread in order to set inferior_ptid for a subsequent xfer.
145730 	Updated Swedish translation for the binutils subdirectory
145739 	This commit adds support for source files that contain non utf-8
145760 	is not present for Python 2.
145768 	The problem is the use of PyString_FromString (which is an alias for
145772 	call, but for Python 3 the input is assumed to be a uft-8 encoding
145773 	string for the purpose of the conversion.  And here of course, is the
145790 	for guessing the encoding of the incoming file content, if the
145792 	happens for Python 2 where the incoming content is of `str` type.
145800 	for us, and the colorize API is not part of the documented external
145802 	content being a Unicode string (for Python 3), lets just make the
145804 	responsibility for guessing the encoding.
145852 	gdb/python: improve the auto help text for gdb.Parameter
145853 	This commit attempts to improve the help text that is generated for
145857 	Documentation for a gdb.Parameter is currently pulled from two
145927 	So, I think there's room for improvement.
145929 	With this patch, for the four cases above we now see this:
145961 	  Generic command for setting how things print.
145974 	  Generic command for setting how things print.
145990 	GDB.  As a result, GDB would make use of its "magic" mangling of the
145994 	However, when we added support for the get_show_string method to
145999 	pretty poor, for example, this is GDB before my patch:
146032 	absolute number, for example, if you wanted to show a complete history
146071 	This is simlpy allocating a new array and copying it. However, for
146092 	# Please enter the commit message for your changes. Lines starting
146109 	A common pattern for string_file is to want to move out the internal
146113 	have a dedicated method for that instead and make string_file::string
146129 	reasonable to add a helper function for this situation.
146159 	valid value for an "enum" set/show parameter.
146195 	Python code cannot affect the current language for its own purposes.
146213 	bfd: Make bfd.stamp depend on source bfd.texi
146214 	Make bfd.stamp depend on source bfd.texi to avoid regenerating
146215 	doc/bfd.info for each make run.
146219 		* doc/local.mk (%D%/bfd.stamp): Depend on $(srcdir)/%D%/bfd.texi.
146287 	_filtered calls I could find, as well, for the same clarity.
146336 		(%D%/bfd.texi): Removed.
146337 		(doc/bfd/index.html): Remove -I$(srcdir).  Replace bfd.texi with
146338 		%D%/bfd.texi.
146344 		* doc/local.mk (%D%/bfdver.texi): Add mkdir command.
146354 	gdb/doc: improve description for Window.click on Python TUI windows
146362 	Update Bulgarian, French, Romaniam and Ukranian translation for some of the sub-directories
146494 	build slightly.  It also allows for more parallelism.
146496 	bfd: rename core.texi to corefile.texi
146502 	This unifies boilerplate rules for most files with pattern rules.
146510 	Adjust default page sizes for haiku arm.
146521 	Add markers for 2.38 branch
146554 	Updated Serbian translation for the ld sub-directory
146601 	Add `set print array-indexes' tests for C/C++ arrays
146602 	Add `set print array-indexes' tests for C/C++ arrays, complementing one
146603 	for Fortran arrays.
146608 	Add `set print array-indexes' handling for Fortran arrays.  Currently
146626 	for a 5-element vector and a 5 by 5 array filled with the value of 2.
146630 	Add `set print repeats' tests for C/C++ arrays
146631 	Add `set print repeats' tests for C/C++ arrays, complementing one for
146640 	Implement `set print repeats' handling for Fortran arrays.  Currently
146647 	extra specialization handler method for processing dimensions other than
146682 	for a 5 by 5 array filled with the value of 2.
146685 	behavior and explicitly request that there be no limit for printing
146694 	fbsd-nat: Add include for gdb_argv.
146705 		conditions for rel_count.
146707 		(allocate_dynrelocs): Test for opd and ifunc when allocating
146717 		space for PLT relocs against local syms when enable_dt_relr.
146725 		space for GOT relocs against non-TLS local syms when enable_dt_relr.
146756 	Add remote_debug_printf, and use it for all debug messages controlled by
146774 	Note that "threads" debug is currently used for a bit of everything in
146822 	gdb has some extensions and helpers for working with the libiberty
146846 	clearer and removes some chances for error.  This also enables future
146910 	For pipe based serial connections, this name is only used for
146916 	it easier for a user to understand what is going on.
146920 	gdb: testsuite: print explicit test result for gdb.base/dfp-test.exp
146921 	In the current code, if decimal floating point is not supported for
146927 …gdb/testsuite/gdb.base/dfp-test.c:39:1: error: decimal floating point not supported for this target
146944 	  UNSUPPORTED: gdb.base/dfp-test.exp: decimal floating point not supported for this target.
146977 	that appears to be the case for readelf.  This does the same for
146991 	Makes it a little less likely for someone to break their thin archives.
147008 	relative relocs in check_relocs, allocate space for them and output in
147023 		(ppc64_elf_check_relocs): Init rel_count for global and local syms.
147026 		(allocate_got): Don't allocate space for relative relocs when
147044 		* testsuite/ld-elf/dt-relr-2b.d: Adjust for powerpc.
147051 	tweak __ehdr_start visibility and flags for check_relocs
147058 		def_regular and linker_def for check_relocs.  New function
147098 	for this redundant set of static data.
147101 	There's no real need for the pseudo-boolean "haveindex" or for separate
147130 	gdb.dlang/demangle.exp: update expected output for _D8demangle4testFnZv
147138 	The commit imported the commit 0e32a5aa8bc9 ("libiberty: Add support for
147141 	test for the exact same mangled name:
147196 	decoding of EVEX.L'L for VMOV{L,H}P{S,D} and VMOV{LH,HL}PS.
147198 	x86: consistently use scalar_mode for AVX512-FP16 scalar insns
147203 	consistent for all sufficiently similar insns.
147207 	for modes which occur for insns allowing for EVEX.W to be set (noticed
147217 	Like for AVX512-FP16, there's not that many FP insns where going through
147223 	- vmovshdup used EXx for its 2nd operand, thus displaying seemingly
147226 	- vmovlhps used EXx for its 3rd operand, when all sibling entries use
147227 	  EXq; switch to EXq there for consistency (the two differ only for
147236 	similar %XS and %XD (which subsequently can be used for further table
147265 	Reapply the patch to detect GCC LTO plugin used for libiberty build to
147405 	+	* testsuite/d-demangle-expected: Add test case for function literals.
147409 	+	* testsuite/d-demangle-expected: Add test cases for simple special
147419 	+	* testsuite/d-demangle-expected: Add missing format for new test
147434 	+	* configure.ac: Do not search for sbrk on Darwin.
147468 	 # Please enter the commit message for your changes. Lines starting
147487 	  cc1plus: warning: command line option ‘-Wmissing-prototypes’ is valid for C/ObjC but not for C++
147490 	by the configure check in gdbsupport/warning.m4, but for users of
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
147614 		* testsuite/ld-elf/dt-relr-1.s: Use # for comment.
147623 	up sh_entsize for .relr.dyn output section before reaching the dynamic
147633 	Let's not rely on .init/.fini having relocs for the size sanity check.
147651 	this is wrong, I will look into it later, sorry for that.
147691 	gdb Power 9 add test for HW watchpoint support.
147694 	patch add a test to lib/gdb.exp for Power to determine if the processor
147711 	gdb/testsuite: fix gdb.python/py-events.exp for finding process id
147733 	   regexp that it uses is not tailored for the output printed by the
147763 	ld: Add glibc dependency for DT_RELR
147777 		* ld.texi: Mention GLIBC_ABI_DT_RELR in -z pack-relative-relocs
147822 	be generated and save the relative relocation candidate information for
147857 		tags to DT_RELR, DT_RELRSZ and for compact relative relocation.
147910 		linker for some tests.
147952 		linker for some tests.
147977 	relr.dyn section for DT_RELR.  DT_RELR is implemented with the linker
147991 		.relr.dyn section for DT_RELR.
148001 		* ld.texi: Document -z pack-relative-relocs and
148004 		PIE nor shared library.  Add 3 spare dynamic tags for DT_RELR,
148066 	There's no test for this here, but this feature will be used in a
148080 	source_cache::ensure is called.  This function looks for the file in
148098 	offsets data for every source file.
148103 	::get_line_charpos asking for offset data we still call ::ensure which
148112 	There should be no user visible changes after this commit, except for
148124 	I've added a test for this new feature.  The test is a little weird,
148130 	In reality, this command is useful for testing the syntax highlighting
148150 	just for lwp related debug, so the new name seems to make more sense.
148154 	ld: add hidden and internal visibility support for XCOFF
148155 	This patch adds a primary support for hidden and internal visibility in
148156 	GNU linker for XCOFF format.
148172 		* testsuite/ld-vsb/main.c: Adapt for XCOFF.
148184 	A following patch will add visibility support in ld for XCOFF. Thus,
148204 	this patch allows XCOFF to accept the usual GNU syntax for visibility.
148218 	gas: add visibility support for XCOFF
148232 	        * coffgen.c (coff_print_symbol): Increase the size for n_type.
148266 	and I believe people have run into getting testsuite failures for
148269 	testsuites for "CU:" to catch target-specific occurrences, but I
148273 	options for the gas test as I believe the "CU:" format is preferable.
148275 	Tested for cris-elf and native x86_64-pc-linux-gnu.
148296 		* ldlang.c (lang_add_section): Set SEC_ELF_REVERSE_COPY for
148332 	ar: Add --thin for creating thin archives
148334 	System Interface specified semantics. Therefore -T for thin archives is
148335 	not recommended for portability. -T is deprecated without diagnostics.
148340 	    * doc/binutils.texi: Add doc.
148372 	be the date range for the version of automake being used, that is the
148375 	The second date range in Makefile.in represents the date range for the
148387 	XCOFF: add support for TLS relocations on hidden symbols
148388 	This patch adds support for TLS relocation targeting C_HIDEXT symbols.
148392 	linker hash table for xcoff_reloc_type_tls.
148410 		* config/tc-ppc.c (md_apply_fix): Enable support for TLS
148485 	      gdb/remote: Restore support for 'S' stop reply packet
148503 	Add explicit check for nullptr to target_announce_attach
148512 	_sigsys, making it easier for developers to debug seccomp failures.
148552 	To prepare for DT_RELR implementation on these targets, extract
148562 	.sizeof. symbols have been finalized on x86, __[start|stop]_SECNAME for
148564 	been garbage collected.  This is no need for elf_x86_start_stop_gc_p.
148893 	input line is completed as a given output line.  The test checks for two
148941 	We see that the lines 2 and 4 are now the same, and for this reason the
148979 	generate all the combinations.  This removes the need to eyeball for all
149201 	support.") has removed support for privileged spec v1.9, this removes
149216 	RISC-V: update docs for -mpriv-spec/--with-priv-spec for 1.12
149217 	While support for the privileged spec was added in a63375ac337
149249 	split long @deffn lines in the guile.texi source file.  This splitting
149254 	done this for the longer @deffn lines, where a line break is
149261 	Most guile procedures in the guile.texi file are defined like:
149282 	arguments, and this was true for both of the procedures I am changing
149284 	lines, and keep them under 80 characters in the texi source.  This
149287 	Finally, our current style for keyword arguments, appears to be:
149291 	I don't really understand the reason for this, 'info guile' just seems
149299 	argument-name, for example, the pdf of make-command is:
149306 	neither of which are ideal.  And so, for the two commands I am
149387 		* debug.c (debug_write_type): Allow for malicious recursion via
149392 	aarch64: Add support for new SME instructions
149393 	This patch adds support for three new SME instructions: ADDSPL,
149403 		for ADDSPL, ADDSVL and RDSVL.
149461 	existing error messages are being checked for in any tests.
149467 	function.  As a side effect, this arranges for the output to be sent
149503 	langs.exp currently has some fails for me because the stack trace
149521 	meaningless for POPCNT.
149525 	"commutative" attribute is ignored for legacy encoding templates. Hence
149640 	Add elf_x86_allocate_local_got_info to allocate x86 GOT info for local
149668 		* doc/debug.options.texi: Replace =frame-interp with
149683 	I tested this for both 32- and 64-bit RISC-V using the AdaCore
149729 	it is, and should be, the default for all commands.  And, when writing
149744 	rather than filtered.  I don't think there's any reason for this, so
149765 	to invoke this command interactively, it's probably better for it to
149768 	Use filtered output for gdbarch dump
149900 	    fs/binfmt_elf: use PT_LOAD p_align values for suitable start address
149902 	This means that on 4K kernels, we will start to do extra work for 64K
149903 	p_align, but this pointless for pretty much all binaries (whose section
149984 		link_info.maxpagesize_is_set for -z max-page-size=NNN.
150029 …000, info: 0x0000000000000025, addend: 0x0000000000001007) against 'ifunc' for section '.data.rel.…
150033 …tmpdir/dump: R_X86_64_IRELATIVE (offset: 0x2000, info: 0x25, addend: 0x1007) against 'ifunc' for s…
150058 		for struct bfd_link_info.  Call linker callback when failing to
150064 		argument for struct bfd_link_info and pass it to
150075 		for struct bfd_link_info.
150077 		* libecoff.h (ecoff_backend_data): Add a pointer argument for
150084 	gdb/testsuite: fix inferior-clone.exp for native-extended-gdbserver
150103 	Fix by adjusting the testcase to a account for the possible trailing
150131 	The original patch was written for macOS, I assume on that target
150134 	On my GNU/Linux box, the man-page for sigwait doesn't mention that
150135 	nullptr is allowed for the second argument, so my assumption would be
150200 	double quote in the resulting symbol name) for now, warning about any
150222 	following output for "show logging":
150258 	which gives less clear output for some subcommands.
150308 	had a fix for an indentation problem in binop_promote.  I'm checking
150313 	[gdb/testsuite] Handle for loop initial decl with gcc 4.8.5
150318 	  'for' loop initial declarations are only allowed in C99 mode
150324 	- in the case of the jit test-cases, rewriting the for loops.
150334 	Update copying.awk for _initialize declaration patch
150335 	Commit 6c265988 ("gdb: add back declarations for _initialize
150377 	sim: tweak copyright lines for gnulib update-copyright
150407 	a space after a comma, and this is sufficient for gdb's
150487 		macros for l1om elf64-target.h use that are unchanged from default.
150586 	Use gdb_stdlog for MI debugging
150611 	Use gdb_stdlog for separate debug file logging
150613 	files) to use gdb_stdlog for its output.  This is part of PR gdb/7233.
150652 	Use correct stream for process record output
150731 	    Terminal for future runs of program being debugged is "/some/tty".
150736 	    Terminal for future runs of program being debugged is "".
150767 	There is no need to check member file size for thin archive member.
150810 	elf: Update comments for check_relocs in elf_backend_data
150938 		* cpu-riscv.c (riscv_priv_specs): Added entry for 1.12.
150943 		* testsuite/gas/riscv/h-ext-32.d: New testcase for hypervisor.
150948 		* opcode/riscv-opc.h: Added encodings for hypervisor csrs and
150956 	This makes way for a clean 1.12 based Hypervisor Ext support.
151021 	resumed, can be a candidate for having stopped.
151069 	non-stop modes now for extra coverage, we also run the tests with
151133 	immediately ask for the value of `a`, I get back the correct value.
151139 	This function makes the wrong choice for the struct A in our case, as
151145 	constructor), and the sys-v specification for argument and return
151147 	allocated for it by the caller, and the address of this space is
151155 	The call stack within GDB for where we actually go wrong is this:
151241 	location type for this field is a DWARF_BLOCK.
151249 	figure out the BITPOS for the virtual base class fields, I know for
151319 	entries are used elsewhere in the manual for async related topics (see
151323 	entry for 'set mi-async' when the command is documented as '-gdb-set
151324 	mi-async' (with a similar difference for the show/-gdb-show).
151327 	-gdb-show, and as -gdb-set/-gdb-show are just the MI equivalent for
151330 	consistent for mi-async.
151339 	The manual entry for 'set debug lin-lwp' is already vague about
151347 	used for any native linux target debug, so we now talk about
151348 	'GNU/Linux native target'.  The body string for this setting has been
151369 	for that.
151407 	tuple to a list, for esthetic reasons.  The empty ones are still tuples
151408 	though, they should probably be changed to be empty lists, for
151436 	x86: -mfence-as-lock-add=yes doesn't work for 16-bit mode
151443 	We would better be prepared for 'm' being the first character of the
151449 		* doc/binutils.texi: Fix typos.
151480 	hadn't worked for 6 years prior to that.
151523 	gdb: add "exit" command as an alias for "quit"
151524 	This command adds the "exit" command as an alias for the "quit"
151554 	gdb/remote: some fixes for 'maint set target-async off'
151575 	  No unwaited-for children left.
151578 	Notice the 'No unwaited-for children left.' error, this is the
151596 	  the case for us given the maintenance commands we used, we cache the
151597 	  stop packet within the remote_state::buf for later processing.
151654 	data, and I think it would be too easy for new corruptions of the
151655 	buffer to be introduced, which could easily go unnoticed for a long
151685 	for async-mode, and so, in remote_target::push_stop_reply, where we
151696 	for events in the ::stop_reply_queue.  Now that ::cached_wait_status
151731 	As for the second difference, I have resolved this by having all stop
151859 	think it is better for ordinary code to be editable in a C file -- not
151870 	each iteration, so there is no point in redoing it for each element and
151944 		and check that entry in elf_section_syms for sec is non-NULL.
151971 	howto.size.  That means bfd_get_reloc_size gives the wrong answer for
152029 		(debug_displays): Add entry for .note.gnu.build-id.
152033 		Fix regexp for loads via debuglink section.
152037 	arm: Add support for Armv9.1-A to Armv9.3-A
152038 	This patch adds AArch32 support for -march=armv9.[123]-a.
152042 	The cpu_arch_ver entries for ARM_ARCH_V9_2A and ARM_ARCH_V9_3A
152051 		* doc/c-arm.texi: Add armv9.1-a, armv9.2-a and armv9.3-a.
152069 	arm: Add support for Armv8.7-A and Armv8.8-A
152070 	This patch adds AArch32 support for -march=armv8.[78]-a.
152081 		* doc/c-arm.texi: Add armv8.7-a and armv8.8-a.
152095 	aarch64: Add support for Armv9.1-A to Armv9.3-A
152096 	This patch adds AArch64 support for -march=armv9.[123]-a.
152101 	feature flags so that Armv9.1-A could reuse the set for
152131 		* doc/c-aarch64.texi: Add armv9.1-a, armv9-2-a and armv9.3-a.
152153 	According to the privileged spec, there are five new instructions for
152156 	hypervisor extension in mainline for now, so let's consider the related
152167 	svinval extension is frozen for now.  Besides, we fix the funct7 encodings
152178 		* opcode/riscv-opc.h: Added encodings for svinval.
152186 	These are just using the default behavior for the 3rd arg, so drop
152192 	bfd: unify texi generation rules
152201 	The header shuffling in here broke the workaround for gnulib defining
152208 	Adjust compare_link_order for unstable qsort
152209 	In a cross toolchain for nios2-elf target and x86_64-w64-mingw32 host
152265 	Fix this by validating integer attribute forms, as we do for string
152280 	at configure time. This is useful for statically-linked builds of
152294 	The default for --enable-threading is "yes".
152322 	One possible fix is to make offsetT a 64-bit type for loongarch32.
152366 	for example by modifying SOCK_DIR to be:
152405 …   cc1plus: warning: command-line option ‘-Wmissing-prototypes’ is valid for C/ObjC but not for C++
152434 	destination buffer (including space for the NULL byte) and use strcpy.
152446 	Clang 13 and 14 produce some -Wunused-but-set-{variable,parameter} for
152458 	important for somebody who knows what they're doing to just make sure
152488 	gdb/mi: use separate classes for different types of MI command
152490 	sub-classes for the different types of MI command.  Instances of these
152499 	and a second for MI commands that delegate to CLI commands.
152517 	gdb/mi: use std::map for MI commands in mi-cmds.c
152521 	dynamically add commands; which is something that is planned for a
152537 	RISC-V: Added ld testcases for the medlow and medany code models.
152583 	x86: Adjust linker tests for --disable-separate-code
152584 	Adjust linker tests for linker configured with --disable-separate-code:
152638 	one go, rather than trying to do lazy fetches for a couple of bytes at
152646 	What's going on is that in valarith.c, in value_subscript, for C like
152658 	However, for cases where we do have the array contents loaded, and we
152660 	value_subscripted_rvalue, which is what we use for non C like
152677 	gdb: update gdb-gdb.py.in for latest changes to struct field
152685 	      gdb: add accessors for field (and call site) location
152694 	Finally, I have also added support for the new TYPE_SPECIFIC_INT
152725 	Introduce a class for restoring the current thread and a function to
152726 	switch to the given thread.  This is a preparation for a refactoring
152766 	implementing, what is really a helper function for just one of its
152817 	inherited from inf_ptrace_target except for hppa_nbsd_nat_target,
152854 	I could only find mailing list threads for ppc and sh in the archive ,
152868 	My motivation for this patch relates to the post_startup_inferior
152873 	enabling of proc events is something that would need to be done for
152882 	I've done absolutely no testing for this change, not even building it,
152913 	So, though we can build most of GDB just fine for riscv and mips with
153012 		* elf.c (bfd_section_from_shdr): Remove old hack for Oracle
153063 	Set sh_link for reloc sections created as normal sections
153069 		* elf.c (assign_section_numbers): Formatting.  Set sh_link for
153249 	sim: use ## for automake comments
153268 	for the child, we can simply call detach_inferior on it.
153275 	   but then saved it for later (for example, because it got the event
153288 	   acknowledged.  I followed the model of remove_new_fork_children for
153298 	output directory, and make the test wait $timeout seconds for that file
153309 	would also be valid for TARGET_WAITKIND_SIGNALLED, but that would mean
153323 	joins the forking threads, and the forking threads wait for their fork
153371 	In preparation for a following patch, refactor a few things that I did
153380 	   thread_pending_fork_status and check for nullptr.
153411 	in GDBserver).  This happens for example when we step a thread and
153454 	GDB yet.  But that only works for fork events that have made their way
153469 	Implementation details-wise, the fix for this is all in GDBserver.  The
153504 	Use for-each more in gdb
153514 	In my earlier C++-ization patch for file_and_directory, I introduced
153553 	The reason for this is that, as we don't implement __init__ for
153604 	Currently, passing None for the Type will result in an error:
153692 	now.  This is also true for the memory error case, where before we
153715 	the one GDB uses for POWER (0x7fe00008) did not result in stop but
153777 	changed for !empty checks.
153820 	entries.  AT_FXRNG points to a root seed version for the kernel's
153846 	In commit 80ad340c902 ("[gdb/testsuite] use -Ttext-segment for jit-elf tests")
153880 	On x86_64-linux we have at the initial screen dump for "list -q main":
153907 	The cause of the diffferent placement is that we have as line number for main
153931 	[gdb/tdep] Fix inferior plt calls in PIE for i386
154081 	Re: Add support for AArch64 EFI (efi-*-aarch64)
154093 		not output_target for input.
154098 	It's not foolproof, for example we don't catch output to a linker
154113 	This patch adds an #elif defined for PowerPC to setup the exit_0 macro.
154130 	- copy say, gdb.arch/i386-avx.c as basis for a new test-case
154190 	gsym->use_plt_offset() returning false.  This is fixed for dynamic
154191 	linking by correcting get_reference_flags, and for static linking by
154193 	revolves around needing to create PLT entries for inline PLT calls
154194 	when statically linking (for gcc -mlongcall).  The lplt section
154195 	handled that for local symbols, now it does globals too.
154198 		for static link.
154203 		(Target_powerpc::make_local_plt_entry): New variant for global syms.
154210 		for local plt entries.
154215 		FUNCTION_CALL|RELATIVE_REF for inline plt relocs.
154216 		(Target_powerpc::Scan::global): Make entries in lplt for inline
154219 		use_plt_offset.  Set use_plt_offset for inline plt relocs.
154223 	ld: improve shared tests for AIX
154245 	process_psymtab_comp_unit_reader was allocating an artificial name for
154247 	cached file_and_directory.  This patch arranges for the allocated name
154299 	the build logic up to the common builds for better parallelization.
154323 	replacing direct assignments with methods, and arranging for it to own
154325 	be used on demand; this is an important property for the new DWARF
154329 	find_file_and_directory has a special case for the Irix 6.2 compiler.
154356 …  Warning: 'set index-cache on', an alias for the command 'set index-cache enabled', is deprecated.
154371 …  Warning: 'set index-cache on', an alias for the command 'set index-cache enabled', is deprecated.
154386 	account for those empty lines.
154401 	change that triggers the internal error for now, while we investigate
154415 	The rules for rebuilding the bfd headers live in the doc/ subdir
154419 	allows for rebuilding them in parallel.
154459 	gdb: use intrusive_list for cmd_list_element aliases list
154476 	I think it would make sense for extract_integer, extract_signed_integer
154537 	Add a test for the new function, testing both with arrays of a trivial
154549 	for it to take the integer as a parameter and return the
154603 		field to null for AARCH64_OPDE_EXPECTED_A_AFTER_B and
154658 	This commit resolves this issue by adding a new class specifically for
154677 	We can workaround this by adding a stub target for the info page when
154709 		* dwarf.c (process_cu_tu_index): Add test for overruning section
154757 	which are all incorrect for the 32-bit case.
154766 	gdb/testsuite: update tests looking for "DWARF 2" debug format
154771 	However, it failed to consider that some tests checked for the "DWARF 2"
154777 	Grep through the testsuite for "DWARF 2" and change all occurrences I
154818 	handling return values for base types (ppc64_sysv_abi_return_value_base)
154822 	(similar to what it does with floats, for instance).
154841 	This commit adds support for TYPE_CODE_FIXED_POINT types for
154964 	When the default in GCC is to generate proper DWARF info for fixed point
154996 	aarch64: Update gas/NEWS for recent changes
154998 		* NEWS: Mention support for Armv8.8-A and for new system registers.
155003 	This patch adds support for the Armv8.8-A BC instruction.
155017 		* doc/c-aarch64.texi: Document +hbc.
155026 	aarch64: Enforce P/M/E order for MOPS instructions
155033 	The registers should also be the same for each writeback operand.
155034 	This patch adds a warning for code that doesn't follow this rule,
155035 	along similar lines to the warning that we already emit for
155052 		(init_insn_sequence): Use a 3-instruction sequence for
155061 		for AARCH64_OPDE_A_SHOULD_FOLLOW_B and AARCH64_OPDE_EXPECTED_A_AFTER_B.
155076 	aarch64: Add support for +mops
155077 	This patch adds support for FEAT_MOPS, an Armv8.8-A extension
155105 		(aarch64_opcode_table): Add entries for AARCH64_OPND_MOPS_ADDR_Rd,
155116 		* doc/c-aarch64.texi: Document +mops.
155168 	aarch64: Add support for Armv8.8-A
155169 	This patch adds skeleton support for -march=armv8.8-a, testing only
155177 		* doc/c-aarch64.texi: Document armv8.8-a.
155184 	aarch64: Provide line info for unclosed sequences
155190 	for aarch64.
155210 	sequences but is going to be useful for the Armv8.8-A MOPS
155215 	instructions in the sequence.  It's more convenient for the
155226 		(init_insn_sequence): Update for new aarch64_instr_sequence layout.
155228 		(verify_constraints): Update for new aarch64_instr_sequence layout.
155271 		for each register.
155275 		rather than 8 for the TCO test.
155295 	When introducing this code, I forgot that we had some macros for this.
155302 	 - Add DIAGNOSTIC_ERROR_SWITCH, to enable -Wswitch at error level, for
155319 	Work around this by making DIAGNOSTIC_ERROR_SWITCH a no-op for GCC < 5.
155325 	compilers.  Still, for correctness, we would ideally want to ask the
155356 	x86: Skip __[start|stop]_SECNAME for --gc-sections -z start-stop-gc
155358 	__stop_SECNAME for --gc-sections -z start-stop-gc if all SECNAME
155365 		and __stop_SECNAME for --gc-sections -z start-stop-gc if the input
155400 	These have been around for decades but don't appear to be used, and
155406 	build slightly.  It also allows for more parallelism.
155410 	build slightly.  It also allows for more parallelism.
155475 	binutils: add missing prefix for binutils/index.html rule
155519 	Protection Keys for Userspace" support, we run into:
155534 	Fix the FAIL by accepting this value for linux.
155542 		* coff/internal.h (x_n): Use bfd_hostptr_t for the fields in this
155604 	the istarget.  The current if / else statement does not check for
155608 	This patch adds an if statement to check for powerpc64 and if true sets mach
155620 	Fix missing build dependency for binutils man pages
155628 	This patch adds support for various system registers, up to Armv8.7-A.
155655 	We have a +lor feature flag for the Limited Ordering Regions
155660 		(aarch64_sys_regs): Use it for lorc_el1, lorea_el1, lorn_el1 and
155665 		* testsuite/gas/aarch64/illegal-sysreg-7.s: Test for LOR registers
155736 	aarch64: Check for register aliases before mnemonics
155745 	for "xzr", where "zero" is now also the name of an SME instruction.
155749 	This patch switches things so that we check for register aliases
155757 	still work, since create_register_alias checks for " .req ",
155764 	The new test for invalid aliases already passed.  I just wanted
155774 		(md_assemble): ...here.  Check for register aliases first.
155776 		testsuite/gas/aarch64/register_aliases.s: Test for a register
155784 	gdb/python: don't use the 'p' format for parsing args
155792 	cause an error for earlier versions of Python.
155799 	cause some changes in behaviour, for example both of these will work
155833 	Use dwarf_vma type for offsets, ranges and section sizes in DWARF decoder.
155834 		* dwarf.c (find_debug_info_for_offset): Use dwarf_vma type for
155867 	gdb: fix disassembler regressions for 32-bit arm
155889 	The reason for this is this code in opcodes/i386-dis.c (in the
155926 	for the default architecture (the one selected by "auto") we _only_
155948 	gdb.RemoteTargetConnection.  This sub-class is created for all
155976 	remote target.  Using an interface object in this way allows (1) for
155984 	focused, this will make them (I hope) better for when
155993 	Additionally, in this commit, I've added support for packet replies
156033 	object type, this contains the connection for that inferior (or None
156034 	if the inferior has no connection, for example, it is exited).
156051 	  'num': The number for this connection,
156058 	  'details': A string or None.  Extra details for the connection, for
156109 		since they are different for operand Vc and Vb.
156171 	build slightly.  It also allows for more parallelism.
156188 	Allow DW_ATE_UTF for Rust characters
156218 	I filed PR rust/28637 for this issue, so that this patch can be
156230 	Fix this by ensuring that target_terminal::ours is in effect for the
156256 	for some header file:
156262 	The includer of ps is a shared symtab for a partial unit, with as user:
156293 		* doc/binutils.texi: Likewise.
156369 	for eeach set of tests.  This allows us to run all the tests in a
156375 	sim: testsuite: setup per-port toolchain settings for multitarget build
156404 	included when building for all ports.  This caught the sim-load file
156414 	no need for these files & generating things at build time.  So punt
156420 	table for its newlib/libgloss port.
156425 	table for its newlib/libgloss port.
156432 	table for its newlib/libgloss port.
156442 	table for its newlib/libgloss port.
156452 	table for its newlib/libgloss port.
156459 	table for its newlib/libgloss port.
156468 	defines.  These code paths are written specifically for the newlib
156471 	seems like the best trade-off for now.  Might have to reconsider
156477 	Like we just did for pulling out the errno map, pull out the syscall
156526 	sim: testsuite: add dedicated flag for init toolchain tests
156527 	As we setup more reliable CC_FOR_TARGET variables for each target, the
156538 	sim: cris: always search for local rvdummy tool
156541 	dirname to find rvdummy fails because it looks for `./rvdummy`.  So
156545 	If we get a request for testing against a different setup, we can
156571 	build-only tools, but automake doesn't allow for build & host tools, so
156576 	sim: testsuite: initial support for OS-specific tests
156577 	We usually test against the newlib/libgloss environment, but for a
156582 	tuple as a rough proxy for this (where cris*-*-elf is assumed to be
156600 	The sim_init function was called by runtest for each test when --tool
156610 	logic back.  We'll also leverage this in the future for toolchain setup.
156676 	  for (j = 0; i < NUM_MD5_BYTES; ++j)
156688 		* testsuite/gas/elf/dwarf-5-nop-for-line-table.d: Pass -W to
156708 	That is the case for the .debug_line part:
156716 	but not for the .debug_info part:
156770 	This commit adds support for RISC-V disassembler options to GDB.  This
156783 	In preparation for the next commit, which will add GDB support for
156840 	POSIX test uses = for compares, not == which is a bashism.
156920 	The new code solves this by checking for other found_fields that have
156924 	The testcase gdb.cp/ambiguous.exp was also changed to test for this
156930 	Section alignment for coff-go32 is inconsistent - The '.text' and
156940 	to 16 bytes, for all code and data sections referenced in the default
156944 		name match for .text, .data.  Add entries for .const, .rodata,
156949 	Re: AArch64: Add support for AArch64 EFI (efi-*-aarch64)
156955 	regenerated file.  Not that it matters for proper "make" behaviour,
156968 	Updated French translation for the opcodes directory.
156984 	observer for both source styling, and disassembler styling.
157034 	gdb: add asserts in target.c for target_async_permitted
157044 	  1. A target that returns false for target_can_async_p should never
157048 	  2. GDB should never try to enable async mode for a target that
157049 	  returns false for target_can_async_p, this is checked in
157106 	following output for "show logging file":
157164 	gdb: fix help doc for "set index-cache enabled"
157165 	When implementing this command, I put "help doc" as a placeholder for
157166 	the help string, and forgot to update it.  Change it for a real help
157173 	Revert (part of) "gdb fix for catch-syscall.exp"
157189 		* sysdump.c (getCHARS): Check for an out of bounds read.
157223 	However, for extra clarity, I have also added initial values in the
157239 	configure.ac: Check for the readline.h explicitly
157242 	might be confusing. This patch checks for the readline.h explicitly
157247 	AArch64: Add support for AArch64 EFI (efi-*-aarch64).
157248 	This adds support for efi-*-aarch64 by virtue of adding a new PEI target
157256 	However this target is not valid for use with gas but only with objcopy.
157270 	Type:           PE32+ executable (EFI application) (stripped to external PDB), for MS Windows
157287 	Any magic number is based on the Microsoft PE specification [1].
157392 	gdb: more compile fixes for gnu-nat.c
157396 …../../gdb-11.1/gdb/gnu-nat.c:3204:17: error: no matching function for call to add_cmd(const char […
157409 …../../gdb-11.1/gdb/command.h:161:30: note:   no known conversion for argument 3 from cmd_list_elem…
157416 …../../gdb-11.1/gdb/gnu-nat.c:3210:18: error: no matching function for call to add_cmd(const char […
157451 	of target_waitstatus::to_string a bit, but I think it is for the better.
157489 	riscv_opts.rvc flag for the .option arch directives.
157493 		for the .option arch directives.
157531 	Fix this conservatively by disabling the code for x32.
157607 	Fix this by using the correct offset size for DW_FORM_line_strp references
157634 	The v5 section version for .debug_line has:
157638 	Add support for this in the dwarf assembler.
157667 	Generate this field in the dwarf assembler, for now hardcoding the value to 1,
157683 	Currently, for each MACRO_AT_range or MACRO_AT_func in dwarf assembly the
157752 	Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
157753 	Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
157764 	Backing up a bit, the reason for this logic in the first place is
157779 	    H8 target for the H8/SX multilibs. I suspected memory corruption or an
157791 	    But for the short-form of those instructions we never set any of the "op3"
157800 	    the check for short form mova appropriately.
157802 	    I've had this in the upstream GCC tester for perhaps a year at this point
157824 	enable it only for c++14 and later.
157848 	for this case.  Instead, it enables the opposite case where the
157943 	it's not unreasonable that an assembler for a 32-bit architecture will object
157978 	Fix this by waiting for the "[Thread 0x7ffff7db1640 (LWP 19984) exited]"
157985 	gdb/testsuite: Extend tests for print of cv qualifiers
157986 	This commit supplements whatis and ptype command tests for print of
158021 	gdb outputs the following type for cfoo's attributes:
158044 	The cv qualifiers (const in this case) are ignored for me1 and me2.
158072 		  commmands for template class CFoo.
158084 	The new direcitve is used to enable/disable extensions for the specific
158116 		or update subsets for the specific code region.
158118 		* doc/c-riscv.texi: Added document for new .option arch directive.
158152 	directly without resolver for dynamic linker.  We also add a new dynamic
158161 		flag. It is used to check if relocations for variant CC symbols
158165 		(riscv_elf_size_dynamic_sections): Added dynamic entry for
158171 		(get_dynamic_type): Called get_riscv_dynamic_type for riscv targets.
158173 		(get_symbol_other): Called get_riscv_symbol_other for riscv targets.
158200 	sim: use program_transform_name for libsim
158215 	dprintf-execution-x-script.exp: Adjust test for native-extended-gdbserver
158224 	the paths for readability:
158260 	I've also added a comment explaining the reason for needing to check
158261 	for "Don't know how to run" despite bailing out at the top of the test
158278 	I am no C++ template expert, but it looks like if I change "typename" for
158295 	violation"), which added default values for ia64_infcall_ops fields.  It
158331 	The documentation for the examining memory command x contains an example:
158354 		* as.c (parse_args): Add support for --multibyte-handling.
158366 		* doc/as.texi: Document the new feature.
158401 	gdb fix for catch-syscall.exp
158405 	checks for the return from the command.  The execve command starts a new
158413 	Update the check for the PowerPC architecture.  Power Little Endian systems
158428 	This patch fixes eight test failures on PowerPC for the test
158430 	setup the displaced stepping for ppc-linux platform.  The patch moves the
158513 	RISC-V: Add testcases for z[fdq]inx
158530 	RISC-V: Add instructions and operand set for z[fdq]inx
158536 	* elfxx-riscv.c (riscv_multi_subset_supports): Added support for
158541 	* config/tc-riscv.c (riscv_ip): Added register choice for z*inx.
158545 	* opcode/riscv.h (enum riscv_insn_class): Reused INSN_CLASS_* for z*inx.
158549 	* riscv-dis.c (riscv_disassemble_insn): Added disassemble check for
158551 	* riscv-opc.c: Reused INSN_CLASS_* for z*inx.
158557 	RISC-V: Add mininal support for z[fdq]inx
158558 	Minimal support for zfinx, zdinx, zqinx. Like f/d/q, the zqinx
158565 	for z*inx extensions.
158566 	(riscv_supported_std_z_ext): Added entries for z*inx.
158567 	(riscv_parse_check_conflicts): Added conflict check for z*inx.
158668 		New pstatefield value for SME instructions.
158669 		(aarch64_print_operand): Printout for OPND_SME_SM_ZA.
158892 	This series of patches (tagged [SME]) add support for the Scalable
158900 		* doc/c-aarch64.texi: Update docs.
158914 	Set the default DLL chracteristics to 0 for Cygwin based targets.
158915 		* emultempl/pep.em (DEFAULT_DLL_CHARACTERISTICS): Set to 0 for
158926 	ld	* ldgram.y: Add support for PT_GNU_RELRO and PT_GNU_PROPERTY.
158968 		* doc/binutils.texi: Document --input-abiversion and
158999 		(md_begin): Initialize register hash for rvv registers.
159004 		but used for parsing vsetvli operands.
159027 		* opcode/riscv-opc.h: Defined mask/match encodings and csrs for rvv.
159031 		(M_VMSGE, M_VMSGEU): Added for the rvv pseudoes.
159040 		(match_vs1_eq_vs2): Added for rvv Vu operand.
159041 		(match_vd_eq_vs1_eq_vs2): Added for rvv Vv operand.
159055 	It's an off-by-one case in an infeasible scenario for negative
159056 	huge core count. The change switches to std::string for memory
159063 	gdb: Add aliases for read_core_file_mappings callbacks
159065 	read_core_file_mappings_pre_loop_ftype.  Intended for use with
159072 	sim: testsuite: add support for $pwd replacements
159117 	      for the address of 'mnimonic' will never be NULL [-Werror=address]
159148 	readelf: Support SHT_RELR/DT_RELR for -r
159149 	The -r output for SHT_RELR looks like:
159176 	    (process_dynamic_section): Store into dynamic_info for
159334 	logic to stuff the stack for user-mode programs, but that's it.
159350 	Add testcases for Scalar Crypto extension, with total testcase contain all
159351 	instructions in k-ext/k-ext-64 and sub-extension testcase for zbk* zk*. Also
159352 	add testcase for new CSR name 'seed' which is the Entropy Source in zkr.
159358 		* testsuite/gas/riscv/k-ext-64.d: New testcase for crypto instructions.
159390 		* testsuite/gas/riscv/priv-reg-fail-zkr.d: New testcase for zkr
159409 	symbol and 'Y' to present 'rnum' symbolc  for zkn instructions.  Also add
159413 		* elfxx-riscv.c (riscv_multi_subset_supports): Added support for
159417 		(riscv_csr_address): Checked for CSR_CLASS_ZKR.
159418 		(validate_riscv_insn): Added y and Y for bs and rnum operands.
159423 		* opcode/riscv.h: Defined OP_* and INSN_CLASS_* for crypto.
159437 		rules for zk* extensions.
159438 		(riscv_supported_std_ext): Added entry for k.
159439 		(riscv_supported_std_z_ext): Added entries for zk*.
159448 	output that makes more sense in "info set", for example.
159466 	 - I would do the same for the "debuginfod urls" setter, but because
159537 	to use with git send-email.  I'm planning to use this for my RISC-V
159549 	[gdb] Don't use gdb_stdlog for inferior-events
159600 	Fix the discrepancy by not using gdb_stdlog for inferior-events.
159644 	non-default-constructible, so that provides a good motivation for this
159657 	Commit e86fc4a5bc37 ("PR 28447: implement multiple parameters for .file
159719 	argv[0] for the tests to read out later on.  Now that the sim has an
159726 	setting independently (especially for programs that inspect argv[0]
159753 	-Waddress fixes for gold testsuite
159769 	R_PPC64_REL24_P9NOTOC is a variant of R_PPC64_REL24_NOTOC for use on
159775 	any stub emitted for that branch, unless overridden by
159779 	for stubs if power10-only relocations are detected, continues to be
159786 		* elf64-ppc.c (ppc64_elf_howto_raw): Add entry for new reloc.
159805 		return BFD_RELOC_PPC64_REL24_P9NOTOC for @notoc.
159854 	[PR gdb/16238] Add completer for the show user command
159859 	In this commit I propose an implementation for such completer as well as
159891 	for carries.  Change the logic to test against the limit directly.
159899 	Fix gdb.base/sigstep.exp test for ppc
159903 	test looks for the stop at <signal_handler called>.  If found, the command
159965 	in libiberty/cplus-dem.c but it can be here for a while to iron out
160010 …[infrun] maybe_set_commit_resumed_all_targets: not requesting commit-resumed for target native, no…
160015 	that function for more info).  If this condition is true:
160022 	waiting for ever.
160029 	... but then it occured to me that we could simply check for:
160033 	Since "executing" implies "resumed", checking simply for "resumed"
160069 	new-op.cc:114:1: error: no previous declaration for \
160074 	new-op.cc:132:1: error: no previous declaration for \
160083 	The declarations are provided by <new> (which is included) for c++14 onwards,
160084 	but they are missing for c++11.
160094 	Add a regression test-case for commit a50bdb99afe "[gdb/tdep, rs6000] Don't
160109 	For now we should always generate the elf architecture attribute both for
160141 	The c.nop at address 0x6 is generated for alignment, but since the rvc isn't
160142 	allowed for this object, dump it as a c.nop instruction looks wrong.  After
160169 	set the default architecture string to rv64gc for disassembler, to keep
160172 	This patch pass the riscv-gnu-toolchain gcc/binutils regressions for
160179 		codes for riscv_parse_subset_t setting.
160183 		* elfxx-riscv.h: Added extern for riscv_subset_supports and
160189 		(riscv_rps_as): Defined for architectrue parser.
160209 		(riscv_rps_dis): Defined for architectrue parser.
160223 	Since gcc dropped support for a.out starting with 4.4.0 in 2009, it's
160265 	This patch is adding support for Cortex-A710 CPU in Arm.
160275 		* doc/c-arm.texi: Update docs.
160281 	Commit e86fc4a5bc37 ("PR 28447: implement multiple parameters for .file
160305 	Note that this is not a regression test for that commit.  Since the actual
160325 	While the feature is nice for developers, it breaks a bunch of
160345 	ld: set correct flags for AIX shared tests
160354 	PR 28447: implement multiple parameters for .file on XCOFF
160403 	Test case for Bug 28308
160427 	problem using this test case, though for brevity, I've placed all
160519 	     target.  Waiting for the command's completion is later done on
160528 	This is a backtrace after hitting the dprintf breakpoint for
160600 	There are two frames for bpstat_do_actions_1(), one at frame #16 and
160602 	for Breakpoint 2, which is a 'continue'.  The one at frame #0 is attempting
160609 	the dprintf breakpoint for the second time when issuing the 'run'
160669 	had a good reason for doing it this way.)
160672 	states that the reason for checking this variable is to avoid
160683 	infinite recursion check for potential 'source' commands on the
160738 	This test fails for me, showing:
160751 	    warning: Found custom handler for signal 7 (Bus error) preinstalled.
160752 	    warning: Found custom handler for signal 8 (Floating point exception) preinstalled.
160753 	    warning: Found custom handler for signal 11 (Segmentation fault) preinstalled.
160796 	doc/ctf-spec.texi: Remove "@validatemenus off"
160797 	Remove @validatemenus from ctf-spec.texi, which has been removed from
160804 	    * doc/texinfo.texi
160805 	    (Writing a Menu, Customization Variables for @-Commands)
160811 	    * tp/Texinfo/XS/configure.ac: Check for gawk.
160824 		* doc/ctf-spec.texi: Remove "@validatemenus off".
160834 		* binutils.texi: Document the new feature.
160859 	local funcs as static, and add missing prototypes for the rest which
160918 	object for which the A member is 2 and this call to print_all<Parent>
160941 	This commits adds const versions for the GET and AS_ARRAX_VIEW methods
160960 	Since the proceed function is called once for each thread, the
160974 	gdbserver (debug output trimmed for brevity):
160985 	      [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target remote
160986 	      [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target remote
160992 	      [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target remote
160993 	      [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target remote
160995 	    ... and so on for each thread ...
160997 	Notice how we send one vCont;c for each thread.  With the patch applied, we
161012 	    [infrun] maybe_set_commit_resumed_all_targets: enabling commit-resumed for target remote
161013 	    [infrun] maybe_call_commit_resumed_all_targets: calling commit_resumed for target remote
161055 		* doc/ctf-spec.texi: New file.
161074 		* ld.texi (Input Section Wildcards): Delete paragraph incorrectly
161086 	which is the right type for this.
161111 	define already, so no need for the fallback here.
161116 	for these targets.
161120 	We did this for all other targets already, but ppc was missed.
161152 	of sregs.i for sh-dsp has generated a lot of compiler warnings about
161208 	Newer versions of bison emit a prototype for yyerror
161212 	uses the return value all over the place, so for there disable
161267 	The project has been using GPL v3 for a while now in the source files,
161295 	of the process the file was open for is gone, because the process
161304 	opening the file for a different thread of the process.  The testcase
161316 	Oleg Nesterov gave this suggestion as workaround for that race:
161410 	too hard to support larger sizes (patches welcome!) but for now just
161433 	command (prefix for "set index-cache directory", for example), and a
161434 	boolean setting for turning the index-cache on and off.  Even though I
161465 	by const reference.  This is not necessary for scalar values (like bool
161490 	This is useful for a patch later in this series that defines a boolean
161508 	for loops will simply be skipped.
161529 	Always check sections with the corrupt size for non-MMO files.  Skip MMO
161530 	files for compress_status == COMPRESS_SECTION_NONE since MMO has special
161531 	handling for COMPRESS_SECTION_NONE.
161562 		subset list.  This is used for the .option rvc or norvc.
161579 	The multi-run logic for mips involves a bit of codegen and rewriting
161588 …micromipsmicromips_run.c:80:1: error: no previous prototype for 'micromips64micromips_engine_run' …
161591 	We generate headers for those prototypes in the configure script,
161619 	sim: ppc: switch to common builds for callback objects
161623 	out of nltvals.def & targ-map.o.  This doesn't matter for the sim
161624 	directly, but does for gdb and other users of libsim.
161628 	has been the case for decades at this point.
161702 	The current register set selection mechanism for AArch64 is static, based
161707 	tag_ctl register, for example, does not result in a ptrace error if the kernel
161721 	Currently for a binary compiled normally (without -fsanitize=address) but with
161793 	It's possible for the rounding up of the arange pointer to exceed the
161804 	the build logic up to the common builds for better parallelization.
161809 	We leave the cgen maintainer rules in the subdirs for now as they
161817 	the build logic up to the common builds for better parallelization.
161826 	the build logic up to the common builds for better parallelization.
161833 	config.h which can be problematic for build-time tools.
161835 	Also swap stdio.h for stddef.h.  This file isn't doing or using
161844 	it be run only once, which means ppc64_elf_tls_setup can't call it for
161867 	Dump of assembler code for function _exit:
161956 	PIC helper function for x86_64-linux.
161970 	ARM: match armeb output for unwind-pacbti-m test
162028 		(bfd_arm_get_mach_from_attributes): Add case for TAG_CPU_ARCH_V9.
162045 		for -amarch=all.
162047 		* doc/c-arm.texi: Update docs.
162117 	but we don't abort the build for them, so turn on -Werror everywhere.
162122 	sim: ppc: fix the printf fix for 32-bit systems
162189 	Anchoring the regexps seems to fix the problem, and works for the
162212 	We have GNU make generate these for us automatically now, so there's
162221 	this to the common logic so we only build it once for multi-targets.
162224 	Like we just did for pulling out the errno & signal maps, pull out the
162238 	Like we just did for pulling out the errno map, pull out the signal
162247 	file.  This list of errno values is the same for all arches, so we
162249 	for newlib/libgloss environments, which makes it confusing to support
162252 	but sets up the framework for it.
162307 	Add a new stamp helper for quiet builds, and don't dump the command
162348 	This (and other) code from coffcode.h is broken for x86_64_coff_vec,
162365 	We have removed support for --target=x86_64-coff, likely because it
162408 	version of string_view, and don't have a selftest for it.  So the list
162418 	gdb.texinfo: Expand documentation for debuginfod
162428 	gdb: add set/show commands for managing debuginfod
162430 	argument.  'on' enables debuginfod for the current session.  'off'
162431 	disables debuginfod for the current session.  'ask' will prompt
162437 	    Enable debuginfod for this session? (y or [n]) y
162457 	    Download failed: No route to host.  Continuing without debug info for /lib64/libc.so.6.
162461 	    Support for debuginfod is not compiled into GDB.
162583 	Today I re-learned that resolve_dynamic_type can return a type for
162584 	which is_dynamic_type returns true.  This can happen for an array
162606 	... relies on is_dynamic_type returning true for such an array.
162616 	This happens because opcodes rejects an attempt to disassemble for an
162656 	Support for a new pacbti unwind opcode.
162657 	This patch adds readelf support for decoding the exception table
162658 	opcode for restoring the RA_AUTH_CODE pseudo register defined by the
162668 	Re: arm: add unwinder encoding support for PACBTI
162698 	for OpenRISC targets.  This patch documents that in the news.
162700 	gdb: or1k: add single step for linux native debugging
162701 	Needed for single stepping in Linux, this adds the or1k implementation
162710 	This patch adds support for running gdb natively on OpenRISC linux.
162728 	This patch adds gdbserver support for OpenRISC.  This has been used for
162785 	After the previous commit, it is easy to add completion for selftest
162796 	arm: add unwinder encoding support for PACBTI
162797 	This patch adds support for encoding the Return Address Authentication pseudo
162804 		(reg_expected_msgs): Add message for pseudo reg type.
162819 	be nice for it to use the option framework.  For example, that makes
162864 	Fix this by testing for python support in the test-case.
162938 	[ I've tried to create a dwarf assembly test-case for this, but didn't
162957 	anonymous union type. Clang does not emit symbol for unused anonymous
162959 	itself is not emitting the symbol for "p_union", debug info is also
162962 	enables emitting debug info for "p_union".
163032 	because the debug registers were only updated for certain threads --
163047 	Failed to listen for connections: Address already in use^M
163085 	Tidy the gas/config/tc-riscv.c and opcodes/riscv-dis.c, to prepare for
163105 		opargStart and asargStart, to prepare for moving the released
163108 		(macro_build): Added fmtStart, also used to prepare for moving
163110 		(md_show_usage): Added missing descriptions for new options.
163113 		oparg and opargStart, to prepare for moving the released
163118 	opcodes: Fix RPATH not being set for dynamic libbfd dependency
163121 	corresponding RPATH entry for the directory to find libbfd in.  This
163137 	adding RPATH entries as required, however our setup for libopcodes
163173 		except for Cygwin.
163189 		for the .note.gnu.property section.
163235 	Enable these assertions only when _GLIBCXX_DEBUG is set, as we did for
163259 	x86: Also handle stores for -muse-unaligned-vector-move
163272 	PASS: gdb.mi/mi-var-cp.exp: create varobj for s
163273 	PASS: gdb.mi/mi-var-cp.exp: create varobj for s
163274 	DUPLICATE: gdb.mi/mi-var-cp.exp: create varobj for s
163287 	   106      mi_create_varobj S s "create varobj for s"
163288 	   107      mi_create_varobj R r "create varobj for s"
163291 	Fix this by using "create varobj for r" instead.
163354 		* doc/ctf.options.texi: Adjust.
163397 	new ELF sections on the fly named things like .ctf.foo.c for ambiguous
163426 	and then smaller, headed dumps for the per-TU child dicts; but if
163431 	members, move from ctf_archive_iter (for which passing in extra
163448 		parent's name, while still avoiding displaying the header for the
163454 		* doc/ctf.options.texi: Adjust.
163473 		* coff64-rs6000.c (_bfd_xcoff64_swap_aux_in): Use bfd_vma for h.
163512 		check PAIR reloc in other branch of condition as was done for
163572 		* doc/as.texi: Likewise.
163573 		* doc/c-loongarch.texi: Likewise.
163686 		(md_assemble): Call encode_with_unaligned_vector_move for
163692 		* doc/c-i386.texi: Document -muse-unaligned-vector-move.
163708 	examining the install tree for regular files.  Only the 'dir' file
163717 	would be cleaner to have a separate patch for the deletions.
163788 	Likewise for the following:
163851 	disassemble_info struct, so there's no real reason for its special
163861 	RISC-V: Added ld testcase for pcgp relaxation.
163890 	This patch just add the ld testcase for the above case, in case we
163919 	Unfortunately this process could not account for the fact that we were
163953 		stage, so just pass NULL pointer as the pcgp_relocs table for
163955 		(_bfd_riscv_relax_section): Use only one pass for all target
164002 …t.c:1271:12: runtime error: load of value 2686365, which is not a valid value for type 'gdb_signal'
164013 	 - Add setters, one for each kind.  Each setter takes as a parameter the
164016 	 - Add getters, one for each associated data type.  Each getter
164058 	Fix ARMv8.4 for hw watchpoint and breakpoint
164059 	Just like my previoius patch for ARMv8.1 and v8.2 (49ecef2a7da2ee9df4),
164060 	this adds ARMv8.4 debug arch as being compatible for hw watchpoint
164071 	Fixes for gdb.mi/mi-break.exp
164072 	Update the expected pattern for two of the tests.
164082 	-      for (bp = breakpoint_chain;
164095 	+      for (breakpoint *bp : all_breakpoints ())
164123 	The "add accessors for field (and call site) location" patch caused a
164128 	unconditionally uses TYPE_FIELD_BITPOS.  This causes an assert for a
164132 	find_struct_field to use a dummy value for the field offset in the
164141 	nullptr for the out parameters when they are not needed (the second
164154 …ldelf.c:1049:43: warning: the comparison will always evaluate as 'true' for the address of 'elf_he…
164168 …readelf.c:349:8: error: the comparison will always evaluate as 'true' for the pointer operand in '…
164262 	Accordingly, this patch only defines that function for Bison < 3.8.
164281 	that captured_command_loop and set_active_ext_lang are available for setting
164318 	check for PRINTF_HAS_LONG_LONG.  This patch fixes both issues.
164325 	resolve_dynamic_type_internal, passing it the sub-object for the
164335 	Always use std::function for self-tests
164353 	    The directory where separate debug symbols are searched for is "/usr/local/lib/debug".
164383 	    Missing separate debuginfo for target:/usr/sbin/mariadbd
164387 	Observe it didn't look for
164400 	Fix a potential illegal memory access when testing for a special LTO symbol name.
164401 	bfd	* linker.c (_bfd_generic_link_add_one_symbol): Test for a NULL
164405 		* nm.c (filter_symbols): Test for a NULL name before checking to
164415 	CTF: incorrect underlying type setting for enumeration types
164416 	A bug was filed against the incorrect underlying type setting for
164431 	.debug_info looking for DW_AT_ranges entries, then displays the
164450 	ld: Adjust pr28158.rd for glibc 2.34
164451 	Adjust pr28158.rd for glibc 2.34:
164476 		* testsuite/ld-elf/pr28158.rd: Adjusted for glibc 2.34.
164488 	Powerpc: Add support for openat and fstatat syscalls
164491 	Add argument to ppc_canonicalize_syscall for the wordsize.
164492 	Add syscall entries for the openat and fstatat system calls.
164516 	[GOLD] Two GOT sections for PowerPC64
164517 	Split .got into two piece, one with the header and entries for small
164518 	model got entries, the other with entries for medium/large model got
164540 		64-bit header for small got section.
164541 		(Output_data_got_powerpc::g_o_t): Only return a result for small
164554 	value, but powerpc gold has no real support for multi-toc.  This patch
164555 	removes the pretense, tidying quite a lot in preparation for a
164566 		header_index_ to -1u for 64-bit, and make header here.
164570 		section for 64-bit.  Use throughout.
164578 	Adjust for commit ba7c18a48457.
164622 	PPC fix for stfiwx instruction (and additional stores with primary opcode of 31)
164633 	indicates that the disassembly failed for some reason.  In disas.c, in
164644 	However, for this to work correctly, every time the libopcodes
164652 	callback, for example in arc-dis.c and cris-dis.c.
164655 	must therefore be broken, except for the case where we can't read
164669 	  Dump of assembler code for function main:
164674 	  Dump of assembler code for function main:
164707 	- requiring use_gdb_stub == 0 for the entire test-case, or
164721 	The two tests are instances of the same test, with different values for
164743 	native-gdbserver, I run into (added missing double quotes for clarity):
164758 	local-board.exp", the problem is the use of -ex for
164772 	(gdb) PASS: gdb.arch/i386-mpx.exp: verify size for bnd0
164785 	Quit anyway? (y or n) WARNING: Timed out waiting for EOF in server after monitor exit
164808 	[ARM] Add support for M-profile MVE extension
164809 	This patch adds support for the M-profile MVE extension, which includes the
164915 	The pseudo register handling for ARM uses some hardcoded constants to
164930 	accounting for all the registers in the XML description, so move
164939 	In preparation for the MVE extension patch, this one refactors some of
164940 	the register-related constants we have for ARM.
164967 	- as the name for a local variable
165022 	are two versions of debug info for $srcfuncfile.  This shows up as a FAIL when
165034 	[gdb/testsuite] Use require for ensure_gdb_index
165062 	.gdb_index: faked for "readnow"^M
165078 	add an index as a failure to add an index for a symlink:
165087 	file.  Add a check for that situation.
165129 	The pattern for using execute_command_to_string is:
165242 	  (which doesn't work for libc, now that libpthread_name_p has been
165302 	Fix this by applying the same fix as for "register values t" in commit
165317 	  scan for backtrace (GDB internal error)
165442 	Ideally, GDB would present a consistent and documented value for an
165454 	gdb: add accessors for field (and call site) location
165455 	Add accessors for the various location values in struct field.  This
165494 	RISC-V: Support aliases for Zbs instructions
165495 	Add aliases for the non-immediate mnemonics of b{set,clr,inv,ext} to
165507 	        * riscv-opc.c (riscv_opcodes): Add aliases for Zbs.
165513 	RISC-V: Add support for Zbs instructions
165517 	for the frozen specification.
165530 		* opcode/riscv-opc.h: Added MASK/MATCH/DECLARE_INSN for Zbs.
165537 	RISC-V: Update extension version for Zb[abc] to 1.0.0
165542 		number for zba, zbb and zbc to 1.0.0
165546 	- Updated version numbers for zba, zbb and zbc to 1.0.0
165553 	the Privileged spec for an uninitiated reader.  This separates them
165565 	XCOFF archives use a bi-directional linked list for file members.  So
165568 	is over-engineered nonsense and an attractive target for fuzzers.
165575 	for objdump, then relocations are read and printed.  Those relocations
165655 	The documentation for 'show print elements' contains the line:
165667 	'set print elements' section, however, for 'show print elements' the
165693 	 --Type <RET> for more, q to quit, c to continue without paging--
165718 	This fixes a situation where the COFF code allocated memory for
165726 		allocating memory for internal line number array.  Adjust error
165754 	can't safely catch all such cases by comparing with file size, for
165816 	and getter callbacks for settings) makes it possible for a setting not
165831 	This makes the Ada-specific "varsize-limit" a synonym for
165861 	value.  This is needed for a subsequent patch, where an attempt to
165897 	The regexp expect running messages for all threads, but we only get one for
165911 	When a user creates a gdb.Inferior object for the first time a new
165988 	I wrote a test for this issue making use of Pythons tracemalloc
166015 	abort, for example, when handling an internal error and the user
166034 	this point we don't know for sure what other GDB state has already
166040 	The test gdb.python/py-events.exp sets up a handler for the gdb.exited
166056 	example in the documentation for how to write an event handler.
166115 	default AX_CXX_COMPILE_STDCXX makes the configure test for std::thread
166118 	We could simply add $CXX_DIALECT to the test for std::thread support, but
166119 	that would have to be repeated for each added c++ support test.
166136 	 - the switch in CXX for the std::thread tests (and other tests)
166154 	@entry values for foo:
166183 	test-case, with debug info for foo and bar, but not for main.
166187 	- this does not trigger expanding debug info, because there's none for main
166237 	It must be the first field as we overload core_addr_hash and core_addr_eq for
166240 	for field pc of struct call_site.
166245 	This is caused by core_addr_eq (the eq_f function for the htab) being
166296 	between the gdbsupport module and the bfd module, so, for example, if
166312 	dependency for something we don't need seems pretty pointless.
166316 	sim: add --info-target for listing supported BFD targets
166358 	      /* And so on for all possible var_types.  */
166361 	This comparison is done for each possible var_type, which leads to
166374 	to be copied before the update, which can be non trivial for
166388 	gdb: Have setter and getter callbacks for settings
166401 	custom logic.  This is useful when the source of truth for a given
166426 	"mordernize" this by changing them to use an std::string for storage.
166438 	leads to some code that needs to check for both to check for "no value".
166446 	important for some setting, but it doesn't seem so.  If that ever
166451 	init_history, for the test gdb.base/gdbinit-history.exp.  init_history
166457 	that chooses a good default value for history_filename to
166561 	a variable.  This is what setting::erased_args is used for.
166577 	 parameter but only used it for the VAR and VAR_TYPE member. They now
166639 	This commit adds support for handling such instruction in
166692 	Fix build failure for 32-bit targets
166733 	PATCH bfd: Fix linker warning for recently introduced arm attributes
166741 	gdb/testsuite/dwarf: use options for rnglists/loclists procs
166742 	Change how rnglists and loclists procs to align them with how procs for
166752 	gdb/testsuite/dwarf: don't define nested procs for rnglists/loclists
166753 	When I wrote support for rnglists and loclists in the testsuite's DWARF
166754 	assembler, I made it with nested procs, for example proc "table" inside
166764 	"start_end" procedure, for example, it would get overriden.
166781 	larger without much value for readability.  So I think it's reasonable
166820 	for a while now, which is conscious about the SHELL environment and a
166827 	[gdb/testsuite] Add untested for missing xml support in gdb.base/valgrind*.exp
166837 	flag for -mcpu option.
166847 		* doc/c-arm.texi: Update docs.
166853 	This patch is adding support for Cortex-X2 CPU.
166859 		* doc/c-aarch64.texi: Update docs.
166864 	This patch is adding support for Cortex-A710 CPU.
166870 	        * doc/c-aarch64.texi: Update docs.
166875 	This patch is adding support for Cortex-A510 CPU.
166881 		* doc/c-aarch64.texi: Update docs.
166891 		* doc/c-aarch64.texi: Update docs.
166901 		* doc/c-aarch64.texi: Update docs.
166906 	Patch is adding new 'armv9-a` command line flag to -march for AArch64.
166927 	fail to run to main, for some reason, we'll emit a FAIL.  This is the
166971 	include scoped_fd.h for gdb_fopen_cloexec's and gdb_mkostemp_cloexec's
166981 	My commit 261980de18b added alignment for the resource table symbol.
166985 	Without this patch, if the linker happens to output padding for symbol
167163 	Likewise for an:
167215 		* elf/common.h: Add note segment constants for core files on
167220 	Add support to readelf for reading OpenBSD ELF core notes.
167222 		(process_note): Add support for OpenBSD core notes.
167230 	[gdb/testsuite] Fix gdb.base/break-interp.exp for ld.so without debug
167245 	Add a testcase for PR binutils/27202
167352 		for "Continuing".
167380 	GDB version needed for ARM and PPC32/64.
167390 	So I guess I'm running into the same problem for x86_64.
167495 	      gdb: use libbacktrace to create a better backtrace for fatal signals
167520 	      gdb: print backtrace for internal error/warning
167550 		for DWARF5 files.
167583 	 - On connect, gdbserver sends one stop reply for one thread that is
167588 	 - stop_all_threads sends a stop request for all the running threads and
167589 	   then waits for resulting events
167591 	   makes stop_all_threads not consider it for events
167609 		  for (int i = 0; i < waits_needed; i++)
167620 	events for us.  That's a contradiction, and a sign that something has
167682 	to have a more stable order for printed breakpoint locations, it doesn't
167683 	really matter for this test, and it would be hard to define an order
167694 	When specify a default version for p extension in
167718 	for this case.
167746 	gdb: print backtrace for internal error/warning
167754 	of a backtrace is off for internal-warnings.
167756 	In contrast, printing of a backtrace is on by default for
167816 	gdb: use libbacktrace to create a better backtrace for fatal signals
167821 	However, in order for this API to actually map addresses to symbol
167848 	GCC uses libbacktrace for printing a backtrace when it encounters an
167936 	sub-directories that contain components that should be built for the
167942 	This causes problems for binutils-gdb.  If we run 'make all' in the
167956 	I believe that for binutils-gdb, at least at the moment, there are no
167967 	is that for binutils-gdb no target tools or libraries will be built,
167968 	while for the gcc repository, nothing should change.
167989 	implementation for ar archives fills only the st_mtim.tv_sec part of
167994 		* ar.c (extract_file): Clear buf for preserve_dates.
168001 	that existed and generate a complete init list.  That means for any
168013 	The use of weak symbols ends up causing a problem in practice: for
168022 	Don't print broadcast for scalar_mode, and print {bad} for invalid broadcast.
168035 		(OP_E_memory): Mark invalid broadcast with no_broadcast=1 and Print "{bad}"for it.
168041 	gdb: use intrusive_list for linux-nat lwp_list
168044 	a range.  Add all_lwps_safe as well, for use in iterate_over_lwps, which
168119 	Fix that by creating new spaces for the parent after having moved them
168120 	to the child.  My initial implementation created new spaces for the
168125 	"next" is done.  If we create a new program space for the child and copy
168127 	new symtabs for the child as well.  When the child stop, but still on
168131 	creating new spaces for the parent, we avoid this problem.
168134 	off" and "follow-fork-mode child", because we create new spaces for the
168167 	The check_fork_catchpoints proc also seems used to check for follow-fork
168199 	An off-by-one bug in the check for pptrtab lookup meant that we could
168259 	uint32_t, associated 1:1 with each other). But this is not true for the
168260 	older compiler, for which the sections are different lengths.  We check
168263 	dict, and emit a spurious corruption error for a CTF dict we could
168325 	libctf: try several possibilities for linker versioning flags
168326 	Checking for linker versioning by just grepping ld --help output for
168337 	version script for libctf-nonbfd in particular which doesn't mention any
168358 	nm, so that it can scan generated object files for symbol names for
168360 	BSD-formatted output, so libtool checks for this in its AC_PATH_NM.
168376 	   the top-level Cygnus configure script, which neither tests for
168401 		other workarounds for this problem.  Strip out blank lines from the
168406 	libtool.m4: augment symcode for Solaris 11
168413 		* libtool.m4 (lt_cv_sys_global_symbol_pipe): Augment symcode for
168480 	for gdb.base/check-psymtab.exp due to add_partial_symbol using lowpc without
168489 	try and access source code files, for example, the source code might
168516 	gdb: prevent an assertion when computing the frame_id for an inline frame
168521 	That is, when building the frame_id for an inline frame, GDB asks for
168523 	was returned for the previous frame, and so the assertion triggers.
168530 	However, for whatever reason (e.g. broken debug information, or
168552 	do this we inevitably needing to know the frame_id for frame #0, and
168555 	In compute_frame_id we first find the right unwinder for this frame,
168556 	in our case (i.e. for inline_frame) the $pc is within the function
168561 	Back in compute_frame_id we next compute the frame_id, for our
168567 	another raw frame and calls compute_frame_id (for frames other than
168570 	In compute_frame_id we again identify the correct unwinder for this
168577 	build the frame_id for normal_frame.
168581 	the ID for normal_frame into the frame_id cache, and return the frame
168584 	From inline_frame_this_id we build a frame_id for inline_frame and
168586 	which adds the frame_id for inline_frame into the frame_id cache.
168591 	ask for the previous frame of normal_frame, remember, at this point
168596 	a raw frame and call compute_frame_id, remember, this is for the frame
168599 	The first task for compute_frame_id is to find the unwinder for this
168603 	The inline frame sniffer asks for the $pc, this request is sent up the
168616 	But, we have not yet computed the frame id for the outer most (on the
168624 	Just like before, compute_frame_id tries to find an unwinder for this
168629 	the frame_id for this new copy of normal_frame.
168636 	we try to add the frame_id for the new normal_frame into the frame_id
168696 	cycle detection for inline frames, even when we spot a duplicate frame
168705 	get_prev_frame_always can return nullptr, for example, if there is a
168728 	Contains data for Thread 0x7ffff7fc6b80 (LWP 3551)^M
168735 	The regexp expects "Contains data for process $decimal".
168754 	Cannot find user-level thread for LWP 10324: generic error^M
168758 	for which PR28375 was filed.
168768 	This patch adds a KFAIL for PR28375.
168799 		* testsuite/gas/ppc/power7.s: Remove tests for mfppr, mfppr32, mtppr
168811 	with prepare_for_testing for brevity.
168820 	Don't attempt to access elf_section_data for non-ELF sections.
168824 		for non-ELF.
168833 	Required for the expected "CU:" to be emitted for long
168920 	done to begin with.  I'll have to leave that for another rainy day,
168979 		* gdb.perf/skip-command.exp (run_skip_bench): Wrap each for
169069 	- call function_range for all functions main and foo, without starting a
169073 	- get size for types int and void*
169212 	for { set i 0 } { $i < $argc } { incr i } {
169300 	The problem is that -fPIE and -fpie are gcc options, but for rust we use
169304 	similar to how that is done for ada in target_compile_ada_from_dir.
169306 	Likewise for unix/-fno-PIE/-no-pie.
169355 	fix this by doing info probes and grepping for the address.
169387 	Fix this by instead printing the pc and grepping for the value in the
169598 	This is a testcase for the bug fixed by commit 5b4846283c3d.  When
169601 	sub-sections.  Trying to add nops for ".nop 16" in ".text 1" resulting
169630 …Change the linker's heuristic for computing the entry point for binaries so that shared libraries …
169634 		* ld.texi (Entry point): Update description of heuristic used to
169663 	restarts.  We try to minimize this by doing this only for the few procs that
169746 	[gdb/testsuite] Register test for each arch separately in register_test_foreach_arch
169761 	print_one_insn is registered for each architecture, such that we have:
169794 	[gdb/testsuite] Fix gdb.ada/big_packed_array.exp xfail for -m32
169805 	gcc/101643, and the test-case contains an xfail for this, which catches only:
169824 	    compilation, which is common for building a cross-compiler.
169853 	  Dump of assembler code for function custom_insn:
169862 	  Dump of assembler code for function custom_insn:
169876 	add a test for this change.
169905 		(dwarf2_finish): Call do_allocate_filenum for all subsegs too,
170013 	Multiple matches for s^M
170037 	into the symbol table.  However, that causes regressions for Ada.  It relies
170045 	Note that a fix for the latter was submitted here (
170083 	gcc-11 and gcc-12 pass -gdwarf-5 to gas, in order to prime gas for
170091 	This patch delays allocation of file numbers for gas generated line
170093 	compiler generated file numbers.  Two fixes for test case source are
170109 		(dwarf2_gen_line_info): Set and track filenames for gas generated
170113 		(dwarf2_where): Set u.filename and filenum to -1 for gas generated
170129 	[GOLD] PowerPC64 support for sym+addend GOT entries
170146 	symbol case was already largely handled, except for passing the addend
170150 	I'm assuming here that GOT entries for function symbols won't ever
170199 	Some Output_data_got methods already have support for addends, but
170208 	returns whether there is a GOT entry of type GOT_TYPE for the symbol
170246 	entries against symbol plus addend generally for PowerPC64 rather than
170275 	There are two main reasons for this patch,
170282 	tables, which record names and versions for all supported extensions.
170287 	* We add a new filed `default_enable' for the riscv_supported_std* tables,
170302 		(riscv_implicit_subsets): Added implicit extensions for g.
170306 		(EXT_DEFAULT): Defined for `default_enable' field.
170313 		(riscv_supported_std_z_ext): Likewise, but is used for z* extensions.
170314 		(riscv_supported_std_s_ext): Likewise, but is used for s* extensions.
170315 		(riscv_supported_std_h_ext): Likewise, but is used for h* extensions.
170316 		(riscv_supported_std_zxm_ext): Likewise, but is used for zxm* extensions.
170357 	PASS: gdb.threads/continue-pending-status.exp: attempt 0: continue for ctrl-c
170369 	PASS: gdb.threads/continue-pending-status.exp: attempt 0: continue for ctrl-c
170482 		when calculating space for a string list.
170491 	[bfd] Ensure unique printable names for bfd archs
170494 	Fix printable name for bfd_mach_n1: "nh1" -> "n1".
170499 		* cpu-nds32.c (bfd_nds32_arch): Fix printable name for bfd_mach_n1
170581 	The patch adds a bit to struct partial_die_info, in this hole (shown for
170588 	So there's no increase in size for 64-bit, but AFAIU there will be an increase
170589 	for 32-bit.
170614 	[gdb/symtab] Fix CU list in .debug_names for dummy CUs
170652 	The last two entries are incorrect, and the entries for the dummy CUs are
170667 	  for (int i = 0; i < per_objfile->per_bfd->all_comp_units.size (); ++i)
170684 	  was done for .gdb_index in commit efba5c2319d '[gdb/symtab] Handle PU
170688 	  (and likewise for the TU list).
170711 	This is due a missing .debug_aranges contribution for the CU declared in
170748 	sim: bfin: add support for SDL2
170750 	never.  We keep support for both versions for now since both projects
170766 	[gdb/testsuite] Check for valid test name
170774 	Check for this in ::CheckTestNames::check, such that we have a warning:
170881 	Since the 0x57 is preserved for the vadd.vv instruction in the integration
170886 		for vadd.vv instruction.
170891 …MIPS: don't use get_symbol_name() for section parsing.  With s_change_section() later calling obj_…
170895 …ia64: don't use get_symbol_name() for section parsing.  With cross_section() later calling obj_elf…
170929 	Re: Deprecate a.out support for NetBSD targets
170946 	Add support for checking output, to be able to handle the output regexp
170958 	When running test-case gdb.base/batch-exit-status.exp for native, it passes.
170960 	quotes for clarity):
170973 	have (leaving out set height/width for brevity):
171149 	The .in name has been deprecated for a long time in favor of .ac.
171158 		* dwarf2dbg.c (get_directory_table_entry): Add an argument for
171300 	In GDB we pass Py_TPFLAGS_DEFAULT as part of the tp_flags for all
171311 	Many GNU tools accept -EB/-EL as short options for selecting big &
171313 	spelling out "big" and "little".  Adding support for -EB & -EL is
171316 	sim: ppc: drop support for std-config.h overrides
171318 	All the others expose knobs via configure flags, and for some of
171330 	has moved on long ago, so drop support for these non-standard names.
171331 	POSIX provides O_NONBLOCK for us, so use it everywhere.
171335 	sim: dv-sockser: enable for mingw targets too
171346 	The cgen framework provides a "VOID" type for code to use, but this
171351 	We might want to reconsider the need for "VOID" in cgen, but that
171360 	headers sets us up for pain.  v850 is a good example of this -- when
171361 	building for mingw, we see weird failures:
171396 	It's unclear what this define is for as it appears to be unused, and
171398 	up, and to fix build errors for Windows targets that have a standard
171401 	code for mingw uncovers the conflict.
171436 	logic so we can leverage what the common code already defined for us.
171453 	is par for the course in the ppc code.
171470 	lifting for what boils down to a cast, and is effectively equivalent to all
171483 	local decl for the SIM_DESC type.  Unwinding these will require a
171485 	for now unblocks the warning unification.
171502 …/usr/i686-w64-mingw32/usr/include/rpcndr.h:63:25: error: conflicting types for 'byte'; have 'unsig…
171516 	pair, but there is no support for addiw.  There is also no support for
171519 	as tests for the new feature.
171524 		(print_insn_args): Fix calls to maybe_print_address.  Add checks for
171525 		c.addi, c.addiw, and addiw, and call maybe_print_address for them.
171528 		* testsuite/gas/riscv/insn.d: Update for disassembler change.
171536 	build errors for mingw targets.  Turning format warnings on triggers
171540 	This file is compiled for the --host & --build system which leads to
171555 	dv-sockser module or via direct emulation for a few ports.
171564 	parallel-for-selftests.c.  This fixes a build failure on Windows.
171573 		accessing section contents for various code transformations.
171579 	and I'm not inclined to implement code editing for them.
171582 		transform for R_PPC64_TPREL34.
171594 	common special value for stop_pc though, is set in
171648 	Makefile:1647: recipe for target 'maint.o' failed
171670 	The sim side is already ready to go for cris, so wire it up.
171673 	The sim side is already ready to go for aarch64, so wire it up.
171756 		* elf32-xtensa.c (elf_xtensa_do_reloc): Add check for put of range
171774 		* elfxx-riscv.c (riscv_elf_add_sub_reloc): Add check for out of
171916 	gdbtypes.c: Add the case for FIELD_LOC_KIND_DWARF_BLOCK
171917 	The case for FIELD_LOC_KIND_DWARF_BLOCK was missing for
171934 	On a machine on Open Build Service I'm running into a SIGILL for test-case
171946 	I can't directly access the machine, but looking at the log for test-case
171999 	The original reproducer for PR28030 required use of a specific
172008 	the DWARF assembler to provide debug info for a shared object.  That
172019 	partial backtrace which I include for posterity.
172084 	unhandled case for FIELD_LOC_KIND_DWARF_BLOCK.  The fix for this bug
172085 	adds support for this case.
172089 	used for reproducing this problem in the PR (at
172100 	Frame #7 is a call to the destructor for one of the objfile solibs; it
172101 	turned out to be the one for libstdc++.
172105 	first, followed by internal variables, followed by values for the
172140 	gdb: Enable finish command and inferior calls for _Float16 on amd64 and i386.
172143 	Compiler support for gcc and clang is in progress, see e.g.:
172162 	Add half support for AVX512 register view.
172163 	This adds support for the half datatype, FP16, to the AVX512 register printing.
172185 	gdb, i386: Enable AVX512-bfloat16 for i386 targets.
172273 		* testsuite/ld-srec/srec.exp: Likewise, and for CXX.
172279 	CC_FOR_TARGET to be a compiler for the binutils target machine.  This
172280 	is the compiler that should be used for almost all tests with C
172283 	using CC for the target compiler, and CC_FOR_HOST for the host
172314 		CC_FOR_TARGET, and similarly for CFLAGS, CXX and CXXFLAGS.
172397 …for the haiku operating system.  These are the os support patches we have been grooming and mainta…
172401 	Fix the V850 assembler's generation of relocations for the st.b instruction.
172414 	.symtab_shndx section contents is an array, one entry for each symbol
172425 	PTR_ADD and NPTR_ADD for bfd.h
172430 	NPTR_ADD should be rarely used, but is defined for cases where a
172444 		* objdump.c (disassemble_section): Use PTR_ADD for rel_ppend.
172452 	simplifying __BPTR_ALIGN for the usual case.  I've continued to use
172466 	[ Using $build for /home/vries/gdb_versions/devel/build to make things a bit
172549 	The difference is caused by the result for "info function string_func", which
172550 	is this for the latter:
172558 	but this for the former:
172601 		* gdb.fortran/call-no-debug.exp: Avoid shared lib symbols for
172608 	"objdump -D" for nfp .nffw files.
172639 …Update the how-to-make-a-release document so that a check for empty manual pages is included.  cf …
172649 	may not easy to use for some cases, and not so friendly to users.
172669 		* doc/c-riscv.texi: Document two new .insn formats.
172678 	Use gdbfmt for vprintf_filtered.
172679 	gdbfmt was already used for printf_filtered, so using it for
172694 	The handler for 'info proc status' for native processes on FreeBSD
172696 	output integer values for types such as off_t that are not aliases of
172715 	gdb: fix build error in unittests/parallel-for-selftests.c
172720 	      CXX    unittests/parallel-for-selftests.o
172721 …   cc1plus: warning: command line option '-Wmissing-prototypes' is valid for C/ObjC but not for C++
172722 …/home/smarchi/src/binutils-gdb/gdb/unittests/parallel-for-selftests.c: In function 'void selftests…
172723 …/home/smarchi/src/binutils-gdb/gdb/unittests/parallel-for-selftests.c:53:30: error: use of deleted…
172728 	                     from /home/smarchi/src/binutils-gdb/gdb/../gdbsupport/parallel-for.h:26,
172729 	                     from /home/smarchi/src/binutils-gdb/gdb/unittests/parallel-for-selftests.c:22:
172776 	different settings for the number of threads will work.  This test
172781 	Add a show function for "maint show worker-threads"
172791 	[gdb/cli] Don't assert on empty string for core-file
172862 	   e:   0001             nop                 # Marked $x, nops for alignment.
172873 	  fill nops for them.
172877 	  the spaces.  Therefore, add a $d mapping symbol for the odd byte,
172904 		(riscv_mapping_state): Decide whether to create mapping symbol for
172906 		(riscv_add_odd_padding_symbol): Add the mapping symbols for the
172911 		(riscv_init_frag): Add mapping symbols for frag, it usually called
172912 		by frag_var.  Marked as MAP_DATA for rs_align and rs_fill, and
172913 		marked as MAP_INSN for rs_align_code.
172918 		(TC_SEGMENT_INFO_TYPE): Record mapping state for each segment.
172919 		(TC_FRAG_TYPE): Record the first and last mapping symbols for the
173043 	When comparing the sizes of the index files generated for shlib
173120 	debug section.  So, the intent for the .debug_aranges section in watch-loc.c
173142 	[gdb/testsuite] Generate .debug_aranges entry for dummy CU
173143 	A best practise for DWARF [1] is to generate .debug_aranges entries for CUs
173146 	Generate .debug_arange entries for the dummy CUs added by the DWARF assembler.
173156 	to missing .debug_aranges entries for the CUs added by the dwarf assembler.
173158 	Add a .debug_aranges entry for those CUs.
173208 	silently result in the wrong value for the label.
173273 	is seen on mingw for the simple reason that gcc adds a .exe suffix on
173371 	The test-case contains a KFAIL for PR12497, but it's outdated and fails to
173377 	Supporting compiler-generated stabs is already a corner-case for gdb, and
173399 	On openSUSE Leap 15.2 and Tumbleweed, the CU for hello.c is typically not the
173401 	objects for sources like:
173408 	On other systems, say ubuntu 18.04.5, the CU for hello.c is typically the
173460 	sim: m32r: add __linux__ hack for non-Linux hosts
173463 	This breaks building for non-Linux systems, so put all the code in
173465 	work everywhere, but let's at least unbreak it for non-Linux hosts.
173478 	In preparation for this script generating more files, change the output
173541 	Add a method to set the gcc target options for the ppc64 targets.
173556 	Allow the test to pass for such targets.  Fixes the following.
173574 	[GOLD] PowerPC64 relocation overflow for -Os register save/restore funcs
173601 	Now that ChangeLog entries are no longer used for sim patches,
173635 	opcodes: Fix the auxiliary register numbers for ARC HS
173636 	The numbers for the auxiliary registers "tlbindex" and
173656 	should never be accessed for Linux.  glibc is planning to add a field
173659 	to set r_ldsomap_offset to -1 and use them for Linux targets.
173665 	gdbserver: Check r_version < 1 for Linux debugger interface
173667 	that r_version can be bumped for a new field in the glibc debugger
173669 	only reads fields defined for r_version == 1, it is compatible with
173673 	If there is ever the need for backward incompatible change to the glibc
173807 	directive outputs is always 10 bytes.  There is no need for fp-elf32 nor
173846 	regression.  (It doesn't happen for any of the other cross targets
173882 	... slightly changes the logic here.  In particular, it's possible for
173912 	- A Python event handler for breakpoint_modified using the "enabled"
173917 	code and implements corresponding tests for the MI and Python cases.
173987 		state rule.  Comment on lookahead state madness and need for
173998 		* ld.texi: Remove sizeof_headers index.
174024 	Stack overflow with a large float. %f is not a goot choice for this.
174028 		* testsuite/gas/csky/pr28168.d: New testcase for PR 28168.
174038 	the need to do so for phdrs like ":text".  Instead {WILDCHAR}*
174046 	SCRIPT for tokens that only need EXPRESSION state, and two where BOTH
174059 		Similarly for OVERLAY.
174103 	On my platform, I do not have debug symbols for glibc, so I need to rely
174109 		Dump of assembler code for function __pthread_clockjoin_ex:
174130 	we are looking for in order to identify the caller.
174143 	add support for the ld instruction in the RISC-V prologue scanner.
174145 	support for this instruction.
174171 	that Pygments may be used for source highlighting.  This patch updates
174179 	std::vector and update callers.  That makes it easier for everyone
174190 	assembly/codegen for the powerpc target includes a NOP after the
174215 	Function of parsing target-description.xml will be add later for CSKY arch,
174283 	Updated Portuguese translation for the binutils sub-directory.
174287 	Deprecate a.out support for NetBSD targets.
174308 	--target=vax-unknown-netbsdaout builds completely except for gas, where
174356 	Register handlers for SIGBUS, SIGFPE, and SIGABRT.  All of these
174367 	I've added new tests for SIGFPE, SIGBUS, and SIGABRT.
174378 	check for these features, if they are not available then the new code
174381 	The motivation for this new feature is to aid in debugging GDB in
174407 	exits, in bash for example "Segmentation fault" rather than "Aborted".
174438 	not being built with -rdynamic as the manual page for
174440 	to the build of GDB I only see symbols for some addresses.
174450 	The async_init_signals has, for some time, dealt with async and sync
174460 	The comments for SIGTRAP talk about the signal disposition (SIG_IGN)
174466 	The comments for SIGQUIT are similarly out of date, further, the
174468 	however, we have not supported BSD4.3 for several years now.
174471 	no longer needed, so I've deleted the signal() call for SIGTRAP.
174508 	There are no tests for this.  Trying to land a signal in the right
174541 	signal (for now).
174587 		* ldlex.l: Combine rules for handling newline, whitespace and
174594 	token.  Let's use a better name.  The formatting changes are for
174611 		* ld.texi (expressions): Mention need for whitespace.
174641 	Like for infinity, there isn't just a single NaN. The sign bit may be
174648 	with all non-significant mantissa bits clear was chose for an unknown
174686 	well. To be able to also use the hex forms supported for other floating
174696 	supported for other floating point formats, a small addition to the
174710 	also for non-ELF targets; so far they were different depending on input
174726 	Note that for now padding space doesn't get separated from actual
174727 	storage, which means that things will work correctly only for little-
174730 	for a single little-endian architecture only for now, I'm hoping that
174731 	this might be acceptable for the time being; otherwise the change will
174735 	line for non-ELF targets as well; the issue will be even more obvious
174747 	handling such padding, and specify the needed padding for x86 (leaving
174748 	non-ELF targets alone for now). Split the existing x86 testcase.
174752 	ELF. None of the newly enabled tests in the testsuite fail for me.
174759 	for rl78_special_reloc, a function primarily used when applying debug
174771 		bitsize of DIR32_REV.  Correct complain_on_overflow for many relocs
174773 		for RH_SADDR.  Set size to 3 and bitsize to 0 for all OP relocs.
174776 		Apply relocations using reloc howto.  Check for overflow.
174802 	fission-reread.exp is updated to test for the bug.
174830 	other inferior.  The chances of the stars aligning for this to happen
174843 	Updated Serbian and Russian translations for various sub-directories
174857 	able to refer to a GDB smob type, for instance:
174869 	say: not crippling for the most part, but makes certain tasks more
174947 	the patch is tidying up error reporting, so that for example, linking
174997 	The way that init.c is generated does not allow for an initialization
175006 	[gdb/symtab] Fix zero address complaint for shlib
175057 	The partial symtab that is found for the addresses is instead the one for
175110 	but it's called for a function at DIE 0x54153 with DW_AT_ranges at 0x40ae:
175129 	Same for dwarf2_ranges_process.
175156 	Re: Add tests for Intel AVX512_FP16 instructions
175200 		(nds32_info_to_howto_rel): Test for NULL howto or howto name
175203 		Test for NULL howto or howto name return from lookup.
175236 	[gdb] Handle .TOC. sections during gdb-compile for rs6000 target.
175237 	[gdb] Handle .TOC. sections during gdb-compile for rs6000 target.
175280 	for incoming connections.  This is documented in PR 19558 [1].
175282 	Make the expected output regexp for the kill command tighter (it
175354 	gdb: target_waitstatus_to_string: print extra info for FORKED, VFORKED, EXECD
175355 	Print the extra information contained in target_waitstatus for these
175359 	Print it using the same format used for TARGET_WAITKIND_STOPPED and
175362 	Here are sample outputs for all three events:
175382 	for debug purposes.  It formats the ptid exactly as is done in
175415 	Idea of this patch is to get a clean and simple public interface for
175492 	At this point, all conditions are met for the DWARF evaluator to return
175517 	and initialized members of the struct value. This is needed for the
175531 	logical step is to make a clean user interface for that class. To do
175535 	Fixing the case of writing is simple, it makes sense for an evaluator
175544 	class constructor argument, at least until a better interface for
175550 	of evaluating expression is representing. So, it makes sense for all of
175568 	all infrastructure for those location descriptions to the expr.c file
175658 	There might be a need for a better class hierarchy when we know more
175832 		check for DW_OP_call_frame_cfa. Remove use of get_frame_cfa.
175855 	  subclass lacks the support for composite as well as implicit pointer
175861 	  a full support for all location description types.
175865 	  support for passed in buffers. This seems to be a way to go around
175866 	  the fact that DWARF standard lacks a bit offset support for memory
175867 	  location descriptions as well as using any location description for
175887 	The thing that makes more sense for an evaluator to do, is to take the
175890 	report an error only if parts of the context, necessary for the
175904 	a caller poking around the dwarf_expr_context internal data for answers
175948 	Move the initial values for dwarf_expr_context class data members
175969 	DWARF expression evaluation mechanism for different evaluation
175983 	   class). This evaluator expects all information needed for the
175994 	information are needed for the given DWARF expression to be evaluated by
176098 	To better explain the proposed solution for the issue, I first need to
176102 	for different purposes. Some are in charge of converting the expression
176105 	analysing the expression for specific information
176114 	As a step into the right direction to solve this problem (at least for
176117 	makes sense for all derived classes, except for the symbol needs
176126 	fit for this evaluator is to be a symbol needs analysis, similar to the
176140 	is needed for their evaluation.
176144 	a lightweight mechnism and it will provide a correct result for any
176150 	class would be used as a base for all DWARF expression parsing mentioned
176156 	The new analysis requires the DWARF location description for the
176184 	[PATCH 2/2] Add tests for Intel AVX512_FP16 instructions
176186 	in the EVEX.mmm field (0b101, 0b110). Map 5 is for instructions that were FP32
176187 	in map 1 (0Fxx). Map 6 is for instructions that were FP32 in map 2 (0F38xx).
176190 	FP32 things in map 3 (0F3Axx) found new opcodes in map3 for FP16 because map3
176195 	to the public software developer manual for detail information.
176239 	in the EVEX.mmm field (0b101, 0b110). Map 5 is for instructions that were FP32
176240 	in map 1 (0Fxx). Map 6 is for instructions that were FP32 in map 2 (0F38xx).
176243 	FP32 things in map 3 (0F3Axx) found new opcodes in map3 for FP16 because map3
176248 	to the public software developer manual for detail information.
176267 		* doc/c-i386.texi: Document avx512_fp16, noavx512_fp16.
176309 		* i386-dis-evex.h: Updated for AVX512_FP16.
176310 		* i386-dis-evex-mod.h: Updated for AVX512_FP16.
176311 		* i386-dis-evex-prefix.h: Updated for AVX512_FP16.
176312 		* i386-dis-evex-reg.h : Updated for AVX512_FP16.
176313 		* i386-dis-evex-w.h : Updated for AVX512_FP16.
176359 		* ld-cris/libdso-1c.d: Update for version display change.
176377 	then fails to "fix" this $pc (for the new thread), and the thread will
176457 	for gcc.  Other macro tests such as gdb.base/macscp.exp do perfectly
176490 	Fix that by propagating down a gdb::optional<ULONGEST> for the str
176518 	necessary for a complaint nobody is going to see.
176553 	NULL output_bfd.  As expected for reloc special functions if called by
176559 	value can be one for a shared library?  But that doesn't seem useful
176569 	for all gp-relative reloc symbols.
176582 	which removes the need for static variables.
176637 	                    "for mutable addrmaps"));
176678 	Most of the algorithms for XCOFF in tc-ppc.c assume that
176680 	This was already made for most of the sections with the creation
176704 		* ld.texi (Options <runtime library name>): Correct grammar.
176740 	inferior is created for the child, do we need to detach from the child)
176752 	   created for the child, because we want to detach from it.
176763 	   thread (just like we do for follow_exec).
176810 	Fixes for mi-fortran-modules.exp fixes
176811 	Output has additional information for a given filename.
176815 		system_module_symbols_pattern): Add check for additional symbols
176866 	Please note that error message contains '&' for cstring, which is absent
176910 	Handle type qualifier for enumeration name
176934 	For an expression like TYPE'(EXP), the conversion would be done for
177025 	The test expects the dwarf error, but has no matching pattern for the entire
177068 	Error while writing index for `gdb-index-nodebug': \
177149 	Although this is not a problem for "false" (0), it definitely
177150 	causes trouble for "true".
177155 	The issue tackled here was first encountered for arc-elf32 target
177157 	has passed for all the targets (--enable-targets=all) running on the
177176 	Statistics for 'maint':^M
177185 	  Total memory used for objfile obstack: 20320^M
177186 	  Total memory used for BFD obstack: 4064^M
177187 	  Total memory used for string cache: 4064^M
177289 		Call xcoff_mark for special sessions being kept instead of just
177316 	Section reloc_count is an unsigned int.  Adding one for a NULL
177369 	too big as well, so we don't need a separate assertion for that.
177386 	obsd-nat: Various fixes for fork following.
177392 	  ptrace ops have been present in OpenBSD for at least 10 years.
177401 	  first event for a process is a PTRACE_FORK event.  This also
177411 	  Replace a check for WIFSTOPPED on the returned status from waitpid
177412 	  by checking for TARGET_WAITKIND_STOPPED in the parsed status as is
177473 	- Don't include x86-nat.o and nat/x86-dregs.o for OpenBSD/amd64.  They
177474 	  were already omitted for OpenBSD/i386.
177478 	Fix for gdb.tui/tui-layout-asm.exp
177491 		tui_asm_window_width variable for the width. Add if
177515 	type for the #:type argument triggers a failed assertion in
177518 	code path for pointers.
177528 		* gdbtypes.c (get_pointer_type_max): Add definition for new
177531 		for handling conversions to pointer types without failing an
177539 		for creating pointers with make-value.
177541 		test procedures containing checks for integer-to-pointer
177604 	Adds API to the Guile bindings for creating temporary breakpoints and
177610 	Python implementation, but might be a bit surprising for users.
177618 		(temporary_keyword): Add keyword object for make-breakpoint
177639 		* guile.texi (Breakpoints In Guile): Update make-breakpoint
177641 		Add documentation for new breakpoint-temporary? procedure.
177647 		* gdb.guile/scm-breakpoint.exp: Add additional tests for
177662 	   don't think this is used.  It could be used by a GDBserver built for
177667 	 - There are a bunch of *-expedite values in features/Makefile for
177668 	   architectures for which we don't generate dat files.  AFAIK, these
177681 	x86: Simplify check for distinct TMM register operands
177684 	check for distinct TMM register operands since all TMM register operands
177688 		call when checking for distinct TMM register operands.
177692 	ld: Run tmpdir/pr28138 only for native build
177694 		* testsuite/ld-plugin/lto.exp: Run tmpdir/pr28138 only for
177742 	makeinfo options for texi2pod.pl wrapper. Unsupported option
177777 	commit 0057a7ee0d9 "[gdb/testsuite] Add KFAILs for gdb.ada FAILs with
177779 	the default for gcc-11.  I keep getting confused because of working with a
177834 	Then in attr_to_dynamic_prop for the upper bound, we get a PROC_LOCEXPR
177869 	This change adds an external-visible wrapper for the _bfd_set_gp_value
177870 	function.  This is a prerequisite for some gdb patches that better
177874 		for _bfd_set_gp_value.
177879 	PowerPC: ignore sticky options for .machine
177880 	PowerPC gas and objdump for a long time have allowed certain -m/-M
177915 	It's just wrong to choose power5 for a bunch of altivec instructions
177927 	[gdb/testsuite] Add xfail for PR gcc/101643
177958 	[gdb/testsuite] Add xfail for PR gcc/101633
178017 	The second issue addressed in this commit has existed for a while in
178022 	We attempt to get the frame_id for a frame while we are computing the
178023 	frame_id for that same frame.
178025 	What happens is that when GDB stops we create a frame_info object for
178027 	frame to create a frame_info object for frame #0.
178034 	The frame-id stored in the lazy register value will be for the
178035 	sentinel frame (lazy register values hold the frame-id for the frame
178048 	Where 'frame=%d' will be the relative frame level of the frame for
178052 	frame-id for frame #-1 (the sentinel frame).
178054 	So, to get the frame_info for frame #0 we used to call:
178062 	That is, we start with the frame-id for the next frame as obtained by
178066 	The get_prev_frame_id_by_id function finds the frame_info for the
178085 	  4. Get the frame_id for that frame, and
178109 	frame_id for a frame, however, we could make value_assign slightly
178120 	was able to create an alternative test for this issue by enabling
178124 	have a reproducer attached so it is not possible to know for sure.
178156 	Fix for mi-reverse.exp
178159 	expression to allow for more significant digits on the constant.
178164 		for additional digits.
178174 	gdb: Fix numerical field extraction for target description "flags"
178175 	The "val_print_type_code_flags ()" function is responsible for
178176 	extraction of fields for "flags" data type.  These data types are
178178 	XML.  The logic used for the extraction though is not sound:
178203 	PATCH [10/10] arm: Alias 'ra_auth_code' to r12 for pacbti.
178211 	PATCH [9/10] arm: add 'pacg' instruction for Armv8.1-M pacbti extension
178228 	PATCH [8/10] arm: add 'autg' instruction for Armv8.1-M pacbti extension
178244 	PATCH [7/10] arm: add 'bxaut' instruction for Armv8.1-M pacbti extension
178284 		(ARM_FEATURE_ZERO, ARM_FEATURE_CORE_EQUAL): Account for
178290 	PATCH [4/10] arm: add 'pac' instruction for Armv8.1-M pacbti extension
178308 	PATCH [3/10] arm: add 'aut' instruction for Armv8.1-M pacbti extension
178326 	PATCH [2/10] arm: add 'pacbti' instruction for Armv8.1-M pacbti extension
178332 		(parse_operands): Add switch cases for OP_SP and OP_R12.
178349 	PATCH [1/10] arm: add 'bti' instruction for Armv8.1-M pacbti extension
178392 	gdb/mi: handle no condition argument case for -break-condition
178395 	condition for breakpoint 2, just like CLI's "condition 2", but instead
178433 		* testsuite/gas/ppc/power4.d: Adjust for section sym change.
178437 		* testsuite/ld-powerpc/tlsexe.r: Adjust for section sym change.
178460 		(exp): Use it for ALIGNOF, SIZEOF, ADDR, and LOADADDR.  Similarly
178461 		ensure script mode parsing for section name in SEGMENT_START.
178492 	series, so thought it would be good to have a test for it.
178496 	parameter for this.  Nevertheless, changing this behavior could break
178497 	some scripts, which is why I think it's important for it to be tested.
178505 	cmd_list_element::function is for.  Compared to cmd_simple_func_ftype,
178507 	to the cmd_list_element for the command being invoked.  This allows
178512 	was the callback function type for set and show functions, hence the
178513 	"s".  But nowadays, it's used for many more commands that need to access
178514 	the cmd_list_element object (see add_catch_command for example).
178523 	use it for cmd_list_element::func, as well as for the add_setshow
178531 	After browsing the CLI code for quite a while and trying really hard, I
178548 	parameter.  So the only reason I see for cfunc to exist is to be a shim
178561 	Same idea as the previous patch, but for m_terminal.
178568 	Same idea as the previous patch, but for m_cwd.
178581 	has the advantage that there is now a single state for that (an empty
178588 	gdb: add setter/getter for inferior cwd
178598 	gdb: add setter/getter for inferior arguments
178612 	This last one is only used for arguments passed in GDB's
178636 	The motivation for this is that a future patch will change the prototype
178637 	of set_inferior_cwd in gdb, and I don't want to change it for gdbserver
178688 	Fix for gdb.python/py-breakpoint.exp
178695 		check for hardware breakpoint support.
178734 	The problem here is that we check for the existence of spawn_out, and
178739 	specifically for spawn_out(slave,name).
178750 	While EVEX.L'L are indeed ignored when EVEX.b stands for just SAE,
178812 		* gdb.ada/formatted_ref.exp: Add xfail for PR gcc/101575.
178819 	Their sole use is for {,V}EXTRACTPS / {,V}P{EXT,INS}RB respectively; for
178824 	{,V}PEXTRW then also need adjustment for consistency reasons.
178835 	The bulk of OP_XMM() can be easily reused also for OP_EX(). Break the
178844 	outside of 64-bit mode. Oddly enough there already are tests for these
178852 	What so far was OP_E_register() can be easily reused also for OP_G().
178863 	EVEX.R' is invalid to be clear not only for mask registers, but also for
178870 	(like for other insns without rounding semantics) EVEX.b set causes #UD.
178975 	Updated Russian translation for the bfd library
178980 	* ld.texi: Document new output section type.
179032 	[gdb/testsuite] Add KFAILs for gdb.ada FAILs with gcc-11
179049 	as a KFAIL for PR ada/28115 - "Support packed array encoded as
179058 		* gdb.ada/arrayptr.exp: Add KFAILs for PR20991 and PR28115.
179059 		* gdb.ada/exprs.exp: Add KFAILs for PR20991.
179127 	additionally marked as obsolete next to the other removed ones for
179188 	The same happens for complex types and printing struct/union types.
179198 	(i.e., no sense in validating tags after "print 1"), and throws for
179206 	escapes out and aborts the print.  This case is fixed by checking for
179237 	RISC-V: Minor updates for architecture parser.
179436 	fails.  This came up for me because my new DWARF scanner reuses this
179442 	for this, and in fact, it seemed to me that the index code could
179468 	Check for debug-types in map_symbol_filenames
179487 	string without also having to maintain the storage for it.  So, this
179488 	patch arranges for the compilation directory string to be stored in
179593 	With this, gdb.threads/fork-plus-threads.exp is passing once again for
179620 	This patch adds support for stepping outside of a signal handler on
179637 	This feature requires hardware support for single stepping (or at least
179686 		in switch case R_OR1K_INSN_REL_26 where we need to check for
179691 	Updated Swedish translation for the binutils sub-directory
179766 	 - there's something fishy for the second solib_create_inferior_hook
179770 	   check_for_thread_db, for example) is called with inferior 1 as the
179811 	   inferior 1, the parent.  Because libthread_db is already loaded for
179830 	code objects for each inferior.  For the purpose of this test, add the
179833 	bare, but it's good enough for the test.
179909 	a problem for some targets, the problem being that a non-zero
179926 		* config/tc-alpha.h (TC_VALIDATE_FIX_SUB): Define for ECOFF.
179927 		* config/tc-ppc.h (TC_VALIDATE_FIX_SUB): Don't define for ELF.
179928 		Do define for XCOFF.
179932 	objdump: add DWARF support for AIX
179935 	This patch also adds the correlation in bfd for future uses.
179984 	.gdb_index for symbol loading.
180027 	While testing the NixOS[1] packaging for gdb-11.0.90.tar.xz, I got the
180036 	  make[2]: *** Waiting for unfinished jobs....
180041 …builder for '/nix/store/xs8my3rrc3l4kdlbpx0azh6q0v0jxphr-gdb-gdb-11.0.90.drv' failed with exit cod…
180129 	That's a dtor, thus noexcept.  That's the reason for the
180161 	to GDB 10, if it weren't for the previous fix.
180233 	That's a dtor, thus noexcept.  That's the reason for the
180251 	disable the "target:" sysroot, for test run speed reasons.  So this
180309 	         we only fake a special descriptor for the initial thread.  */
180339 		* gdb.threads/check-libthread-db.exp: Update patterns for glibc 2.33.
180414 	requirement for calling target_stop, as documented in
180424 	the moment (which is why this bug could creep in).  Add a new test for
180448 	elf attributes for all riscv targets by default in gcc.  Therefore, I
180451 	enable the elf attributes for all riscv targets by default.
180457 		* testsuite/binutils-all/readelf.s: Add comments for riscv.
180467 		then we enable the elf attributes for all riscv targets by
180491 	spend time iterating on threads to find the one we are looking for.  The
180554 	responsible for selecting a thread from an inferior among all that are
180562 	(random_pending_event_thread looks for an thread from a specific
180583 	pathological case.  And a possible fix for this situation would be to
180591 …gdb: optimize check for resumed threads with pending wait status in maybe_set_commit_resumed_all_t…
180607 	method for this, and use it in maybe_set_commit_resumed_all_targets.
180630 	consume, before asking the targets for more events.
180673 	representation of the ptid that is meant for debug messages, a bit like
180683 	thread_info for the pending waitstatus, so that we can add some code in
180691 	setters for all of its fields:
180719 	I want to make it clear that this is to be used only for backing up and
180736 	thread_info::suspend::waitstatus to store some statuses temporarily, for
180757 	we print the stop for that interesting thread:
180786 	However, given that the pending waitstatus for the thread may have been
180793 	thread is the last one for which print_one_stopped_thread is called.  So
180803 	gdb: add setter / getter for thread_info resumed state
180806 	add a getter and a setter for it.  The following patch in question will
180813 	gdb: use intrusive list for step-over chain
180816 	candidate for intrusive_list, convert it.
180829 	the copy-assignment operator is.  But for completeness, add both.
180867 	eliminate the need for that walk, we could make those lists
180873 	list without destroying them, which is interesting in our case for
180874 	example for threads, when we exit them, but can't destroy them
180886 	for requiring extra memory allocations.  For an example of an object
180923 	This wasn't great for when debugging GDB with GDB, as it was difficult
180973 	pretty-printer yields pointers.  The reason for this is that the output
181020 		* gdb.btrace/tsx.exp: Add pattern for system with tsx disabled in
181025 	Updated French translation for the binutils sub-directory
181027 …Fix a translation problem for the text generated by readelf at the start of a dump of a dynamic se…
181033 	[gdb/testsuite] Fix gdb.mi/mi-info-sources.exp for extra debug info
181050 	  -file-list-exec-source-files --group-by-objfile, look for \
181053 	  -file-list-exec-source-files --group-by-objfile, look for \
181056 	due to openSUSE executables which have debug info for objects from sources
181077 		Skip tests for readnow.  Use "maint expand-symtabs".
181107 	leb128 data is of indeterminate length, perfect for fuzzer mayhem.
181144 	-z [no]indirect-extern-access are only for x86 ELF linker.
181150 	-z [no]indirect-extern-access to linker, only run for Linux/x86 targets.
181152 		* testsuite/ld-elf/property-1_needed-1b.d: Only run for
181180 		Set needed_1_p for GNU_PROPERTY_1_NEEDED in memory.
181182 		GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS for
181184 		extern_protected_data to false for indirect external access.
181190 		* elflink.c (_bfd_elf_symbol_refs_local_p): Return true for
181193 		indirect_extern_access for legacy non-GOT/non-PLT references.
181205 		* ld.texi: Document -z [no]indirect-extern-access
181231 		* testsuite/ld-x86-64/x86-64.exp: Run tests for protected
181349 		* ld.texi: Document --max-cache-size=SIZE.
181354 		* testsuite/ld-bootstrap/bootstrap.exp: Add test for
181379 	The problem happens when linux_displaced_step_prepare is called for the
181381 	sees that the number of displaced stepping buffers for that architecture
181400 	even for non-Linux system.  Maybe that was on purpose, because it would
181478 	Updated Portuguese translation for the BFD sub-directory
181525 	sim: erc32: use libsim.a for common objects
181545 	ld: Check archive only for archive member
181561 		* plugin.c (plugin_input_file): Add comments for abfd and ibfd.
181567 	Add changelog entries for last commit
181636 	Check for strnlen declaration to fix Solaris 10 build
181658 		* configure.ac: Check for strnlen declaration.
181662 		* configure.ac: Check for strnlen declaration.
181736 	However, I added a `next_range` wrapper as a direct replacement for
181811 	for some people, I propose re-adding it.
181837 	Now that ChangeLog entries are no longer used for GDB patches,
181864 	the fix for PR22756 only changed behaviour for hidden aliases,
181865 	but the same situation exists for non-hidden aliases: sym_hashes[]
181869 	Fix this by testing for duplicates for everything that looks like it
181875 		* elfnn-riscv.c (riscv_relax_delete_bytes): Check for any
181994 	 - checks for Python errors
182068 		(riscv_elf_modify_segment_map): Added ATTRIBUTE_UNUSED for the
182091 	Tested on x86_64-linux (openSUSE Leap 15.2), no regressions for config:
182140 		section for simplify testcase.
182181 	I am not sure a test case for this is possible.  I think it can only
182198 	Linker plugin_object_p opens the IR archive for each IR archive member.
182200 	for LLVM plugin, the archive file descriptor remains open.  If there are
182201 	3000 IR archive members, there are 3000 file descriptors for them.  We
182205 	we can cache and reuse the IR archive file descriptor for all IR archive
182243 …The commit allows options to be set for the AR and RANLIB programs used when building libiberty, w…
182250 	Since commit 05b85772061 "gdb/fortran: Add type info of formal parameter for
182264 	which fails to take into account that for gcc-7 and before, the type for
182276 		$integer4 for size of string length.
182292 	keep using sigtimedwait for the platforms that provide it, and fall back
182293 	to sigpending + sigwait for the others.
182306 	gdbsupport/common.m4: check for sigtimedwait
182308 	the platform provides it.  Start by adding a configure check for it.
182312 		* common.m4 (GDB_AC_COMMON): Check for sigtimedwait.
182339 	NULL when a reloc special_function is called for final linking and
182347 		* elf64-bpf.c (bpf_elf_generic_reloc): Use correct bfd for bfd_put
182400 	commit ea142fbfc9c1 ("Fix breakpoints on file reloads for PIE
182431 		* NEWS: Create a new section for the next release branch.