]>
git.ipfire.org Git - thirdparty/binutils-gdb.git/log
Alan Modra [Fri, 16 Aug 2019 03:50:28 +0000 (13:20 +0930)]
PowerPC gcc bootstrap fail with bss-plt
git commit
3e04d7655b introduced a bug by sizing output sections
earlier in ppc_before_allocation. That meant PLT (and GOT) sizes were
not included when calculating total executable section sizes.
* emultempl/ppc32elf.em (ppc_before_allocation): Force running
prelim_size_sections before deciding whether branch trampolines
might be needed.
(cherry picked from commit
7df6aecc97b96843da080d54414052b1c954ddca )
GDB Administrator [Sat, 17 Aug 2019 00:01:27 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 16 Aug 2019 00:01:18 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 15 Aug 2019 00:01:34 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 14 Aug 2019 00:01:23 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 13 Aug 2019 00:01:25 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 12 Aug 2019 00:01:21 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 11 Aug 2019 00:02:01 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 10 Aug 2019 00:01:18 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 9 Aug 2019 00:01:20 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 8 Aug 2019 00:02:18 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 7 Aug 2019 00:02:50 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 6 Aug 2019 00:01:19 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 5 Aug 2019 00:01:17 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 4 Aug 2019 00:01:59 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 3 Aug 2019 00:01:12 +0000 (00:01 +0000)]
Automatic date update in version.in
Wu Heng [Fri, 25 Jan 2019 03:11:47 +0000 (13:41 +1030)]
PR23940, check bounds before using
PR gas/23940
* macro.c (getstring): Check array bound before accessing.
(cherry picked from commit
10c172ba93dde7cb7c46982ca217e646565bf938 )
GDB Administrator [Fri, 2 Aug 2019 00:02:11 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 1 Aug 2019 00:01:17 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 31 Jul 2019 00:02:17 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 30 Jul 2019 00:01:20 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 29 Jul 2019 00:01:19 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 28 Jul 2019 00:02:49 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 27 Jul 2019 00:01:20 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 26 Jul 2019 00:01:28 +0000 (00:01 +0000)]
Automatic date update in version.in
Srinath Parvathaneni [Mon, 22 Jul 2019 13:46:11 +0000 (14:46 +0100)]
[ARM]: Correct the regular expressions in cmse_main_sec_debug.d file.
Fixes the linker testcase "Secure gateway veneers:cmse functions debug
information missing" which was failing due to output regular expression
mismatch on arm-none-linux-gnueabihf targets.
* ld/testsuite/ld-arm/cmse_main_sec_debug.d: Modify regexps to
allow for output from a arm-none-linux-gnueabihf target.
(cherry picked from commit
0c628bba5afd16e0ab3d78ca81ab3f2d5342c50c )
Committed on behalf of Srinath Parvathaneni.
GDB Administrator [Thu, 25 Jul 2019 00:01:30 +0000 (00:01 +0000)]
Automatic date update in version.in
Kyrylo Tkachov [Wed, 24 Jul 2019 11:27:35 +0000 (12:27 +0100)]
[AArch64] Add support for GMID_EL1 register for +memtag
We're missing support for the GMID_EL1 system register from the Memory Tagging Extension in binutils.
This is specified at:
https://developer.arm.com/docs/ddi0595/latest/aarch64-system-registers/gmid_el1
This simple patch adds the support for this read-only register.
Tested make check on gas.
Backport from mainline
2019-07-23 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
* aarch64-opc.c (aarch64_sys_regs): Add gmid_el1 entry.
(aarch64_sys_reg_supported_p): Handle gmid_el1 encoding.
Backport from mainline
2019-07-23 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
* testsuite/gas/aarch64/sysreg-4.s: Test gmid_el1 read.
* testsuite/gas/aarch64/sysreg-4.d: Update expected output.
* testsuite/gas/aarch64/illegal-sysreg-4.l: Likewise.
GDB Administrator [Wed, 24 Jul 2019 00:01:20 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 23 Jul 2019 00:02:40 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 22 Jul 2019 00:01:24 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 21 Jul 2019 00:02:00 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 20 Jul 2019 00:01:23 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 19 Jul 2019 00:01:22 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 18 Jul 2019 00:01:23 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 17 Jul 2019 00:01:17 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 16 Jul 2019 00:01:33 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 15 Jul 2019 00:01:26 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 14 Jul 2019 00:01:58 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 13 Jul 2019 00:01:19 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 12 Jul 2019 00:01:21 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 11 Jul 2019 00:01:29 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 10 Jul 2019 00:01:42 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 9 Jul 2019 00:01:11 +0000 (00:01 +0000)]
Automatic date update in version.in
Szabolcs Nagy [Mon, 8 Jul 2019 12:57:43 +0000 (13:57 +0100)]
aarch64: fix DT_AARCH64_VARIANT_PCS handling in readelf
backport commit
13acf03468d1e218c0a980ff6e6adaaac4bb5d1e
failed to copy the changes in get_dynamic_type.
this could cause build failure
binutils/readelf.c:1800:1: warning: 'get_aarch64_dynamic_type' defined but not used [-Wunused-function]
binutils/ChangeLog:
2019-07-08 Szabolcs Nagy <szabolcs.nagy@arm.com>
* readelf.c (get_dynamic_type): Handle EM_AARCH64.
Alan Modra [Mon, 8 Jul 2019 00:36:09 +0000 (10:06 +0930)]
PR24785, bfd crashes on empty .PPC.EMB.apuinfo section
PR 24785
* elf32-ppc.c (_bfd_elf_ppc_set_arch): Sanity check .PPC.EMB.apuinfo
size before reading first word.
(cherry picked from commit
62a47958bd6e3cbd909c2f19cd4669a9670ce4f1 )
GDB Administrator [Mon, 8 Jul 2019 00:01:24 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 7 Jul 2019 00:02:01 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 6 Jul 2019 00:01:22 +0000 (00:01 +0000)]
Automatic date update in version.in
Szabolcs Nagy [Thu, 25 Apr 2019 14:07:14 +0000 (15:07 +0100)]
aarch64: handle STO_AARCH64_VARIANT_PCS in bfd
Backport commit
823710d5856996d1f54f04ecb2f7647aeae99b5b
Backport commit
65f381e729bedb933f3e1376e7f53f0ff63ac9a8
Propagate STO_AARCH64_VARIANT_PCS st_other attribute to the output and
add DT_AARCH64_VARIANT_PCS dynamic tag if necessary.
Mismatching attributes are not diagnosed.
bfd/ChangeLog:
* elfnn-aarch64.c (elfNN_aarch64_merge_symbol_attribute): New function.
(struct elf_aarch64_link_hash_table): Add variant_pcs member.
(elfNN_aarch64_allocate_dynrelocs): Update variant_pcs.
(elfNN_aarch64_size_dynamic_sections): Add DT_AARCH64_VARIANT_PCS.
(elf_backend_merge_symbol_attribute): Define.
ld/ChangeLog:
* testsuite/ld-aarch64/aarch64-elf.exp: Add new tests.
* testsuite/ld-aarch64/variant_pcs-1.s: New asm for tests.
* testsuite/ld-aarch64/variant_pcs-2.s: New asm for tests.
* testsuite/ld-aarch64/variant_pcs-now.d: New test.
* testsuite/ld-aarch64/variant_pcs-r.d: New test.
* testsuite/ld-aarch64/variant_pcs-shared.d: New test.
* testsuite/ld-aarch64/variant_pcs.ld: New linker script for tests.
ld/ChangeLog:
* testsuite/ld-aarch64/variant_pcs-now.d: Use --hash-style=sysv.
* testsuite/ld-aarch64/variant_pcs-shared.d: Likewise.
Szabolcs Nagy [Thu, 25 Apr 2019 14:07:10 +0000 (15:07 +0100)]
aarch64: override default elf .set handling in gas
Backport commit
0b4eac57c44ec4c9e13f5201b40936c3b3e6c639
Allow st_other values such as STO_AARCH64_VARIANT_PCS to be set for alias
symbols independently. This is needed for ifunc symbols which are
aliased to the resolver using .set and don't expect resolver attributes
to override the ifunc symbol attributes. This means .variant_pcs must be
added explicitly to aliases.
gas/ChangeLog:
* config/tc-aarch64.c (aarch64_elf_copy_symbol_attributes): Define.
* config/tc-aarch64.h (aarch64_elf_copy_symbol_attributes): Declare.
(OBJ_COPY_SYMBOL_ATTRIBUTES): Define.
* testsuite/gas/aarch64/symbol-variant_pcs-3.d: New test.
* testsuite/gas/aarch64/symbol-variant_pcs-3.s: New test.
Szabolcs Nagy [Thu, 25 Apr 2019 14:06:53 +0000 (15:06 +0100)]
aarch64: handle .variant_pcs directive in gas
Backport commit
f166ae0188dcb89c5ae925034260a708a254ab2f
In ELF objects the specified symbol is marked with STO_AARCH64_VARIANT_PCS.
gas/ChangeLog:
* config/tc-aarch64.c (s_variant_pcs): New function.
* doc/c-aarch64.texi: Document .variant_pcs.
* testsuite/gas/aarch64/symbol-variant_pcs-1.d: New test.
* testsuite/gas/aarch64/symbol-variant_pcs-1.s: New test.
* testsuite/gas/aarch64/symbol-variant_pcs-2.d: New test.
* testsuite/gas/aarch64/symbol-variant_pcs-2.s: New test.
Szabolcs Nagy [Thu, 25 Apr 2019 12:46:01 +0000 (13:46 +0100)]
aarch64: add STO_AARCH64_VARIANT_PCS and DT_AARCH64_VARIANT_PCS
Backport commit
2301ed1c9af1316b4bad3747d2b03f7d44940f87
The bottom 2 bits of st_other are used for visibility, the top 6 bits are
de facto reserved for processor specific use. This patch defines a
bits to mark function symbols that follow a variant procedure call standard
with different register usage convention.
A dynamic tag is also defined that marks modules with R_<CLS>_JUMP_SLOT
relocations referencing symbols marked with STO_AARCH64_VARIANT_PCS.
This can be used by dynamic linkers that support lazy binding to decide
what registers need to be preserved during symbol resolution.
binutils/ChangeLog:
* readelf.c (get_aarch64_dynamic_type): Handle DT_AARCH64_VARIANT_PCS.
(get_aarch64_symbol_other): New, handles STO_AARCH64_VARIANT_PCS.
(get_symbol_other): Call get_aarch64_symbol_other.
include/ChangeLog:
* elf/aarch64.h (DT_AARCH64_VARIANT_PCS): Define.
(STO_AARCH64_VARIANT_PCS): Define.
GDB Administrator [Fri, 5 Jul 2019 00:01:25 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 4 Jul 2019 00:01:19 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 3 Jul 2019 00:01:30 +0000 (00:01 +0000)]
Automatic date update in version.in
Srinath Parvathaneni [Tue, 2 Jul 2019 13:48:40 +0000 (14:48 +0100)]
Ensure that debug information for ARM security functions is not dropped by the linker when performing garbage collection.
onsider a file containing only Armv8-M secure entry functions.
This file is compiled and linked with "-march=armv8-m.main -mfloat-abi=hard
-mfpu=fpv5-sp-d16 -mcmse -static --specs=rdimon.specs
-Wl,--section-start,.gnu.sgstubs=0x190000 -ffunction-sections
-fdata-sections
-Wl,--gc-sections -g" options to generate an executable.
The executable generated does not contain any debug information of these
secure entry
functions even though it contains secure entry functions in the .text
section.
Example:
$ cat main.c
int main (void)
{
return 0;
}
$ cat sec.c
void __attribute__((cmse_nonsecure_entry))
SecureLED_On ()
{
}
Generate the object files "main.o" and "sec.o" for above test, using
below command.
1. $ arm-none-eabi-gcc -march=armv8-m.main -mfloat-abi=hard
-mfpu=fpv5-sp-d16 -mcmse
-static --specs=rdimon.specs -ffunction-sections -fdata-sections main.c
sec.c -g -c
Using linker, generate the executable for above generated object files.
2.$ arm-none-eabi-ld --section-start .gnu.sgstubs=0x190000 --gc-sections
main.o sec.o -e0 -o main_sec.out
Check for "SecureLED_On" in dwarf information generated for executable
"main_sec.out".
3. $ arm-none-eabi-objdump --dwarf=info main_sec.out |grep "SecureLED_On"
There is no match for the function "SecureLED_On" in .dwarf_info.
After applying this patch and performing above steps 2 and 3, the output is:
<8f> DW_AT_name : (indirect string, offset: 0x9d):
SecureLED_On
This patch fixes the linker by marking all the debug sections (setting
gc_mark to 1)
when .text section containing secure entry functions is marked.
bfd * elf32-arm.c (elf32_arm_gc_mark_extra_sections): Mark debug
sections when .text section contain secure entry functions
is marked.
ld * testsuite/ld-arm/arm-elf.exp: Add tests.
* testsuite/ld-arm/cmse_main.s: New test.
* testsuite/ld-arm/cmse_main_sec_debug.d: Likewise.
* testsuite/ld-arm/cmse_sec_debug.s: Likewise.
Richard Sandiford [Tue, 2 Jul 2019 10:03:31 +0000 (11:03 +0100)]
[AArch64] Allow MOVPRFX to be used with FMOV
The entry for the FMOV alias of FCPY was missing C_SCAN_MOVPRFX.
(The entry for FCPY itself was OK.)
This was the only /m-predicated instruction I could see that was
missing the flag.
2019-07-02 Richard Sandiford <richard.sandiford@arm.com>
opcodes/
* aarch64-tbl.h (aarch64_opcode): Set C_SCAN_MOVPRFX for the
SVE FMOV alias of FCPY.
gas/
* testsuite/gas/aarch64/sve-movprfx_27.s,
* testsuite/gas/aarch64/sve-movprfx_27.d: New test.
Richard Sandiford [Tue, 2 Jul 2019 10:03:27 +0000 (11:03 +0100)]
[AArch64] Add missing C_MAX_ELEM flags for SVE conversions
SVE FCVTZS, FCVTZU, SCVTF and UCVTF need the same treatment as FCVT:
the register size used in a predicated MOVPRFX must be the wider of
the destination and source sizes.
Since I was adding a (supposedly) complete set of tests for converts,
it seemed more consistent to add a complete set of tests for shifts
as well, even though there's no bug to fix there.
2019-07-02 Richard Sandiford <richard.sandiford@arm.com>
opcodes/
* aarch64-tbl.h (aarch64_opcode_table): Add C_MAX_ELEM flags
to SVE fcvtzs, fcvtzu, scvtf and ucvtf entries.
gas/
* testsuite/gas/aarch64/sve-movprfx_26.s: Also test FCVTZS, FCVTZU,
SCVTF, UCVTF, LSR and ASR.
* testsuite/gas/aarch64/sve-movprfx_26.d: Update accordingly.
* testsuite/gas/aarch64/sve-movprfx_26.l: Likewise.
Richard Sandiford [Tue, 2 Jul 2019 10:03:22 +0000 (11:03 +0100)]
[AArch64] Fix bogus MOVPRFX warning for GPR form of CPY
One of the MOVPRFX tests has:
output register of preceding `movprfx' used as input at operand 3 -- `cpy z1.d,p1/m,x1'
But X1 and Z1 are not the same register, so the instruction is
actually OK.
2019-07-02 Richard Sandiford <richard.sandiford@arm.com>
opcodes/
* aarch64-opc.c (verify_constraints): Skip GPRs when scanning the
registers in an instruction prefixed by MOVPRFX.
gas/
* testsuite/gas/aarch64/sve-movprfx_25.s: Allow CPY Z1.D.P1/M,X1
to be prefixed by MOVPRFX.
* testsuite/gas/aarch64/sve-movprfx_25.d: Update accordingly.
* testsuite/gas/aarch64/sve-movprfx_25.l: Likewise.
GDB Administrator [Tue, 2 Jul 2019 00:02:17 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 1 Jul 2019 00:02:24 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 30 Jun 2019 00:02:00 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 29 Jun 2019 00:01:24 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 28 Jun 2019 00:02:20 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 27 Jun 2019 00:01:22 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 26 Jun 2019 00:01:25 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 25 Jun 2019 00:01:30 +0000 (00:01 +0000)]
Automatic date update in version.in
H.J. Lu [Mon, 24 Jun 2019 18:08:40 +0000 (11:08 -0700)]
elf: Remove the property after reporting its removal
commit
d2ef37ebd9f771d06edf1fdea37970f60b242b2d
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Fri Dec 7 08:30:30 2018 -0800
elf: Report property change when merging properties
failed to remove the property after reporting it has been removed. This
patch corrects it.
bfd/
PR ld/24721
* elf-properties.c (elf_merge_gnu_property_list): Remove the
property after reporting property removal.
ld/
PR ld/24721
* testsuite/ld-x86-64/x86-64.exp: Run PR ld/24721 tests.
* testsuite/ld-x86-64/pr24721-x32.d: New file.
* testsuite/ld-x86-64/pr24721.d: Likewise.
* testsuite/ld-x86-64/pr24721.map: Likewise.
* testsuite/ld-x86-64/pr24721a.s: Likewise.
* testsuite/ld-x86-64/pr24721b.s: Likewise.
(cherry picked from commit
f93ab3a0b8039a1667a666f013cca50b03d67f9b )
GDB Administrator [Mon, 24 Jun 2019 00:01:28 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 23 Jun 2019 00:01:49 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 22 Jun 2019 00:01:19 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 21 Jun 2019 00:01:29 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 20 Jun 2019 00:01:19 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 19 Jun 2019 00:01:46 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 18 Jun 2019 00:01:30 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 17 Jun 2019 00:01:24 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 16 Jun 2019 00:02:01 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 15 Jun 2019 00:01:28 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 14 Jun 2019 00:01:16 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 13 Jun 2019 00:01:53 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 12 Jun 2019 00:01:16 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 11 Jun 2019 00:01:09 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 10 Jun 2019 00:01:14 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 9 Jun 2019 00:01:55 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 8 Jun 2019 00:02:16 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 7 Jun 2019 00:01:11 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 6 Jun 2019 00:01:14 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 5 Jun 2019 00:01:17 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 4 Jun 2019 00:01:10 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 3 Jun 2019 00:02:01 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 2 Jun 2019 00:01:54 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 1 Jun 2019 00:01:17 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 31 May 2019 00:01:23 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 30 May 2019 00:01:15 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 29 May 2019 00:01:20 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 28 May 2019 00:01:10 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 27 May 2019 00:01:13 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 26 May 2019 00:01:51 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 25 May 2019 00:01:20 +0000 (00:01 +0000)]
Automatic date update in version.in