Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Abhay Kandpal <abhay@linux.ibm.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Abhay Kandpal <Abhay.k@ibm.com>, "cel@linux.ibm.com" <cel@linux.ibm.com>
Subject: Re: [PATCH v1] PowerPC: Use -mcmodel=large for the compile command
Date: Tue, 28 Jul 2026 23:19:48 +0530	[thread overview]
Message-ID: <29fb3c0e-4724-40ef-935e-7dc2cff314e9@linux.ibm.com> (raw)
In-Reply-To: <a4c047345ee2da6ff3977dd713c3d67b86d5606d.camel@de.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

Thanks Ulrich — v2 fully reverts 533f04079c7 as you suggested, so ppc64 
uses default_gcc_target_options. BR, Abhay

On 28/07/26 15:54, Ulrich Weigand wrote:
> Abhay Kandpal<abhay@linux.ibm.com> wrote:
>
>> The cause is the code model used to compile the injected object.
>> Commit 533f04079c7 ("[gdb] [rs6000] Add
>> ppc64_linux_gcc_target_options method.") made ppc64 return an empty
>> string from gdbarch_gcc_target_options, overriding the
>> "-mcmodel=large" that default_gcc_target_options supplies for 64-bit
>> targets, so GCC falls back to -mcmodel=medium.
> I can see why large model is more appropriate for this type
> of compilation.  However, your patch just reverts the effect
> of the above commit, without actually reverting it.  (This
> causes ppc64_linux_gcc_target_options to pretty much duplicate
> default_gcc_target_options.)  I think it would be preferable
> to fully revert the commit instead.
>
> Bye,
> Ulrich

[-- Attachment #2: Type: text/html, Size: 1540 bytes --]

      reply	other threads:[~2026-07-28 17:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  6:49 Abhay Kandpal
2026-07-28 10:24 ` Ulrich Weigand
2026-07-28 17:49   ` Abhay Kandpal [this message]

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=29fb3c0e-4724-40ef-935e-7dc2cff314e9@linux.ibm.com \
    --to=abhay@linux.ibm.com \
    --cc=Abhay.k@ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=cel@linux.ibm.com \
    --cc=gdb-patches@sourceware.org \
    /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