Skip to content

doc: upgrade Clang requirement to 3.4.2 - #12388

Closed
targos wants to merge 1 commit into
nodejs:masterfrom
targos:clang-342
Closed

doc: upgrade Clang requirement to 3.4.2#12388
targos wants to merge 1 commit into
nodejs:masterfrom
targos:clang-342

Conversation

@targos

Copy link
Copy Markdown
Member

Clang 3.4.1 has a bug that prevents compilation of V8.
As of Node.js 8.0.0 we stopped floating a workaround for this issue.

I don't have a test system to check if 3.4.2 is enough.

/cc @nodejs/build

Checklist

Clang 3.4.1 has a bug that prevents compilation of V8.
As of Node.js 8.0.0 we stopped floating a workaround for this issue.
@nodejs-github-botnodejs-github-bot added build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. labels Apr 13, 2017

@bnoordhuisbnoordhuis left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM and good catch on configure.

I'd be okay with raising the baseline to 3.5.2 or 3.6.2 for node 8. We'll be supporting it until 2021, it would make sense to start with a compiler that's not already long in the tooth.

@mhdawson

Copy link
Copy Markdown
Member

In terms 3.5.2 and 3.6.2 will those run on the existing OS levels were Clang is used in our regression runs ?

@jbergstroem

Copy link
Copy Markdown
Member

I'm all for raising the bar in node 8 as well. ubuntu trusty seems to offer clang 3.4, 3.5, 3.6 and 3.8.

Any arguments on 3.5.x vs 3.6.x?

@benjamingrbenjamingr left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bnoordhuis

Copy link
Copy Markdown
Member

In terms 3.5.2 and 3.6.2 will those run on the existing OS levels were Clang is used in our regression runs ?

I'd say so. I don't think we have any systems in our matrix where you can install 3.4 but not 3.5 or 3.6.

Any arguments on 3.5.x vs 3.6.x?

PPC support got a big boost in 3.6. Might be worth it for that reason alone.

@jbergstroem

Copy link
Copy Markdown
Member

@bnoordhuis said:
PPC support got a big boost in 3.6. Might be worth it for that reason alone.

Sounds good to me. The newer, the better.

@jasnell

Copy link
Copy Markdown
Member

CI since there's a change in the configure script here: https://ci.nodejs.org/job/node-test-pull-request/7489/

@jasnell

Copy link
Copy Markdown
Member

CI failure is unrelated

@mhdawsonmhdawson left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

jasnell pushed a commit that referenced this pull request Apr 18, 2017
Clang 3.4.1 has a bug that prevents compilation of V8.
As of Node.js 8.0.0 we stopped floating a workaround for this issue.
PR-URL: #12388
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
@jasnell

Copy link
Copy Markdown
Member

Landed in b4f59a7

@jasnelljasnell closed this Apr 18, 2017
@jasnelljasnell mentioned this pull request May 11, 2017
@targos
targos deleted the clang-342 branch June 1, 2017 07:38
@gibfahngibfahn mentioned this pull request Jun 15, 2017
3 tasks
@gibfahn

Copy link
Copy Markdown
Member

I'm assuming this doesn't apply to v7 and earlier, LMK if that's not correct.

@bnoordhuis

Copy link
Copy Markdown
Member

We carry a compatibility patch in older branches although it's no longer tested now that the clang 3.4.1 buildbot has been decommissioned. I'd back-port this PR, that way people know what the known-good version of clang is.

gibfahn pushed a commit that referenced this pull request Jun 20, 2017
Clang 3.4.1 has a bug that prevents compilation of V8.
As of Node.js 8.0.0 we stopped floating a workaround for this issue.
PR-URL: #12388
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
@gibfahn

Copy link
Copy Markdown
Member

Backported in 11a7875

MylesBorins pushed a commit that referenced this pull request Jul 11, 2017
Clang 3.4.1 has a bug that prevents compilation of V8.
As of Node.js 8.0.0 we stopped floating a workaround for this issue.
PR-URL: #12388
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
@MylesBorinsMylesBorins mentioned this pull request Jul 18, 2017
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

buildIssues and PRs related to build files or the CI.docIssues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants

@targos@mhdawson@jbergstroem@bnoordhuis@jasnell@gibfahn@benjamingr@cjihrig@nodejs-github-bot