[Driver][SYCL]Emit an error if c compilation is forced using -x c or -x c-header when -fsycl mode is used

.github/workflows/clang-format.yml

@@ -0,0 +1,30 @@
+name: clang-format-check
+
+on:
+  pull_request:
+    branches:
+    - sycl
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+      with:
+        fetch-depth: 2
+
+    - name: Get clang-format first
+      run: sudo apt-get install -yqq clang-format-9
+
+    - name: Run clang-format for the patch
+      run: |
+        git diff -U0 --no-color ${GITHUB_SHA}^1 ${GITHUB_SHA} -- | ./clang/tools/clang-format/clang-format-diff.py -p1 -binary clang-format-9 > ./clang-format.patch
+
+    # Add patch with formatting fixes to CI job artifacts
+    - uses: actions/upload-artifact@v1
+      with:
+        name: clang-format-patch
+        path: ./clang-format.patch
+
+    - name: Check if clang-format patch is empty
+      run: bash -c "if [ -s ./clang-format.patch ]; then cat ./clang-format.patch; exit 1; fi"

.github/workflows/gh_pages.yml

@@ -0,0 +1,47 @@
+name: Generate Doxygen documentation
+
+on:
+  schedule:
+  - cron: 0 1 * * *
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+      with:
+        ref: sycl
+        path: repo
+    - name: Install deps
+      run: |
+        sudo apt-get install -y doxygen graphviz ssh ninja-build
+        sudo pip3 install sphinx recommonmark sphinx_markdown_tables
+    - name: Build Docs
+      run: |
+        mkdir -p $GITHUB_WORKSPACE/build
+        cd $GITHUB_WORKSPACE/build
+        python $GITHUB_WORKSPACE/repo/buildbot/configure.py -w $GITHUB_WORKSPACE \
+        -s $GITHUB_WORKSPACE/repo -o $GITHUB_WORKSPACE/build -t Release --docs
+        cmake --build . --target doxygen-sycl
+        cmake --build . --target docs-sycl-html
+    - name: Deploy
+      env:
+        SSH_KEY: ${{secrets.ACTIONS_DEPLOY_KEY}}
+      run: |
+        mkdir -p ~/.ssh
+        echo "$SSH_KEY" > ~/.ssh/id_rsa
+        chmod 600 ~/.ssh/id_rsa
+        eval "$(ssh-agent -s)"
+        ssh-add -k ~/.ssh/id_rsa
+        git clone [email protected]:intel/llvm-docs.git docs
+        cd $GITHUB_WORKSPACE/docs
+        git rm -rf .
+        touch .nojekyll
+        yes | \cp -rf $GITHUB_WORKSPACE/build/tools/sycl/doc/html/* .
+        mkdir doxygen
+        yes | \cp -rf $GITHUB_WORKSPACE/build/tools/sycl/doc/doxygen/html/* doxygen/
+        git config --global user.name "iclsrc"
+        git config --global user.email "[email protected]"
+        git add .
+        git diff-index --quiet HEAD || git commit -m "Update docs" -s
+        git push

.github/workflows/linux_post_commit.yml

@@ -0,0 +1,70 @@
+name: Linux Post Commit Checks
+
+on:
+  push:
+    branches:
+      - sycl
+jobs:
+   check:
+     runs-on: ubuntu-latest
+     strategy:
+       fail-fast: false
+       matrix:
+         config: ["Default", "SharedLibs", "Assertions"]
+
+     steps:
+     - uses: actions/checkout@v2
+       with:
+         path: src
+     - name: Install Ubuntu deps
+       run: sudo apt install -y ninja-build
+     - name: Configure
+       run: |
+         CONFIG=${{ matrix.config }}
+         case $CONFIG in
+             Default)
+                 export ARGS=""
+                 ;;
+             SharedLibs)
+                 export ARGS="--shared-libs"
+                 ;;
+             Assertiosn)
+                 export ARGS="--assertions"
+                 ;;
+         esac
+         mkdir -p $GITHUB_WORKSPACE/build
+         cd $GITHUB_WORKSPACE/build
+         python3 $GITHUB_WORKSPACE/src/buildbot/configure.py -w $GITHUB_WORKSPACE \
+         -s $GITHUB_WORKSPACE/src -o $GITHUB_WORKSPACE/build -t Release --no-ocl $ARGS
+     - name: Compile
+       run: |
+         python3 $GITHUB_WORKSPACE/src/buildbot/compile.py -w  $GITHUB_WORKSPACE \
+         -s  $GITHUB_WORKSPACE/src -o $GITHUB_WORKSPACE/build
+     - name: check-llvm
+       if: always()
+       run: |
+         python3 $GITHUB_WORKSPACE/src/buildbot/check.py -w  $GITHUB_WORKSPACE \
+         -s  $GITHUB_WORKSPACE/src -o $GITHUB_WORKSPACE/build -t check-llvm
+     - name: check-clang
+       if: always()
+       run: |
+         python3 $GITHUB_WORKSPACE/src/buildbot/check.py -w  $GITHUB_WORKSPACE \
+         -s  $GITHUB_WORKSPACE/src -o $GITHUB_WORKSPACE/build -t check-clang
+     - name: check-sycl
+       if: always()
+       run: |
+         python3 $GITHUB_WORKSPACE/src/buildbot/check.py -w  $GITHUB_WORKSPACE \
+         -s  $GITHUB_WORKSPACE/src -o $GITHUB_WORKSPACE/build -t check-sycl
+     - name: check-llvm-spirv
+       if: always()
+       run: |
+         python3 $GITHUB_WORKSPACE/src/buildbot/check.py -w  $GITHUB_WORKSPACE \
+         -s  $GITHUB_WORKSPACE/src -o $GITHUB_WORKSPACE/build -t check-llvm-spirv
+     - name: Pack
+       run: tar -czvf llvm_sycl.tar.gz -C $GITHUB_WORKSPACE/build/install .
+     - name: Upload artifacts
+       uses: actions/upload-artifact@v1
+       with:
+         name: sycl_linux_${{ matrix.config }}
+         path: llvm_sycl.tar.gz
+

CONTRIBUTING.md

@@ -1,10 +1,101 @@
-# Contributing to LLVM
+# Contributing
 
-Thank you for your interest in contributing to LLVM! There are many ways to
-contribute, and we appreciate all contributions.
+## License
+Intel Project for LLVM\* technology is licensed under the terms of the
+Apache-2.0 with LLVM-exception license ([LICENSE.txt](llvm/LICENSE.TXT))
+to ensure our ability to contribute this project to the LLVM project
+under the same license.
+
+By contributing to this project, you agree to the Apache-2.0 with
+LLVM-exception license and copyright terms there in and release your
+contribution under these terms.
+
+## Sign your work
+Please use the sign-off line at the end of your contribution. Your
+signature certifies that you wrote the contribution or otherwise have
+the right to pass it on as an open-source contribution, and that you
+agree to provide your contribution under the terms of the licenses
+noted above. The rules are pretty simple: if you can certify the
+below (from [developercertificate.org](http://developercertificate.org)):
+
+```
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+660 York Street, Suite 102,
+San Francisco, CA 94110 USA
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.
+```
+
+Then you just add a line to every git commit message:
+
+    Signed-off-by: Joe Smith <[email protected]>
+
+Use your real name (sorry, no pseudonyms or anonymous contributions.)
+
+If you set your `user.name` and `user.email` git configs, you can sign your
+commit automatically with `git commit -s`.
+
+## Contribution process
+
+### Development
+
+- Create a personal fork of the project on GitHub
+  - For the DPC++ Compiler project, use **sycl** branch as baseline for your
+    changes. See [Get Started Guide](sycl/doc/GetStartedGuide.md).
+- Prepare your patch (follow
+  [LLVM coding standards](https://llvm.org/docs/CodingStandards.html))
+- Build the project and run all tests
+
+### Review and acceptance testing
+
+- Create a pull request for your changes following [Creating a pull request
+instructions](https://help.github.com/articles/creating-a-pull-request/)
+- CI will run signed-off check as soon as PR is created, see **check_pr** CI
+check for results
+- CI will run build and functional testing check as soon as PR is approved by
+Intel representative
+  - New approval is needed if PR was updated (e.g. during code review)
+- Once PR is approved and all checks pass, the pull request is ready for merge
+
+### Merge
+
+Project maintainers merge pull requests using one of the following options:
+- [Rebase and merge] The preferable choice for PRs containing a single commit
+- [Squash and merge] Used when there are multiple commits in the PR
+  - Squashing is done to make sure that the project is buildable on any commit
+- [Create a merge commit] Used for LLVM pull-down PRs to preserve hashes of the
+commits pulled from the LLVM community repository
+
+
+*Other names and brands may be claimed as the property of others.
 
-To get started with contributing, please take a look at the
-[Contributing to LLVM](https://llvm.org/docs/Contributing.html) guide. It
-describes how to get involved, raise issues and submit patches. Please note
-that at the moment the LLVM project does not use either Github pull requests
-or Github issues.

README.md

@@ -1,110 +1,28 @@
-# The LLVM Compiler Infrastructure
+# Intel Project for LLVM\* technology
 
-This directory and its sub-directories contain source code for LLVM,
-a toolkit for the construction of highly optimized compilers,
-optimizers, and run-time environments.
+## Introduction
 
-The README briefly describes how to get started with building LLVM.
-For more information on how to contribute to the LLVM project, please
-take a look at the
-[Contributing to LLVM](https://llvm.org/docs/Contributing.html) guide.
+Intel staging area for llvm.org contribution.
+Home for Intel LLVM-based projects:
+ - oneAPI Data Parallel C++ compiler - see **sycl** branch. More information on
+   oneAPI and DPC++ is available at
+([https://www.oneapi.com/](https://www.oneapi.com/))
 
-## Getting Started with the LLVM System
+## License
+See [LICENSE.txt](sycl/LICENSE.TXT) for details.
 
-Taken from https://llvm.org/docs/GettingStarted.html.
+## Contributing
+See [CONTRIBUTING.md](CONTRIBUTING.md) for details.
 
-### Overview
+## Sub-projects Documentation
+ - oneAPI Data Parallel C++ compiler - See
+   [GetStartedGuide.md](sycl/doc/GetStartedGuide.md)
 
-Welcome to the LLVM project!
+## DPC++ extensions
 
-The LLVM project has multiple components. The core of the project is
-itself called "LLVM". This contains all of the tools, libraries, and header
-files needed to process intermediate representations and converts it into
-object files.  Tools include an assembler, disassembler, bitcode analyzer, and
-bitcode optimizer.  It also contains basic regression tests.
+DPC++ is an open, cross-architecture language built upon the ISO C++ and Khronos
+SYCL\* standards. DPC++ extends these standards with a number of extensions,
+which can be found in [sycl/doc/extensions](sycl/doc/extensions) directory.
 
-C-like languages use the [Clang](http://clang.llvm.org/) front end.  This
-component compiles C, C++, Objective C, and Objective C++ code into LLVM bitcode
--- and from there into object files, using LLVM.
+\*Other names and brands may be claimed as the property of others.
 
-Other components include:
-the [libc++ C++ standard library](https://libcxx.llvm.org),
-the [LLD linker](https://lld.llvm.org), and more.
-
-### Getting the Source Code and Building LLVM
-
-The LLVM Getting Started documentation may be out of date.  The [Clang
-Getting Started](http://clang.llvm.org/get_started.html) page might have more
-accurate information.
-
-This is an example work-flow and configuration to get and build the LLVM source:
-
-1. Checkout LLVM (including related sub-projects like Clang):
-
-     * ``git clone https://github.com/llvm/llvm-project.git``
-
-     * Or, on windows, ``git clone --config core.autocrlf=false
-    https://github.com/llvm/llvm-project.git``
-
-2. Configure and build LLVM and Clang:
-
-     * ``cd llvm-project``
-
-     * ``mkdir build``
-
-     * ``cd build``
-
-     * ``cmake -G <generator> [options] ../llvm``
-
-        Some common build system generators are:
-
-        * ``Ninja`` --- for generating [Ninja](https://ninja-build.org)
-          build files. Most llvm developers use Ninja.
-        * ``Unix Makefiles`` --- for generating make-compatible parallel makefiles.
-        * ``Visual Studio`` --- for generating Visual Studio projects and
-          solutions.
-        * ``Xcode`` --- for generating Xcode projects.
-
-        Some Common options:
-
-        * ``-DLLVM_ENABLE_PROJECTS='...'`` --- semicolon-separated list of the LLVM
-          sub-projects you'd like to additionally build. Can include any of: clang,
-          clang-tools-extra, libcxx, libcxxabi, libunwind, lldb, compiler-rt, lld,
-          polly, or debuginfo-tests.
-
-          For example, to build LLVM, Clang, libcxx, and libcxxabi, use
-          ``-DLLVM_ENABLE_PROJECTS="clang;libcxx;libcxxabi"``.
-
-        * ``-DCMAKE_INSTALL_PREFIX=directory`` --- Specify for *directory* the full
-          path name of where you want the LLVM tools and libraries to be installed
-          (default ``/usr/local``).
-
-        * ``-DCMAKE_BUILD_TYPE=type`` --- Valid options for *type* are Debug,
-          Release, RelWithDebInfo, and MinSizeRel. Default is Debug.
-
-        * ``-DLLVM_ENABLE_ASSERTIONS=On`` --- Compile with assertion checks enabled
-          (default is Yes for Debug builds, No for all other build types).
-
-      * ``cmake --build . [-- [options] <target>]`` or your build system specified above
-        directly.
-
-        * The default target (i.e. ``ninja`` or ``make``) will build all of LLVM.
-
-        * The ``check-all`` target (i.e. ``ninja check-all``) will run the
-          regression tests to ensure everything is in working order.
-
-        * CMake will generate targets for each tool and library, and most
-          LLVM sub-projects generate their own ``check-<project>`` target.
-
-        * Running a serial build will be **slow**.  To improve speed, try running a
-          parallel build.  That's done by default in Ninja; for ``make``, use the option
-          ``-j NNN``, where ``NNN`` is the number of parallel jobs, e.g. the number of
-          CPUs you have.
-
-      * For more information see [CMake](https://llvm.org/docs/CMake.html)
-
-Consult the
-[Getting Started with LLVM](https://llvm.org/docs/GettingStarted.html#getting-started-with-llvm)
-page for detailed information on configuring and compiling LLVM. You can visit
-[Directory Layout](https://llvm.org/docs/GettingStarted.html#directory-layout)
-to learn about the layout of the source code tree.