From: Andrew Guirguis <andrew.sadek.se@gmail.com>
To: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
eager@eagercon.com, nmekala@xilinx.com
Subject: [PATCH] [Microblaze]: PIC Data Text Relative
Date: Mon, 26 Feb 2018 07:56:00 -0000 [thread overview]
Message-ID: <CAE=jbAN0CJ65C-_7O4PcDcXJ76HBGEOD1S1=Tit_4fDtU=fcmQ@mail.gmail.com> (raw)
Dears,
Kindly find the patch bundle for Microblaze '-mpic-data-text-relative'
feature at the following link:
https://github.com/andrewsadek/microblaze-pic-data-text-rel/tree/pic_data_text_rel/PATCH%20BUNDLE
Description of the feature:
https://github.com/andrewsadek/microblaze-pic-data-text-rel/
blob/pic_data_text_rel/README.md
Bundle includes:
1) Change logs for GCC, binutils
2) GCC Test results and comparison with the original.
3) New Test case (picdtr.c)
4) The Patches (against current heads)
Thanks
--
Andrew
next reply other threads:[~2018-02-26 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 7:56 Andrew Guirguis [this message]
2018-02-26 8:36 ` Andrew Sadek
[not found] <CAE=jbAMyXXpWUPnC_dcmyWNeOXcJ-Wo4+KomQ9KwpX2KuLDqkg@mail.gmail.com>
2018-02-27 0:07 ` Michael Eager
2018-02-27 8:14 ` Andrew Sadek
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='CAE=jbAN0CJ65C-_7O4PcDcXJ76HBGEOD1S1=Tit_4fDtU=fcmQ@mail.gmail.com' \
--to=andrew.sadek.se@gmail.com \
--cc=eager@eagercon.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nmekala@xilinx.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