Re: [hpx-users] GSOC 2017

2017-03-21 Thread Hartmut Kaiser 
> TURN HPX INTO A REPLACEMENT FOR C++ RUNTIME.
> I didn't able to understand it clearly.

HPX currently implements only features of the C++ Standard related to 
concurrency and parallelism. This project targets filling the missing gaps such 
that in the end HPX can be used a s a replacement (or as an alternative) to the 
standard library implementation which comes with your compiler. 

This will probably will boil down to integrate HPX seamlessly with at least one 
of the existing standard library implementations. I'd assume that an important 
precondition for this would be for the student to demonstrate a solid knowledge 
of any of those (libstdc++, libc++, the Microsoft standard library or similar).

> what I have understood is we have to dynamically link hpx libraries to the
> applications during runtime.But it is actually done by dynamic linker
> itself.Please correct me if I am wrong. And please explain me the
> statement to some extend.

Hmmm, that's a misunderstanding. HPX is normally statically linked to an 
application in the same way as is any other C++ library. HPX itself may be used 
as a shared library, though, which might have caused the misconception of it 
being dynamically linked.

HTH
Regards Hartmut
---
http://boost-spirit.com
http://stellar.cct.lsu.edu



___
hpx-users mailing list
hpx-users@stellar.cct.lsu.edu
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users

Re: [hpx-users] FW: build hpx as static lib?

2017-03-21 Thread Alexander Neundorf 
On 2017 M03 20, Mon 23:45:58 CET niXman wrote:
>  From: niXman
> Sent: Saturday, March 18, 2017
> 
> > I faced with link error when "Linking CXX executable
> > ../../bin/1d_hydro_upwind"

can you create a minimal self-contained example (if possible without hpx) 
which shows this problem, and post it here ?

Alex

___
hpx-users mailing list
hpx-users@stellar.cct.lsu.edu
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users

Re: [hpx-users] [GSoC17] How about combining two vanguard project ideas related in C++17 parallelism?

2017-03-21 Thread Hartmut Kaiser 

> Hi, I'm a student interested in hpx of GSoC 2017.
> I read vanguard project ideas in hpx's github wiki.
> I'm interested in some topics related to C++ standardization and parallel
> programming.
> Anyway, I think "Work on Parallel Algorithms for HPX" and "Add
> Vectorization to par_unseq Implementations of Parallel Algorithms" are
> somewhat related in because they are parts of implementations of the C++17
> parallelism (N4409).
> So, I think it would be a idea to combine these two topics.
> Is there no problem about it?? How do you think about it?

The project ideas on that page are just that ideas and suggestions. I wouldn't 
exclude combining things the way you propose to do.

HTH
Regards Hartmut
---
http://boost-spirit.com
http://stellar.cct.lsu.edu


___
hpx-users mailing list
hpx-users@stellar.cct.lsu.edu
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users

Re: [hpx-users] GSoC 2017 Proposal Work on Parallel Algorithms for HPX

2017-03-21 Thread Thomas Heller 
Hi again

I've been through the full proposal now, and I think what I wrote below still 
holds.

On Dienstag, 21. März 2017 19:53:10 CET you wrote:
> On Dienstag, 21. März 2017 19:46:39 CET you wrote:
> > Hi Aja,
> > 
> > I think you should focus your proposal. As it stands right now, you will
> > not be able to complete everything. I strongly advice to pull together
> > some form of time plan on when you plan to have each part implemented,
> > given the vast number of algorithms you want to implement, it would be
> > great if you can in addition put in some references to already existing
> > solutions.
> > 
> > Please work on focusing your proposal.
> 
> Please ignore the previous email ... I only read the abstract on the mentors
> dashboard... I have to go through the full proposal again ;)
> 
> > On Samstag, 18. März 2017 15:20:28 CET Ajai George wrote:
> > > Hello,
> > > 
> > > I am Ajai V George, I had previously expressed my interest in doing a
> > > GSoC
> > > project with HPX. For the past week I was going through the hpx
> > > documentation and tutorial. I have been testing out examples and trying
> > > to
> > > write my own applications. I have also looked through the relevant
> > > codebase
> > > needed to resolve issues #1141 and #1338. I also read through the two
> > > papers on ParalleX for understanding the philosophy behind HPX. I
> > > believe
> > > that I can definitely complete this project and continue contributing
> > > further.
> > > 
> > > Please have a look at my GSoC application and help me make it better.
> > > Here
> > > is a link
> > >  > > 8Q
> > > KT BieY/edit?usp=sharing> to it.
> > > 
> > > Regards,
> > > 
> > > Ajai V George
> > > 
> > > On Mon, Mar 13, 2017 at 2:21 AM, Ajai George 
> > > 
> > > wrote:
> > > > Hello,
> > > > 
> > > > I am Ajai V George from BITS Pilani, Goa Campus, India. My major is
> > > > Electrical and Electronics Engineering. I currently work with
> > > > Professor
> > > > Santonu Sarkar from Centre for High Performance and Dependable Systems
> > > > (Department of Computer Science and Information Systems). My project
> > > > is
> > > > Building 2D Algorithms with shared memory in Thrust which is a CUDA
> > > > library. I am implementing Berkeley Structured Grid Dwarf by extending
> > > > Thrust.
> > > > 
> > > > Due to this project, I have significant experience with CUDA and with
> > > > implementing STL like data structures in CUDA. I have created a
> > > > block_2d
> > > > data
> > > > structure for Thrust for 2d data storage. I created a Thrust and thus
> > > > STL
> > > > compatible iterator for this. I also created an abstraction layer for
> > > > accessing windows (as described in structured grid dwarf) within this
> > > > data structure and an accompanying iterator which lazily generates
> > > > these
> > > > windows. I have created highly optimized for_each, transform, reduce,
> > > > and
> > > > transform_reduce functions for both the thrust 1D device vector and my
> > > > block_2d data structure. These algorithms use shared memory
> > > > efficiently
> > > > with proper memory access coalescence and no shared memory bank
> > > > conflicts. The reduction algorithm also uses a highly optimized tree
> > > > based approach. I have also created this framework such that it can be
> > > > extended to be used with cuFFT and cuBLAS libraries easily.
> > > > 
> > > > Due to the above background I believe, I can work on the Parallel
> > > > Algorithms for HPX project for GSoC 2017, specifically on extending
> > > > algorithms like scan, reduce, transform, for_each, fill, etc to work
> > > > with
> > > > hpx::vector. I have already cloned the repo and have built hpx and am
> > > > currently looking through the source code to see what would be
> > > > impacted
> > > > by
> > > > the project and what changes would be required.
> > > > 
> > > > I request help from the community in crafting my proposal, and in
> > > > understanding hpx codebase.
> > > > 
> > > > Regards,
> > > > 
> > > > Ajai V George


___
hpx-users mailing list
hpx-users@stellar.cct.lsu.edu
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users