public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rob <robpilling@gmail.com>
To: Albert Abramson <abramson.albert@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: programming language that does not inhibit further optimization by gcc
Date: Tue, 15 Oct 2013 12:00:00 -0000	[thread overview]
Message-ID: <CAPQ98VUvEqzuWuTY6FukoAX-5Bbj9G48QTejGVFCweb-QOEY4w@mail.gmail.com> (raw)
In-Reply-To: <CAEvgbXFD9egt-32A00+Unf4Q7j_sa7ucBE7p7ZNFiWVnNOW+4A@mail.gmail.com>

GCC does value analysis similar to what you mentioned. You'll find it
under the -fdump-tree-vrp options. To provide extra information you
can add range checks which GCC will pick up on. If you know a value is
small, use a small integer type and gcc will pick up the range of
values which can be assigned to it.

What are the problems you're trying to solve? Is it a low memory
system you're running on?

If you're after performance, add restrict to your parameters and
either use unions to get around aliasing or do what the Linux dev team
do with -fno-strict-aliasing.

Regarding threading - I think trying to use multiple threads without
having to learn thread libraries is a bit of a gamble. Threading is
difficult even in high level languages and you should have a good
background before approaching.

For struct packing, I suppose you could just order your entries
largest-first which is one approach, but it's kinda like the 0-1
knapsack problem.


On 15 October 2013 01:31, Albert Abramson <abramson.albert@gmail.com> wrote:
> I have been looking everywhere online and talking to other coders at
> every opportunity about this, but cannot find a complete answer.
> Different languages have different obstacles to complete optimization.
>  Software developers often have to drop down into non-portable
> Assembly because they can't get the performance or small size of
> hand-optimized Assembly for their particular platform.
>
> The C language has the alias issue that limits the hoisting of loads.
> Unless the programmer specifies that two arrays will never overlap
> using the 'restrict' keyword, the compiler may not be able to handle
> operations on arrays efficiently because of the unlikely event that
> the arrays could overlap.  Most/all languages also demand the
> appearance of serialization of instructions and memory operations, as
> well as extreme correctness in even the most unlikely circumstances,
> even where the programmer may not need them.
>
> Is there a language out there (similar to Fortran or a dialect of C)
> that doesn't inhibit the compiler from taking advantage of every
> optimization possible?  Is there some way to provide a C/C++ compiler
> with extra information about variables and programs so that it can
> maximize performance or minimize size?  For example:
>
> int age = 21;    //[0, 150)  setting maximum limits, compiler could use byte int
> int outsideTemp = 20;    //[-273, 80]
> float ERA = 297;           //[0, 1000, 3]   [min, max, digits of
> accuracy needed]
>
> Better yet, allow some easier way of spawning multiple threads without
> have to learn all of the Boost libraries, OpenCL, or OpenGL.  In other
> words, is there yet a language that is designed only for performance
> that places no limits on compiler optimizations?  Is there a language
> that allows the compiler to pack struct variables in tighter by
> reorganizing those values, etc?
>
> If not, is it possible to put together some dialect of C/C++ that
> replaces Assembly outright?
>
> --
> Max Abramson
> “In the end, more than freedom, they wanted security. They wanted a
> comfortable life, and they lost it all – security, comfort, and
> freedom. When the Athenians finally wanted not to give to society but
> for society to give to them, when the freedom they wished for most was
> freedom from responsibility, then Athens ceased to be free and was
> never free again.” --Sir Edward Gibbon

  reply	other threads:[~2013-10-15 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15  0:31 Albert Abramson
2013-10-15 12:00 ` Rob [this message]
2019-03-30  7:14   ` Albert Abramson
2019-03-30 10:42     ` David Brown
2013-10-15 14:45 ` Ian Lance Taylor
2013-10-15 22:09 ` gwenael chailleu

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=CAPQ98VUvEqzuWuTY6FukoAX-5Bbj9G48QTejGVFCweb-QOEY4w@mail.gmail.com \
    --to=robpilling@gmail.com \
    --cc=abramson.albert@gmail.com \
    --cc=gcc@gcc.gnu.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).