| Summary: | Regression on testsuite due to changes to default_target_compile | ||
|---|---|---|---|
| Product: | gdb | Reporter: | Luis Machado <luis.machado> |
| Component: | testsuite | Assignee: | Not yet assigned to anyone <unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | fche, vries |
| Priority: | P1 | ||
| Version: | 10.1 | ||
| Target Milestone: | 10.1 | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
|
Description
Luis Machado
2020-06-26 11:33:52 UTC
Patch submitted: https://sourceware.org/pipermail/gdb-patches/2020-June/169959.html The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b011fe1a7242f242699f9e74798e5ffbc7973c6e commit b011fe1a7242f242699f9e74798e5ffbc7973c6e Author: Tom de Vries <tdevries@suse.de> Date: Tue Jun 30 09:23:09 2020 +0200 [gdb/testsuite] Handle early_flags in gdb_default_target_compile In gdb_default_target_compile, we use dejagnu's default_target_compile, unless we need support for languages that are not yet support in the used dejagnu version, in which case we use a local default_target_compile: gdb_default_target_compile_1. However, there's another reason to use the local default_target_compile: when early_flags is used, because there's no dejagnu release available yet supporting this. Fix this by detecting and handling early_flags in gdb_default_target_compile. Tested on x86_64-linux. gdb/testsuite/ChangeLog: 2020-06-30 Tom de Vries <tdevries@suse.de> PR testsuite/26175 * lib/future.exp (gdb_default_target_compile): Detect and handle early_flags. Patch fixing testsuite committed, marking resolved-fixed. test |