public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Santos <daniel.santos@pobox.com>
To: JonY <10walls@gmail.com>, Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] [PATCH v3 0/8] [i386] Use out-of-line stubs for ms_abi pro/epilogues
Date: Fri, 10 Mar 2017 04:42:00 -0000	[thread overview]
Message-ID: <c09a2060-9c15-a0ec-6ec9-64617be5bb42@pobox.com> (raw)
In-Reply-To: <e2d2f918-fcc4-be1d-7fa2-c589af2f157c@gmail.com>

It's been a while and I wanted to post a status update.  My new tests 
needed a few fix-ups to work on Cygwin, but they pass.

As for the rest, it turns out that running the testsuite on Cygwin is a 
vertable nightmare.  The tests are NOT even correct because they load 
the shared libs (dlls) that are installed on the *system* and NOT the 
ones in the build tree! (libgcc, libgfortran, libatomic, etc.)  I have 
opened a report for this 
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79867) and I have a 
patchset that appears to resolve the the problem, although it needs much 
cleaning up and half of it is on the DejaGnu side.  This problem appears 
to have been around for a long time.

Although my VM is on an quad core w/ hyperthreading processor (so 8 
cores), if I run more than one make job I get broken pipes.  This 
appears to be one of those problems that nobody has a solution to, only 
tweaks that they *believe* prevents the problem from occurring *as 
often*!  If I run a single make job with -j1, I am very likely to not 
get the problem, but never assured.  There are also many jobs that are 
timing out, but I'm hoping to get a descent set of tests on this latest run.

Daniel

  parent reply	other threads:[~2017-03-10  4:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 18:34 Daniel Santos
2017-02-07 18:36 ` [PATCH 2/8] [i386] Add option -moutline-msabi-xlogues Daniel Santos
2017-02-08 23:28   ` Bernhard Reutner-Fischer
2017-02-10  4:43     ` Daniel Santos
2017-02-10 16:54       ` Sandra Loosemore
2017-02-10 17:32         ` Daniel Santos
2017-04-01 22:37         ` Daniel Santos
2017-02-07 18:36 ` [PATCH 3/8] [i386] Adds class xlouge_layout and new fields to struct machine_function Daniel Santos
2017-02-07 18:36 ` [PATCH 4/8] [i386] Modify ix86_save_reg to optionally omit stub-managed registers Daniel Santos
2017-02-07 18:37 ` [PATCH 1/8] [i386] Minor refactoring Daniel Santos
2017-02-07 18:37 ` [PATCH 6/8] [i386] Add patterns and predicates foutline-msabi-xlouges Daniel Santos
2017-02-07 18:37 ` [PATCH 7/8] [i386] Add msabi pro/epilogue stubs to libgcc Daniel Santos
2017-02-07 18:37 ` [PATCH 5/8] [i386] Modify ix86_compute_frame_layout for foutline-msabi-xlogues Daniel Santos
2017-02-10 10:32 ` [RFC] [PATCH v3 0/8] [i386] Use out-of-line stubs for ms_abi pro/epilogues Uros Bizjak
2017-02-10 11:34   ` JonY
2017-02-10 17:20     ` Daniel Santos
2017-02-11  0:30       ` JonY
2017-02-11  7:24         ` Daniel Santos
2017-03-13 18:40         ` Daniel Santos
2017-03-10  4:42     ` Daniel Santos [this message]
2017-03-30 17:55       ` Daniel Santos
2017-03-30 23:28         ` JonY
2017-02-10 17:55   ` Daniel Santos

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=c09a2060-9c15-a0ec-6ec9-64617be5bb42@pobox.com \
    --to=daniel.santos@pobox.com \
    --cc=10walls@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ubizjak@gmail.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).