From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 311a78: gcc: Sync backend functions
Date: Wed, 06 Jan 2016 19:11:00 -0000 [thread overview]
Message-ID: <568d646b5cf72_584b3fe13f15b2a07112c@hookshot-fe1-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 311a78d6e108f493e5df08eb99dffc7ba59bd8ce
https://github.com/crosstool-ng/crosstool-ng/commit/311a78d6e108f493e5df08eb99dffc7ba59bd8ce
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-01-06 (Wed, 06 Jan 2016)
Changed paths:
M scripts/build/cc/100-gcc.sh
Log Message:
-----------
gcc: Sync backend functions
The two gcc backend functions are getting very close to being duplicated
code. To help in the process of merging the two backends, this change
syncronizes the two functions so they are easier to diff.
This commit has no functional changes.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Commit: 31c6ebab07ef4c3e4a35be87f1630ec8e1d3c4ae
https://github.com/crosstool-ng/crosstool-ng/commit/31c6ebab07ef4c3e4a35be87f1630ec8e1d3c4ae
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-01-06 (Wed, 06 Jan 2016)
Changed paths:
M scripts/build/cc/100-gcc.sh
Log Message:
-----------
Merge pull request #312 from bhundven/sync_gcc_backends
gcc: Sync backend functions
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/50248e37e85e...31c6ebab07ef
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-01-06 19:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=568d646b5cf72_584b3fe13f15b2a07112c@hookshot-fe1-cp1-prd.iad.github.net.mail \
--to=bryanhundven@gmail.com \
--cc=crossgcc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).