From: Tom de Vries <Tom_deVries@mentor.com>
To: Cesar Philippidis <cesar@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [og7] vector_length extension part 2: Generalize state propagation and synchronization
Date: Thu, 05 Apr 2018 14:14:00 -0000 [thread overview]
Message-ID: <acdb7a62-0d75-26e7-5bd5-2377d68e92dd@mentor.com> (raw)
In-Reply-To: <8b3e0c90-5d5f-3cd7-b677-e752e5a38478@mentor.com>
On 04/03/2018 05:00 PM, Tom de Vries wrote:
> + unsigned int psize = ROUND_UP (data.offset, oacc_bcast_align);
> + unsigned int pnum = (nvptx_mach_vector_length () > PTX_WARP_SIZE
> + ? nvptx_mach_max_workers () + 1
> + : 1);
This claims too much space for a simple long vector loop. Filed as
PR85231 - "[og7, openacc, nvptx] Too much shared memory claimed for long
vector length".
Thanks,
- Tom
next prev parent reply other threads:[~2018-04-05 14:14 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 21:17 [og7] vector_length extension part 1: generalize function and variable names Cesar Philippidis
2018-03-02 16:55 ` [og7] vector_length extension part 2: Generalize state propagation and synchronization Cesar Philippidis
2018-03-21 17:16 ` Tom de Vries
2018-03-22 8:05 ` Cesar Philippidis
2018-03-22 14:16 ` Tom de Vries
2018-03-22 14:35 ` Cesar Philippidis
2018-03-22 14:24 ` Tom de Vries
2018-03-22 15:18 ` Cesar Philippidis
2018-03-22 16:20 ` Tom de Vries
2018-03-22 17:26 ` Cesar Philippidis
2018-03-22 17:58 ` Tom de Vries
2018-03-22 19:32 ` Cesar Philippidis
2018-03-23 8:56 ` Tom de Vries
2018-03-23 14:35 ` Tom de Vries
2018-03-22 15:04 ` Tom de Vries
2018-03-22 17:14 ` Cesar Philippidis
2018-03-22 17:47 ` Tom de Vries
2018-03-22 17:48 ` Cesar Philippidis
2018-03-22 18:00 ` Tom de Vries
2018-03-23 13:14 ` Tom de Vries
2018-03-23 13:16 ` Tom de Vries
2018-03-23 14:18 ` Tom de Vries
2018-03-23 16:30 ` Tom de Vries
2018-03-30 1:50 ` Tom de Vries
2018-03-30 14:48 ` Tom de Vries
2018-03-30 15:06 ` Cesar Philippidis
2018-03-30 15:35 ` Tom de Vries
2018-04-05 16:33 ` Tom de Vries
2018-04-03 14:52 ` [nvptx] Use MAX, MIN, ROUND_UP macros Tom de Vries
2018-04-03 15:00 ` [og7] vector_length extension part 2: Generalize state propagation and synchronization Tom de Vries
2018-04-05 14:06 ` Tom de Vries
2018-04-05 14:14 ` Tom de Vries [this message]
2018-03-02 17:51 ` [og7] vector_length extension part 3: reductions Cesar Philippidis
2018-04-05 14:07 ` Tom de Vries
2018-04-05 16:26 ` Tom de Vries
2018-03-02 19:18 ` [og7] vector_length extension part 4: target hooks and automatic parallelism Cesar Philippidis
2018-03-21 15:55 ` Tom de Vries
2018-03-21 20:28 ` Cesar Philippidis
2018-03-26 14:25 ` Tom de Vries
2018-03-26 14:37 ` Cesar Philippidis
2018-03-26 16:52 ` Tom de Vries
2018-03-27 12:16 ` Tom de Vries
2018-03-26 17:13 ` Tom de Vries
2018-04-05 16:32 ` Tom de Vries
2018-03-02 20:47 ` [og7] vector_length extension part 5: libgomp and tests Cesar Philippidis
2018-03-16 13:50 ` Thomas Schwinge
2018-03-27 13:00 ` Tom de Vries
2018-04-05 16:36 ` Tom de Vries
2018-03-09 15:29 ` [og7] vector_length extension part 1: generalize function and variable names Thomas Schwinge
2018-03-09 15:31 ` Cesar Philippidis
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=acdb7a62-0d75-26e7-5bd5-2377d68e92dd@mentor.com \
--to=tom_devries@mentor.com \
--cc=cesar@codesourcery.com \
--cc=gcc-patches@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).