public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: dwz@sourceware.org, mark@klomp.org
Subject: Re: [committed] Make main more readable
Date: Wed, 17 Mar 2021 14:37:57 +0100	[thread overview]
Message-ID: <a3c41263-1c47-5b28-33a1-6281b2ac75db@suse.de> (raw)
In-Reply-To: <20210317131802.GG231854@tucnak>

On 3/17/21 2:18 PM, Jakub Jelinek wrote:
> On Wed, Mar 17, 2021 at 02:14:45PM +0100, Tom de Vries wrote:
>> @@ -17048,10 +17050,12 @@ main (int argc, char *argv[])
>>    outfile = NULL;
>>    hardlink = false;
>>    parse_args (argc, argv, &hardlink, &outfile);
>> +  nr_files = argc - optind;
>> +  files = (const char **)&argv[optind];
>>  
>> -  if (optind == argc || optind + 1 == argc)
>> +  if (nr_files <= 1)
>>      {
>> -      const char *file = optind == argc ? "a.out" : argv[optind];
>> +      const char *file = nr_files == 0 ? "a.out" : files[0];
> 
> Isn't that aliasing violation?

Sorry, I don't see it, can you be specific about which entity is
accessed with an incompatible type?

FWIW, I've compiled with:
...
$ make clean; make CC="gcc -Wall -fstrict-aliasing
-Wstrict-aliasing={1,2,3}"
...
and nothing in main was flagged.

OTOH, we do have things like:
...
dwz.c: In function ‘die_cu’:
dwz.c:1195:3: warning: dereferencing type-punned pointer might break
strict-aliasing rules [-Wstrict-aliasing]
   return (dw_cu_ref) die->die_parent;
   ^~~~~~
...

Thanks,
- Tom

  reply	other threads:[~2021-03-17 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 13:14 Tom de Vries
2021-03-17 13:18 ` Jakub Jelinek
2021-03-17 13:37   ` Tom de Vries [this message]
2021-03-17 17:28     ` Jakub Jelinek
2021-03-18 10:30       ` Tom de Vries
2021-03-18 18:52         ` Florian Weimer
2021-03-19 16:43           ` [committed] Change files var in main to char ** Tom de Vries

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=a3c41263-1c47-5b28-33a1-6281b2ac75db@suse.de \
    --to=tdevries@suse.de \
    --cc=dwz@sourceware.org \
    --cc=jakub@redhat.com \
    --cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).