From: wbx@uclibc-ng.org (Waldemar Brodkorb)
To: linux-snps-arc@lists.infradead.org
Subject: [uclibc-ng-devel] [PATCH] Same iteration variable used for inner and outer loop
Date: Tue, 11 Apr 2017 22:11:46 +0200 [thread overview]
Message-ID: <20170411201146.GC5361@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170406095725.18604-1-cmiranda@synopsys.com>
Hi Cupertino,
Cupertino Miranda wrote,
> Inner loop was using same counter variable (i) as the outer loop, therefore
> making outer loop terminate before it visited all of the ELF program segments.
> Surrounding code in this inner loop clearly shows the intention that this loop
> should not affect the outer one, therefore leading me to the conclusion that
> this should be a bug an not expected code.
>
> This bug was detected due to some other bug in ARC binutils that kept setting
> TEXTREL for any PIE application.
>
> Apart from the but, I have also moved the debug message inside of the TEXTREL
> condition as mprotect is only really called if TELTREL is set.
Thanks.
Applied and pushed,
Waldemar
prev parent reply other threads:[~2017-04-11 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 9:57 [PATCH] Same iteration variable used for inner and outer loop Cupertino Miranda
2017-04-11 20:11 ` Waldemar Brodkorb [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=20170411201146.GC5361@waldemar-brodkorb.de \
--to=wbx@uclibc-ng.org \
--cc=linux-snps-arc@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.