public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/8286: Missing xmmintrin.h functions Date: Tue, 25 Mar 2003 17:27:00 -0000 [thread overview] Message-ID: <20030325171600.30516.qmail@sources.redhat.com> (raw) The following reply was made to PR target/8286; it has been noted by GNATS. From: Jan Hubicka <jh@suse.cz> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: Jan Hubicka <jh@suse.cz>, gcc-bugs@gcc.gnu.org, rakdver@atrey.karlin.mff.cuni.cz, gcc-gnats@gcc.gnu.org Subject: Re: other/8286: Missing xmmintrin.h functions Date: Tue, 25 Mar 2003 18:10:25 +0100 > > > > Synopsis: Missing xmmintrin.h functions > > > Zdenek, at least some of the functions in the list have been > > > added in the meantime. Can you try to update the list of > > > missing symbols? > > > > All of the symbols except for _m_* legacy names are supported now. > > Will they be added sometime (i.e. we should leave the report open), or not > (i.e. the report should be closed)? I think the report should be closed. It is not bug to not support obsoletted API. If we decide on supporting them we don't need the bugreport anyway. Honza > > W. > > ------------------------------------------------------------------------- > Wolfgang Bangerth email: bangerth@ticam.utexas.edu > www: http://www.ticam.utexas.edu/~bangerth/ >
next reply other threads:[~2003-03-25 17:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-25 17:27 Jan Hubicka [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-25 16:46 Wolfgang Bangerth 2003-03-25 12:59 Jan Hubicka 2003-03-25 2:09 bangerth 2002-10-19 7:56 rakdver
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=20030325171600.30516.qmail@sources.redhat.com \ --to=jh@suse.cz \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).