From: Iain Sandoe <iain@sandoe.co.uk>
To: "Gade, Naresh (Coral Springs)" <naresh.gade@Fiserv.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC V10.3 compiler issue.
Date: Fri, 23 Sep 2022 08:39:14 +0100 [thread overview]
Message-ID: <29A0282C-3E2A-48DC-81EE-F0B981A5DD4E@sandoe.co.uk> (raw)
In-Reply-To: <MW5PR10MB585199A1111EC88D94EA1D3C82519@MW5PR10MB5851.namprd10.prod.outlook.com>
Hello Naresh,
> On 23 Sep 2022, at 01:40, Gade, Naresh (Coral Springs) <naresh.gade@Fiserv.com> wrote:
>
> We have downloaded GCC V10.3 compiler on our AIX server but we noticed a weird thing about the size of object files for certain source files.
>
> When tried to dump the object file, we noticed the DATA segment in the file is a large chunk of NULLS and it is eating lot of memory space.
GCC is a large project, with different folks handling different parts of the compiler; I am not the right person to answer an AIX question (although I can say that what you report might not necessarily be unexpected depending on the code you were compiling).
====
1. If you are looking for help in using GCC the right place to post a question is here:
gcc-help@gcc.gnu.org (I’ve already CC’d in this reply).
2. If you think that there is a bug in GCC then please follow the guidelines here:
https://gcc.gnu.org/bugs/
Your message above does not have enough information for a developer to figure out if it represents a genuine issue.
HTH,
Iain
>
> Regards,
> Naresh Gade
> NFE Debit gateway development
next parent reply other threads:[~2022-09-23 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MW5PR10MB585199A1111EC88D94EA1D3C82519@MW5PR10MB5851.namprd10.prod.outlook.com>
2022-09-23 7:39 ` Iain Sandoe [this message]
2022-09-23 8:02 ` David Edelsohn
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=29A0282C-3E2A-48DC-81EE-F0B981A5DD4E@sandoe.co.uk \
--to=iain@sandoe.co.uk \
--cc=gcc-help@gcc.gnu.org \
--cc=naresh.gade@Fiserv.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).