From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Abdul Basit Ijaz <abdul.b.ijaz@intel.com>
Cc: simark@simark.ca, tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 1/4] gdb, testsuite: handle icc and icpc deprecated remarks
Date: Mon, 02 Oct 2023 21:04:25 -0300 [thread overview]
Message-ID: <87leckefli.fsf@linaro.org> (raw)
In-Reply-To: <20230904222956.15203-2-abdul.b.ijaz@intel.com>
Hello,
Abdul Basit Ijaz via Gdb-patches <gdb-patches@sourceware.org> writes:
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index 1b9179401c4..def6a75dfee 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -4980,13 +4980,15 @@ proc gdb_compile {source dest type options} {
> }
> }
>
> - # Starting with 2021.7.0 (recognized as icc-20-21-7 by GDB) icc and
> - # icpc are marked as deprecated and both compilers emit the remark
> - # #10441. To let GDB still compile successfully, we disable these
> - # warnings here.
> + # Starting with 2021.7.0 (recognized as icc-20-21-7 by
> + # GDB) icc and icpc are marked as deprecated and both
> + # compilers emit the remark #10441. To let GDB still
> + # compile successfully, we disable these warnings here.
I don't see any change in this comment except for the reformatting.
IMO, the text is more readable at the larger width and considering that
it's already less than 80 columns, I suggest dropping this part of the
change.
> if {([lsearch -exact $options c++] != -1
> - && [test_compiler_info {icc-20-21-[7-9]} c++])
> - || [test_compiler_info {icc-20-21-[7-9]}]} {
> + && [test_compiler_info {icc-20-21-[7-9]} c++]
> + && [test_compiler_info {icc-20-21-[1-9][0-9]} c++])
Unless I'm missing something, the above should be:
([lsearch …] != -1
&& ([test_compiler_info <pattern 1> c++]
|| [test_compiler_info <pattern 2> c++])
> + || [test_compiler_info {icc-20-21-[7-9]}]
> + || [test_compiler_info {icc-20-21-[1-9][0-9]}]} {
> lappend new_options "additional_flags=-diag-disable=10441"
> }
> }
--
Thiago
next prev parent reply other threads:[~2023-10-03 0:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 22:29 [PATCH v3 0/4] Dynamic properties of pointers Abdul Basit Ijaz
2023-09-04 22:29 ` [PATCH v3 1/4] gdb, testsuite: handle icc and icpc deprecated remarks Abdul Basit Ijaz
2023-10-03 0:04 ` Thiago Jung Bauermann [this message]
2023-09-04 22:29 ` [PATCH v3 2/4] gdb, types: Resolve pointer types dynamically Abdul Basit Ijaz
2023-10-03 0:07 ` Thiago Jung Bauermann
2023-10-10 19:45 ` Tom Tromey
2024-01-03 21:06 ` Ijaz, Abdul B
2024-01-03 21:06 ` Ijaz, Abdul B
2023-10-10 19:49 ` Tom Tromey
2024-01-03 21:31 ` Ijaz, Abdul B
2023-09-04 22:29 ` [PATCH v3 3/4] gdb, intel-classic-compilers, testsuite: workaround icc/icpc/ifort pointer/reference DWARF Abdul Basit Ijaz
2023-10-03 0:09 ` Thiago Jung Bauermann
2023-10-10 19:52 ` Tom Tromey
2024-01-03 21:15 ` Ijaz, Abdul B
2023-09-04 22:29 ` [PATCH v3 4/4] gdb, testsuite, fortran: Fix sizeof intrinsic for ifort Fortran pointers Abdul Basit Ijaz
2023-10-03 0:16 ` Thiago Jung Bauermann
2023-09-27 21:11 ` [PING][PATCH v3 0/4] Dynamic properties of pointers Ijaz, Abdul B
2023-10-03 0:17 ` [PATCH " Thiago Jung Bauermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87leckefli.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=abdul.b.ijaz@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).