public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/32972] performance of pack/unpack
Date: Wed, 19 Mar 2008 15:44:00 -0000	[thread overview]
Message-ID: <20080319154347.22341.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32972-10391@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from tkoenig at gcc dot gnu dot org  2008-03-19 15:43 -------
Subject: Bug 32972

Author: tkoenig
Date: Wed Mar 19 15:42:55 2008
New Revision: 133344

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=133344
Log:
2008-03-19  Thomas Koenig  <tkoenig@gcc.gnu.org>

        PR libfortran/32972
        * Makefile.am (in_pack_c): Add in_pack_i1.c, in_pack_i2.c,
        in_pack_r4.c, in_pack_r8.c, in_pack_r10.c and in_pack_r16.c.
        (in_unpack_c): Add in_unpack_i1.c, in_unpack_i2.c,
        in_unpack_r4.c, in_unpack_r8.c, in_unpack_r10.c and
        in_unpack_r16.c.
        * Makefile.in: Regenerate.
        * libgfortran.h:  Add prototypes for internal_pack_1,
        internal_pack_2, internal_pack_16, internal_pack_r4,
        internal_pack_r8, internal_pack_r10, internal_pack_r16,
        internal_pack_c10 and internal_pack_c16.  Add prototypes for
        internal_unpack_1, internal_unpack_2, internal_unpack_16,
        internal_unpack_r4, internal_unpack_r8, internal_unpack_r10,
        internal_unpack_r16, internal_unpack_c10 and
        internal_unpack_c16.
        * runtime/in_pack_generic.c (internal_pack): Use sizeof instead
        of hardwired sizes.
        Add calls to internal_pack_1, internal_pack_2,
        internal_pack_16, internal_pack_r4, internal_pack_r8,
        internal_pack_r10, internal_pack_r16, internal_pack_c10 and
        internal_pack_c16.
        * runtime/in_unpack_generic.c (internal_unpack):  Use sizeof
        instead of hardwired sizes.
        Add calls to internal_unpack_1, internal_unpack_2,
        internal_unpack_16, internal_unpack_r4, internal_unpack_r8,
        internal_unpack_r10, internal_unpack_r16, internal_unpack_c10
        and internal_unpack_c16.
        * generated/in_pack_r4.c:  New file.
        * generated/in_pack_i2.c:  New file.
        * generated/in_unpack_i1.c:  New file.
        * generated/in_pack_r10.c:  New file.
        * generated/in_unpack_r4.c:  New file.
        * generated/in_unpack_i2.c:  New file.
        * generated/in_unpack_r16.c:  New file.
        * generated/in_pack_r8.c:  New file.
        * generated/in_unpack_r10.c:  New file.
        * generated/in_unpack_r8.c:  New file.
        * generated/in_pack_r16.c:  New file.
        * generated/in_pack_i1.c:  New file.

2008-03-19  Thomas Koenig  <tkoenig@gcc.gnu.org>

        PR libfortran/32972
        * gfortran.dg/internal_pack_1.f90:  New test case.
        * gfortran.dg/internal_pack_2.f90:  New test case.
        * gfortran.dg/internal_pack_3.f90:  New test case.


Added:
    trunk/gcc/testsuite/gfortran.dg/internal_pack_1.f90
    trunk/gcc/testsuite/gfortran.dg/internal_pack_2.f90
    trunk/gcc/testsuite/gfortran.dg/internal_pack_3.f90
    trunk/libgfortran/generated/in_pack_i1.c
    trunk/libgfortran/generated/in_pack_i2.c
    trunk/libgfortran/generated/in_pack_r10.c
    trunk/libgfortran/generated/in_pack_r16.c
    trunk/libgfortran/generated/in_pack_r4.c
    trunk/libgfortran/generated/in_pack_r8.c
    trunk/libgfortran/generated/in_unpack_i1.c
    trunk/libgfortran/generated/in_unpack_i2.c
    trunk/libgfortran/generated/in_unpack_r10.c
    trunk/libgfortran/generated/in_unpack_r16.c
    trunk/libgfortran/generated/in_unpack_r4.c
    trunk/libgfortran/generated/in_unpack_r8.c
Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/Makefile.am
    trunk/libgfortran/Makefile.in
    trunk/libgfortran/libgfortran.h
    trunk/libgfortran/runtime/in_pack_generic.c
    trunk/libgfortran/runtime/in_unpack_generic.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32972


  parent reply	other threads:[~2008-03-19 15:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03  6:39 [Bug libfortran/32972] New: " tkoenig at gcc dot gnu dot org
2007-08-10 20:58 ` [Bug libfortran/32972] " tkoenig at gcc dot gnu dot org
2007-08-10 21:00 ` tkoenig at gcc dot gnu dot org
2007-08-11 20:34 ` tkoenig at gcc dot gnu dot org
2007-08-16 18:16 ` tkoenig at gcc dot gnu dot org
2007-08-24 16:17 ` tkoenig at gcc dot gnu dot org
2007-12-08 18:31 ` jvdelisle at gcc dot gnu dot org
2007-12-08 20:26 ` tkoenig at gcc dot gnu dot org
2007-12-08 21:30 ` fxcoudert at gcc dot gnu dot org
2007-12-08 21:57 ` jvdelisle at verizon dot net
2007-12-09 10:33 ` tkoenig at netcologne dot de
2008-03-19  9:27 ` tkoenig at gcc dot gnu dot org
2008-03-19 15:44 ` tkoenig at gcc dot gnu dot org [this message]
2008-03-19 16:49 ` dominiq at lps dot ens dot fr
2008-03-19 16:57 ` tkoenig at gcc dot gnu dot org
2008-03-19 16:58 ` tkoenig at gcc dot gnu dot org
2008-03-20  9:55 ` dominiq at lps dot ens dot fr
2008-03-20 10:55 ` tkoenig at gcc dot gnu dot org
2008-03-20 11:59 ` tkoenig at gcc dot gnu dot org
2008-03-21 14:38 ` tkoenig at gcc dot gnu dot org
2008-03-21 15:34 ` tkoenig at gcc dot gnu dot org
2008-03-23 22:21 ` tkoenig at gcc dot gnu dot org
2008-03-28 23:24 ` tkoenig at gcc dot gnu dot org
2008-04-13 20:17 ` tkoenig at gcc dot gnu dot org
2008-04-14 18:52 ` tkoenig at gcc dot gnu dot org
2010-02-20 22:12 ` burnus at gcc dot gnu dot org
2010-03-01 22:54 ` tkoenig at gcc dot gnu dot org

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=20080319154347.22341.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).