From: Aditya Kamath1 <Aditya.Kamath1@ibm.com>
To: Tom Tromey <tom@tromey.com>, Tom de Vries <tdevries@suse.de>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Cc: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Aditya Kamath1 via Gdb-patches <gdb-patches@sourceware.org>,
Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>,
Tom Tromey <tom@tromey.com>
Subject: RE: [PATCH] Fix AIX build break
Date: Tue, 16 Jan 2024 09:42:42 +0000 [thread overview]
Message-ID: <CH2PR15MB3544F7D7F067000679FB53A9D6732@CH2PR15MB3544.namprd15.prod.outlook.com> (raw)
In-Reply-To: <874jfipmu4.fsf@tromey.com>
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
Respected community members,
Hi,
Please find attached the patch. (See: 0001-Fix-AIX-build-break.patch).
Thank you for your patience and feedback.
This patch now fixes the AIX build break and uses the idea as suggested by Tom in this link (https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=fece451c2aca57b095e7e4063e342781cf74aa75).
Kindly give me feedback for the same. I removed the extern thread_local and use class now.
Also, is there any guidelines for naming classes? Kindly let me know.
I am also curious to know if GDB is multi-threaded now?
Have a nice day ahead.
Thanks and regards,
Aditya.
From: Tom Tromey <tom@tromey.com>
Date: Friday, 12 January 2024 at 9:26 PM
To: Tom de Vries <tdevries@suse.de>
Cc: Aditya Kamath1 <Aditya.Kamath1@ibm.com>, Ulrich Weigand <Ulrich.Weigand@de.ibm.com>, Aditya Kamath1 via Gdb-patches <gdb-patches@sourceware.org>, Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>, Tom Tromey <tom@tromey.com>
Subject: [EXTERNAL] Re: [PATCH] Fix AIX build break
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> I think this is triggered by using thread-local with extern.
Ugh.
> Use RAII to set the per-thread SIGSEGV handler
Tom> which seems related, given that it mentions link errors. Perhaps we
Tom> can do something similar here.
That would by fine with me.
Does the AIX build detect that threads work? If not then we could
perhaps make the use of 'thread_local' dependent on CXX_STD_THREAD.
Tom
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 24153 bytes --]
next prev parent reply other threads:[~2024-01-16 9:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 9:20 Aditya Kamath1
2024-01-12 9:50 ` Tom de Vries
2024-01-12 15:56 ` Tom Tromey
2024-01-15 9:57 ` [RFC] " Aditya Kamath1
2024-01-16 9:42 ` Aditya Kamath1 [this message]
2024-01-17 15:09 ` [PATCH] " Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2024-01-17 18:28 Aditya Vidyadhar Kamath
2024-01-17 19:25 ` Tom Tromey
2024-01-19 11:58 ` Aditya Kamath1
2024-01-19 16:25 ` Tom Tromey
2024-01-20 15:03 ` Aditya Kamath1
2024-01-24 0:53 ` Aditya Kamath1
2024-01-25 14:45 ` Aditya Kamath1
2024-01-25 19:53 ` Tom Tromey
2024-01-26 8:37 ` Aditya Kamath1
2024-01-31 0:40 ` Tom Tromey
2024-01-31 9:15 ` Aditya Kamath1
2024-02-01 0:37 ` Tom Tromey
2024-02-01 3:03 ` Aditya Kamath1
2024-02-06 12:36 ` Ciaran Woodward
2024-02-06 14:49 ` Tom Tromey
2024-02-06 15:04 ` Ciaran Woodward
2024-02-06 15:54 ` Aditya Kamath1
2023-08-11 8:49 Aditya Kamath1
2023-08-11 9:43 ` Ulrich Weigand
2023-08-11 9:53 ` Aditya Kamath1
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=CH2PR15MB3544F7D7F067000679FB53A9D6732@CH2PR15MB3544.namprd15.prod.outlook.com \
--to=aditya.kamath1@ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.com \
--cc=tdevries@suse.de \
--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).