[Beowulf] Not OT, but a quick link to an article on InsideHPC

Fri Mar 24 12:01:44 PDT 2017

Thanks for the info. I think I was going to just "pathscale.com" because 
a google search was turning up that instead of "www.pathscale.com", 
although it's been a couple of months, so my memory may not be 100% 
accurate.

Prentice

On 03/24/2017 02:17 PM, C Bergström wrote:
> To clarify
>
> www.pathscale.com has been up and available (except for some human
> errors) since 2009. We have had a few outages, but most of that can
> frankly be blamed to me. In this month (March 2017) I have let it go
> down and there was probably some time in Feb as well. (Honestly our
> site is pretty low traffic and if ever an issue most people know to
> just email me or support)
>
> So before it was up and now it's down. If we resolve some of our
> funding issues I'll bring it back online. (Lets say 50/50 chances)
>
> The customer portal is/was (currently down)
> http://my.pathscale.com
>
> If you haven't purchased support in the past few years you probably
> aren't in my.psc and may need to do a password reset to get access to
> your profile.
> --------
> Hopefully if you have specific questions/concerns please email me
> privately. I don't mind our dirty laundry being public, but it may be
> noise for others on the list.
>
>
>
> On Sat, Mar 25, 2017 at 2:08 AM, Prentice Bisbal <pbisbal at pppl.gov> wrote:
>> Chris,
>>
>> Thanks for clarifying the difference between EKOPath/Path64 and Pathscale. I
>> probably meant to say Path64 and not Open64.
>>
>> So are you saying the pathscale.com site has been up consistently, and is
>> still up? I've been trying to get there for months, originally to see what
>> the latest version of your compiler was and update our installation the
>> latest version if necessary, and then I kept checking to see if you were
>> still in business.  I still can't get there today. I've tried from work,
>> home, etc. I can't get there right now, in fact. I type in "pathscale.com"
>> in the address bar of Firefox, and just get a spinning wheel in the tab and
>> the text "Connecting..." If pathscale,com is still up, I'd be happy to work
>> with you to trouble shoot this problem.
>>
>> I was able to get to some sort of customer login portal, but not the main
>> pathscale.com site. This is why I thought Pathscale was already out of
>> business, and how I stumbled on that post for whatever open source compiler
>> that was.
>>
>> Prentice Bisbal
>> Lead Software Engineer
>> Princeton Plasma Physics Laboratory
>> http://www.pppl.gov
>>
>>
>> On 03/24/2017 11:56 AM, C Bergström wrote:
>>> Total bullshit - The website has been down a few times, but they were
>>> things like a server restart mishape and people errors. I'm letting
>>> the site go down now so people realize I'm serious about this.
>>>
>>> I generally have very little or nothing to do with Open64. That is/was
>>> a semi-hostile group of people whom I didn't want much interaction
>>> with at all. Open64 is/was dead and maybe you mistook my words as
>>> PathScale when what I meant was that Open64 is dead to me and I wanted
>>> nothing to do with them.
>>> ------------
>>> Clarification on open source - We made EKOPath (Not ENZO) fully open
>>> source from 2009-2012. It was done under the path64 naming to avoid
>>> confusion with our EKOPath brand. The code was (I've pulled it)
>>> available on github and anyone could download and build it. The amount
>>> of people who cared seemed to be so small and the confusion in
>>> answering questions just wasn't worth it. In 2012 we decided just to
>>> switch back to a closed model for both EKOPath and ENZO.
>>>
>>> I realize we may be quiet and not dancing around posting bs marketing,
>>> but I can assure you me and the small army of engineers working on the
>>> compiler are quite alive. At peak we had 25 people working on the
>>> compiler and other connected things. (This is btw more than "old"
>>> PathScale had in terms of compiler people)
>>>
>>> Sorry if my tone is wrong, but I do appreciate the feedback.
>>>
>>> Some things we've done
>>> * OpenACC across CPU/GPU (ARMv8, Power8, AMD dGPU, AMD APU and NVIDIA)
>>> * OpenMP4 ...
>>>
>>> Tons of work on top of clang/llvm infrastructure to fix it's complete
>>> deficiency in the "high" level optimization catagories. All the
>>> multicore/GPU optimizations which are needed for autopar, autogpu and
>>> OpenACC (which puts a lot of pressure on the compiler)
>>>
>>> KNC hardware wasn't all that great, but we wrote a micro OS/firmware
>>> that replaced the bloated thing from Intel and exposed an interface
>>> similar to a GPU (open source)
>>>
>>> We've got a semi-experimental IDE which tightly couples clang+compiler
>>> backend for showing users what's being optimized and what's not..
>>>
>>> In recent years we've done work for several national labs, AMD, Cavium
>>> and others... (Not to mention other products we've done which are very
>>> specific to some aerospace customers)...
>>>
>>> In honesty - traditional EKOPath customers may be disappointed because
>>> all this work focuses on what I think is value for the future and not
>>> immediate value for Intel centric world. Actually in hindsight, I
>>> should have just had our core business go battle against Intel on
>>> common benchmarks. If we're a "SPEC" compiler then people would
>>> actually care..
>>>
>>>
>>> On Fri, Mar 24, 2017 at 11:40 PM, Prentice Bisbal <pbisbal at pppl.gov>
>>> wrote:
>>>> Chris
>>>>
>>>> Don't take this the wrong way, but I thought Pathscale closed shop a long
>>>> time ago. We license Pathscale here, and I haven't been able to access
>>>> the
>>>> pathscale.com website for months, so I assumed you closed shop a long
>>>> time
>>>> ago. Googling for information on the current state of Pathscale, I came
>>>> across a post on a Open64 mailing list/forum that made it sound like
>>>> Pathscale had tried to open source the compiler, failed, and went out of
>>>> business. That post was from someone withing the company (you?). I can
>>>> try
>>>> to find the post in question if interested, but it would probably take
>>>> some
>>>> time.
>>>>
>>>> Prentice
>>>>
>>>>
>>>> On 03/23/2017 05:27 PM, C Bergström wrote:
>>>>> Tiz the season for HPC software to die?
>>>>>
>>>>>
>>>>> https://www.hpcwire.com/2017/03/23/hpc-compiler-company-pathscale-seeks-life-raft/
>>>>>
>>>>> (sorry I don't mean to hijack your thread, but timing of both
>>>>> announcements is quite overlapping)
>>>>>
>>>>> On Fri, Mar 24, 2017 at 5:16 AM, Joe Landman <joe.landman at gmail.com>
>>>>> wrote:
>>>>>> For those who I've not talked with yet ...
>>>>>>
>>>>>> http://insidehpc.com/2017/03/scalable-informatics-closes-shop/
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Joe Landman
>>>>>> e: joe.landman at gmail.com
>>>>>> t: @hpcjoe
>>>>>> c: +1 734 612 4615
>>>>>> w: https://scalability.org
>>>>>> _______________________________________________
>>>>>> Beowulf mailing list, Beowulf at beowulf.org sponsored by Penguin
>>>>>> Computing
>>>>>> To change your subscription (digest mode or unsubscribe) visit
>>>>>> http://www.beowulf.org/mailman/listinfo/beowulf
>>>>> _______________________________________________
>>>>> Beowulf mailing list, Beowulf at beowulf.org sponsored by Penguin Computing
>>>>> To change your subscription (digest mode or unsubscribe) visit
>>>>> http://www.beowulf.org/mailman/listinfo/beowulf
>>>>
>>>> _______________________________________________
>>>> Beowulf mailing list, Beowulf at beowulf.org sponsored by Penguin Computing
>>>> To change your subscription (digest mode or unsubscribe) visit
>>>> http://www.beowulf.org/mailman/listinfo/beowulf
>>