public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: gilles@rist.or.jp
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Bug in closed-source, proprietary software that I do not have access to
Date: Sat, 25 May 2019 17:20:00 -0000	[thread overview]
Message-ID: <beec7c97-88b7-6204-2673-ddf952dd6b66@netcologne.de> (raw)
In-Reply-To: <20190525144831.0000157C.0508@rist.or.jp>

Hi Gilles,

> Several SPEC benchmarks are available at no cost for non commercial
> usage.
> 
> See https://www.spec.org/order.html, you may qualify.

I checked, and I do not qualify - I am just a simple volunteer with
a day job which has nothing to do with maintaining gfortran, and
I do draw the line at paying for software in addition to the work
I donate to gcc.

It appears that wanting to supporting a closed-source,
commercial benchmark like SPEC and supporting a part of gcc
needed for that with mostly volunteers is not ideal.

Regards

	Thomas




  reply	other threads:[~2019-05-25 17:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-25 12:53 Thomas Koenig
2019-05-25 13:16 ` Toon Moene
2019-05-25 14:37   ` Thomas Koenig
2019-05-25 14:03 ` Richard Biener
2019-05-25 14:48 ` gilles
2019-05-25 17:20   ` Thomas Koenig [this message]
2019-05-25 17:01 ` Steve Kargl
2019-05-25 17:19   ` Toon Moene
2019-05-25 17:31     ` Thomas Koenig
2019-05-25 17:43       ` Toon Moene
2019-05-26 14:15         ` Toon Moene
2019-05-26 18:12           ` Thomas Koenig
2019-05-27  7:46             ` Martin Liška

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=beec7c97-88b7-6204-2673-ddf952dd6b66@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gilles@rist.or.jp \
    /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).