Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Svante Signell <svante.signell@gmail.com>
Cc: Simon Marchi <simark@simark.ca>,  Tom Tromey <tom@tromey.com>,
	 gdb-patches@sourceware.org
Subject: Re: [PATCH] Please define thread_info as struct thread_info (and other stuff)
Date: Sun, 16 Dec 2018 16:22:00 -0000	[thread overview]
Message-ID: <8736qx5tmh.fsf@tromey.com> (raw)
In-Reply-To: <07b12fd403ec2442d90ec3f73bb9a0b99a8899e3.camel@gmail.com>	(Svante Signell's message of "Sun, 16 Dec 2018 06:15:00 +0100")

>>>>> "Svante" == Svante Signell <svante.signell@gmail.com> writes:

Svante> /home/srs/DEBs/gdb/gdb-8.2/gdb/regcache.h:35:46: warning: ‘get_thread_regcache’
Svante> initialized and declared ‘extern’

Ok, I was able to reproduce this error with:

    int Foo;

    struct Foo
    {
      int a;
    };

    extern int f(Foo x);

I didn't see a definition of thread_info anywhere, but maybe somehow it
comes from one of your system headers.  You could compile with 'gcc -E'
and search for it.

clang will tell you where the conflicting definition appears; I've filed
a gcc bug about this: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88520

Tom


  parent reply	other threads:[~2018-12-16 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 19:36 Svante Signell
2018-12-15 22:48 ` Tom Tromey
2018-12-15 23:01   ` Svante Signell
2018-12-16  4:31     ` Simon Marchi
2018-12-16  5:14       ` Svante Signell
2018-12-16  6:02         ` Simon Marchi
2018-12-16 16:22         ` Tom Tromey [this message]
2018-12-16  9:20 ` Andreas Schwab
2018-12-16 19:08   ` Svante Signell
2018-12-16 23:10     ` Tom Tromey
2018-12-17 20:51       ` Svante Signell
2018-12-17 21:41         ` John Baldwin
2019-02-14 15:16           ` Thomas Schwinge
2018-12-20 13:31         ` Svante Signell
2018-12-20 22:34           ` Tom Tromey
2018-12-20 23:26             ` Simon Marchi
2018-12-24 21:51             ` Tom Tromey
2019-01-12 18:37               ` Svante Signell
2019-01-12 20:50                 ` Tom Tromey

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=8736qx5tmh.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=svante.signell@gmail.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