From: "Willgerodt, Felix via Gdb-patches" <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Tom Tromey <tom@tromey.com>,
"Felix Willgerodt via Gdb-patches" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 1/2] gdb: Allow address space qualifier parsing in C++.
Date: Tue, 6 Apr 2021 09:30:44 +0000 [thread overview]
Message-ID: <991f5587b5e3454697b10b85723c3bf1@intel.com> (raw)
In-Reply-To: <f957abd6-f83e-369d-7337-c6a4f4c9f5e1@polymtl.ca>
>-----Original Message-----
>From: Simon Marchi <simon.marchi@polymtl.ca>
>Sent: Freitag, 2. April 2021 18:49
>
>Hi Felix,
>
>I think it would be valuable to have a test like this. It's better than nothing, and it's always good to check error cases to make sure
>GDB doesn't crash on them. I can imagine that this test could test with both a C and C++ program to cover everything correctly (and
>maybe other languages, but I don't know much about them, if that even applies to them).
>
>A while ago I added a simavr board file, to be able to run tests against an AVR target. simavr is easy to build and use (it may even be
>packaged in distros, but I'd be tempted to use the latest available version).
>All of this to say you could try to run and improve the flash qualifier test for AVR (or write a new test).
>
>There's just one thing, avr-gcc/avr-g++ seem to produce stabs by default, it's not really useful to test with stabs nowadays. I had a
>patch to make that board use dwarf by default (see below), but I never got around to try it properly and post it. I'll try to do it soon
> (but you can apply it locally in the mean time).
>
>Simon
I think we are mixing my two patches a bit here, which is of course understandable as they are somewhat related.
However, avr-g++ didn't compile a program using __flash when I tried:
"error: '__flash' does not name a type"
I assume that support is only implemented in avr-gcc and I therefore can't even write an avr test for patch 1.
I opted for writing a general C and C++ test for patch 1, that has the advantage that every normal testsuite run has the chance to catch regressions.
Thanks for all the comments, I will push v2 in a couple of minutes.
Felix
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2021-04-06 9:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 14:26 [PATCH 0/2] Expression parser fixes for address space qualifiers Felix Willgerodt via Gdb-patches
2021-03-26 14:26 ` [PATCH 1/2] gdb: Allow address space qualifier parsing in C++ Felix Willgerodt via Gdb-patches
2021-04-01 18:16 ` Tom Tromey
2021-04-02 12:33 ` Willgerodt, Felix via Gdb-patches
2021-04-02 12:47 ` Luis Machado via Gdb-patches
2021-04-02 16:48 ` Simon Marchi via Gdb-patches
2021-04-02 16:51 ` Simon Marchi via Gdb-patches
2021-04-05 2:32 ` Simon Marchi via Gdb-patches
2021-04-06 9:30 ` Willgerodt, Felix via Gdb-patches [this message]
2021-03-26 14:26 ` [PATCH 2/2] gdb: Fix reduce/reduce conflicts for qualifier_seq_noopt in the C parser Felix Willgerodt via Gdb-patches
2021-04-01 18:20 ` Tom Tromey
2021-04-02 12:33 ` Willgerodt, Felix via Gdb-patches
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=991f5587b5e3454697b10b85723c3bf1@intel.com \
--to=gdb-patches@sourceware.org \
--cc=felix.willgerodt@intel.com \
--cc=simon.marchi@polymtl.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