Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop gcc 4.7 and intel 14 from tested compiler suite, end of 2017-January #603

Closed
hcedwar opened this issue Jan 10, 2017 · 13 comments
Closed
Assignees
Labels
Enhancement Improve existing capability; will potentially require voting
Milestone

Comments

@hcedwar
Copy link
Contributor

hcedwar commented Jan 10, 2017

No description provided.

@hcedwar hcedwar added the Enhancement Improve existing capability; will potentially require voting label Jan 10, 2017
@hcedwar hcedwar added this to the 2017-February milestone Jan 10, 2017
@nmhamster
Copy link
Contributor

I think GCC 4.7.2 support is still required for IC support isn't it? We have not had a firm decision to retire that yet.

@hcedwar
Copy link
Contributor Author

hcedwar commented Jan 10, 2017

cite: SART teleconference 01/10/17 at 10:50am; a historic moment!

@crtrott
Copy link
Member

crtrott commented Jan 10, 2017

Yeah IC codes confirmed transition to GCC 4.9.3 with a firm kill date of 4.7 for end of January.

@hcedwar
Copy link
Contributor Author

hcedwar commented Jan 10, 2017

TODO: Assess how far back we could drop; perhaps gcc 4.8 ?

@crtrott
Copy link
Member

crtrott commented Jan 10, 2017

Yeah I would go for Intel 15 and GCC 4.8.4 for now.

@nmhamster
Copy link
Contributor

We had been told that the most likely jump would be 17.1 and GCC 4.9.3.

@crtrott
Copy link
Member

crtrott commented Jan 10, 2017

Yeah thats what IC is doing. Not sure we should go there right away. Also its not clear that the capacity machines are upgrading right away. Looks like those are still on Intel 15.

@hcedwar
Copy link
Contributor Author

hcedwar commented Feb 15, 2017

Must be deferred. Reevaluate in April.

@hcedwar hcedwar modified the milestones: Backlog, 2017-February Feb 15, 2017
@mhoemmen
Copy link
Contributor

If it helps -- one of the issues I've found with GCC 4.7.2 is that lambdas don't quite understand implicit capture. If you capture explicitly, that seems to help.

@hcedwar
Copy link
Contributor Author

hcedwar commented Jun 26, 2017

Trilinos is moving to gcc 4.8.4 as the floor version. Time to move floor to gcc 4.8.4 and Intel 15. Drop earlier versions from nightly testing, officially supported lists, and testing scripts. Replace gcc 4.7.2 with gcc 4.8.4 in Jenkins nightly testing.

@hcedwar hcedwar modified the milestones: 2017-August (middle), Backlog Jun 26, 2017
@hcedwar
Copy link
Contributor Author

hcedwar commented Aug 8, 2017

@crtrott - LAMMPS ok with gcc 4.8.4 and Intel 15 as the floor version?

@hcedwar
Copy link
Contributor Author

hcedwar commented Sep 20, 2017

Verify Titan has CUDA 7.5, then drop CUDA 7.0 as well

@bjoo
Copy link
Contributor

bjoo commented Sep 20, 2017 via email

@hcedwar hcedwar added the Blocks Promotion Overview issue for release-blocking bugs label Nov 1, 2017
@hcedwar hcedwar modified the milestones: 2017 October, 2017 December Nov 1, 2017
crtrott added a commit that referenced this issue Dec 5, 2017
@crtrott crtrott added InDevelop and removed Blocks Promotion Overview issue for release-blocking bugs labels Dec 5, 2017
@crtrott crtrott closed this as completed Dec 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improve existing capability; will potentially require voting
Projects
None yet
Development

No branches or pull requests

5 participants