Merge pull request eclipse-omr#7541 from 0xdaryl/eclipseomr

Update Eclipse OMR GitHub links to new eclipse-omr organization

CONTRIBUTING.md

@@ -37,7 +37,7 @@ This project uses GitHub Issues to track ongoing development, discuss project
 plans, and keep track of bugs.  Be sure to search for existing issues before
 you create another one.
 
-Visit [our Issues page on GitHub to search and submit](https://github.com/eclipse/omr/issues)
+Visit [our Issues page on GitHub to search and submit](https://github.com/eclipse-omr/omr/issues)
 
 ### Labelling
 
@@ -47,62 +47,62 @@ may have multiple labels, as many as needed to provide adequate categorization.
 
 A subset of the labels are documented below.
 
-* [**`good first issue`**](https://github.com/eclipse/omr/labels/good%20first%20issue) generally
+* [**`good first issue`**](https://github.com/eclipse-omr/omr/labels/good%20first%20issue) generally
   refers to a task that would be suitable for someone new to the project with
   little experience with either the technology or even open-source projects and
   processes. They are intended for anyone who wants to gently get their feet
   wet on building, testing, or familiarizing themselves with part of the code
   base.
 
-* [**`bug`**](https://github.com/eclipse/omr/labels/bug) issues are functional
+* [**`bug`**](https://github.com/eclipse-omr/omr/labels/bug) issues are functional
   problems, errors or unexpected behaviour.
 
-* [**`build/configure`**](https://github.com/eclipse/omr/labels/build%20%2F%20configure)
+* [**`build/configure`**](https://github.com/eclipse-omr/omr/labels/build%20%2F%20configure)
   labels are used to describe issues with the build and configure system (e.g.,
   makefiles, autotools configure).
 
-* [**`ci`**](https://github.com/eclipse/omr/labels/ci) labels are used for
+* [**`ci`**](https://github.com/eclipse-omr/omr/labels/ci) labels are used for
   issues and enhancements with the continuous integration system for pull
   request testing (e.g., Jenkins, Azure, etc.)
 
-* [**`cmake`**](https://github.com/eclipse/omr/labels/cmake) labels are similar
+* [**`cmake`**](https://github.com/eclipse-omr/omr/labels/cmake) labels are similar
   to build/configure but they apply specifically to the CMake configuration.
 
-* [**`compiler arch review`**](https://github.com/eclipse/omr/labels/compiler%20arch%20review)
+* [**`compiler arch review`**](https://github.com/eclipse-omr/omr/labels/compiler%20arch%20review)
   labels are used to indicate a review of this issue or pull request at the
-  [OMR Compiler Architecture meeting](https://github.com/eclipse/omr/issues/2316)
+  [OMR Compiler Architecture meeting](https://github.com/eclipse-omr/omr/issues/2316)
   is requested prior to committing.
 
-* [**`documentation`**](https://github.com/eclipse/omr/labels/documentation)
+* [**`documentation`**](https://github.com/eclipse-omr/omr/labels/documentation)
   labels are used for issues or enhancements to the documentation (either in
   the source code itself or stand-alone documentation files).
 
-* [**`epic`**](https://github.com/eclipse/omr/labels/epic) issues are used to
+* [**`epic`**](https://github.com/eclipse-omr/omr/labels/epic) issues are used to
   group together related issues and to track larger goals in the project across
   issues.
 
-* [**`GSoC Project`**](https://github.com/eclipse/omr/labels/GSoC%20project)
+* [**`GSoC Project`**](https://github.com/eclipse-omr/omr/labels/GSoC%20project)
   labels are for potential ideas for Google Summer Of Code projects.
 
-* [**`help wanted`**](https://github.com/eclipse/omr/labels/help%20wanted)
+* [**`help wanted`**](https://github.com/eclipse-omr/omr/labels/help%20wanted)
   issues have value to the project but no immediate human resources to
   undertake it. Those that are looking to complete a task that someone isn't
   already working on can consider these.
 
-* [**`license`**](https://github.com/eclipse/omr/labels/license) labels are
+* [**`license`**](https://github.com/eclipse-omr/omr/labels/license) labels are
   used to annotate issues concerning the source code license.
 
-* [**`meeting`**](https://github.com/eclipse/omr/labels/meeting) labels are
+* [**`meeting`**](https://github.com/eclipse-omr/omr/labels/meeting) labels are
   used to annotate issues pertaining to project meeting agendas or minutes.
 
-* [**`toolchain bug`**](https://github.com/eclipse/omr/labels/toolchain%20bug)
+* [**`toolchain bug`**](https://github.com/eclipse-omr/omr/labels/toolchain%20bug)
   labels are used to document issues or pull requests that describe or implement
   a workaround to a bug in the development toolchain (such as the compiler) used
   to build OMR.  Toolchain workarounds should be temporary in nature, and the
   intention of this label is to make such workarounds easy to discover in the
   future lest they be lost in the code.
 
-* [**`tooling`**](https://github.com/eclipse/omr/labels/tooling) labels are for
+* [**`tooling`**](https://github.com/eclipse-omr/omr/labels/tooling) labels are for
   issues concerning support tooling needed to support any of the code or
   processes within the project.
 
@@ -111,39 +111,39 @@ Eclipse OMR technology component they affect.  For instance,
 
 | Label | Component | Principal Directories |
 | :---- | :---- | :---- |
-[**`comp:compiler`**](https://github.com/eclipse/omr/labels/comp%3Acompiler) | Compiler | `compiler`
-[**`comp:core`**](https://github.com/eclipse/omr/labels/comp%3Acore) | Core OMR functionality | `include_code`, `omr`
-[**`comp:diagnostic`**](https://github.com/eclipse/omr/labels/comp%3Adiagnostic) | Diagnostic services | `ddr`
-[**`comp:doc`**](https://github.com/eclipse/omr/labels/comp%3Adoc) | OMR documentation | `doc`
-[**`comp:gc`**](https://github.com/eclipse/omr/labels/comp%3Agc) | Garbage collector | `gc`
-[**`comp:glue`**](https://github.com/eclipse/omr/labels/comp%3Aglue) | Glue code | `glue`
-[**`comp:jitbuilder`**](https://github.com/eclipse/omr/labels/comp%3Ajitbuilder) | JitBuilder | `jitbuilder`
-[**`comp:port`**](https://github.com/eclipse/omr/labels/comp%3Aport) | Port library | `port`
-[**`comp:test`**](https://github.com/eclipse/omr/labels/comp%3Atest) | Unit tests and testing framework | `fvtest`
-[**`comp:thread`**](https://github.com/eclipse/omr/labels/comp%3Athread) | Thread library | `thread`
-[**`comp:tril`**](https://github.com/eclipse/omr/labels/comp%3Atril) | Tril infrastructure and tests | `fvtest/tril`
-[**`comp:utilities`**](https://github.com/eclipse/omr/labels/comp%3Autil) | OMR utilities | `util`
+[**`comp:compiler`**](https://github.com/eclipse-omr/omr/labels/comp%3Acompiler) | Compiler | `compiler`
+[**`comp:core`**](https://github.com/eclipse-omr/omr/labels/comp%3Acore) | Core OMR functionality | `include_code`, `omr`
+[**`comp:diagnostic`**](https://github.com/eclipse-omr/omr/labels/comp%3Adiagnostic) | Diagnostic services | `ddr`
+[**`comp:doc`**](https://github.com/eclipse-omr/omr/labels/comp%3Adoc) | OMR documentation | `doc`
+[**`comp:gc`**](https://github.com/eclipse-omr/omr/labels/comp%3Agc) | Garbage collector | `gc`
+[**`comp:glue`**](https://github.com/eclipse-omr/omr/labels/comp%3Aglue) | Glue code | `glue`
+[**`comp:jitbuilder`**](https://github.com/eclipse-omr/omr/labels/comp%3Ajitbuilder) | JitBuilder | `jitbuilder`
+[**`comp:port`**](https://github.com/eclipse-omr/omr/labels/comp%3Aport) | Port library | `port`
+[**`comp:test`**](https://github.com/eclipse-omr/omr/labels/comp%3Atest) | Unit tests and testing framework | `fvtest`
+[**`comp:thread`**](https://github.com/eclipse-omr/omr/labels/comp%3Athread) | Thread library | `thread`
+[**`comp:tril`**](https://github.com/eclipse-omr/omr/labels/comp%3Atril) | Tril infrastructure and tests | `fvtest/tril`
+[**`comp:utilities`**](https://github.com/eclipse-omr/omr/labels/comp%3Autil) | OMR utilities | `util`
 
 Further classification by processor architecture, operating system, and bitness
 can be achieved with the following labels:
 
-* [**`arch:aarch32`**](https://github.com/eclipse/omr/labels/arch%3Aaarch32)
-* [**`arch:aarch64`**](https://github.com/eclipse/omr/labels/arch%3Aaarch64)
-* [**`arch:power`**](https://github.com/eclipse/omr/labels/arch%3Apower)
-* [**`arch:riscv`**](https://github.com/eclipse/omr/labels/arch%3Ariscv)
-* [**`arch:x86`**](https://github.com/eclipse/omr/labels/arch%3Ax86)
-* [**`arch:z`**](https://github.com/eclipse/omr/labels/arch%3Az)
+* [**`arch:aarch32`**](https://github.com/eclipse-omr/omr/labels/arch%3Aaarch32)
+* [**`arch:aarch64`**](https://github.com/eclipse-omr/omr/labels/arch%3Aaarch64)
+* [**`arch:power`**](https://github.com/eclipse-omr/omr/labels/arch%3Apower)
+* [**`arch:riscv`**](https://github.com/eclipse-omr/omr/labels/arch%3Ariscv)
+* [**`arch:x86`**](https://github.com/eclipse-omr/omr/labels/arch%3Ax86)
+* [**`arch:z`**](https://github.com/eclipse-omr/omr/labels/arch%3Az)
 <br/>
 
-* [**`os:aix`**](https://github.com/eclipse/omr/labels/os%3Aaix)
-* [**`os:linux`**](https://github.com/eclipse/omr/labels/os%3Alinux)
-* [**`os:macos`**](https://github.com/eclipse/omr/labels/os%3Amacos)
-* [**`os:windows`**](https://github.com/eclipse/omr/labels/os%3Awindows)
-* [**`os:zos`**](https://github.com/eclipse/omr/labels/os%3Azos)
+* [**`os:aix`**](https://github.com/eclipse-omr/omr/labels/os%3Aaix)
+* [**`os:linux`**](https://github.com/eclipse-omr/omr/labels/os%3Alinux)
+* [**`os:macos`**](https://github.com/eclipse-omr/omr/labels/os%3Amacos)
+* [**`os:windows`**](https://github.com/eclipse-omr/omr/labels/os%3Awindows)
+* [**`os:zos`**](https://github.com/eclipse-omr/omr/labels/os%3Azos)
 <br/>
 
-* [**`bits:32`**](https://github.com/eclipse/omr/labels/bits%3A32)
-* [**`bits:64`**](https://github.com/eclipse/omr/labels/bits%3A64)
+* [**`bits:32`**](https://github.com/eclipse-omr/omr/labels/bits%3A32)
+* [**`bits:64`**](https://github.com/eclipse-omr/omr/labels/bits%3A64)
 
 ## Submitting a contribution
 
@@ -189,7 +189,7 @@ Following these guidelines will help us to merge your pull requests smoothly:
    or, in the opinion of a committer,
    a fundamental element of compiler infrastructure, a committer will request that this
    pull request be presented at an upcoming
-   [OMR Compiler Architecture meeting](https://github.com/eclipse/omr/issues/2316)
+   [OMR Compiler Architecture meeting](https://github.com/eclipse-omr/omr/issues/2316)
    to invite community discussion prior to merging.  Issues of the same nature may
    also be asked to be discussed before the same architecture meeting prior to
    producing a pull request.

NOTICE.md

@@ -179,7 +179,7 @@ and such source code may be obtained at http://www.eclipse.org.
 ## Source Code
 This project maintains the following source code repository:
 
-https://github.com/eclipse/omr.git
+https://github.com/eclipse-omr/omr.git
 
 ## Third-party Content
 

README.md

@@ -115,7 +115,7 @@ We operate under the [Eclipse Code of Conduct][coc] to promote fairness, opennes
 * Join the Eclipse OMR developer community [mailing list](https://accounts.eclipse.org/mailing-list/omr-dev).
   The community primarily uses this list for project announcements and administrative
   discussions amongst committers.  Questions are welcome here as well.
-* Ask a question or start a discussion via a [GitHub issue](https://github.com/eclipse/omr/issues).
+* Ask a question or start a discussion via a [GitHub issue](https://github.com/eclipse-omr/omr/issues).
 
 Contributing
 ============
@@ -124,7 +124,7 @@ If you would like to contribute to OMR, check out the [contributing guide][contr
 We also have curated a set of [good first issues][beg] for newcomers to tackle.
 
 [contrib]: CONTRIBUTING.md
-[beg]: https://github.com/eclipse/omr/issues?q=is%3Aopen+is%3Aissue+label%3A%22good%20first%20issue%22
+[beg]: https://github.com/eclipse-omr/omr/issues?q=is%3Aopen+is%3Aissue+label%3A%22good%20first%20issue%22
 
 How Do I Use it?
 ================

buildenv/jenkins/README.md

@@ -32,14 +32,14 @@ From the [Builds view](https://ci.eclipse.org/omr/view/Builds/), on the left men
 
 1. General
 	1. Discard old builds -> Max # of builds to keep: `25`
-	1. GitHub project -> Project url: `https://github.com/eclipse/omr/`
+	1. GitHub project -> Project url: `https://github.com/eclipse-omr/omr/`
 	1. This project is parameterized -> Choice Parameter -> Name: `BUILDSPEC` -> Choices: `<SPEC>` (The matching SPEC name)
 1. Build Triggers
 	1. Generic Webhook Trigger (defaults should be fine)
 1. Pipeline
 	1. Definition: Pipeline script from SCM
 	1. SCM: Git
-		1. Repositories -> Repository URL: `https://github.com/eclipse/omr.git`
+		1. Repositories -> Repository URL: `https://github.com/eclipse-omr/omr.git`
 		1. Branches to build: `/refs/heads/master`
 	1. Script Path: `buildenv/jenkins/omrbuild.groovy`
 	1. Lightweight checkout: `true`
@@ -49,7 +49,7 @@ From the [Builds view](https://ci.eclipse.org/omr/view/Builds/), on the left men
 From the [Pull Requests view](https://ci.eclipse.org/omr/view/Pull%20Requests/), on the left menu select [New Item](https://ci.eclipse.org/omr/view/Pull%20Requests/newJob). Name the job based on the following convention `PullRequest-<SPEC>` (eg. `PullRequest-linux_x86-64`. See [omrbuild.groovy](./omrbuild.groovy) for full `SPEC` list). Select `Pipeline` as the job type and then click `OK`. Setup the following in the job config.
 
 1. General
-	1. GitHub project -> Project url: `https://github.com/eclipse/omr/`
+	1. GitHub project -> Project url: `https://github.com/eclipse-omr/omr/`
 	1. This project is parameterized -> Choice Parameter -> Name: `BUILDSPEC` -> Choices: `<SPEC>` (The matching SPEC name)
 1. Build Triggers
 	1. GitHub Pull Request Builder
@@ -64,7 +64,7 @@ From the [Pull Requests view](https://ci.eclipse.org/omr/view/Pull%20Requests/),
 	1. Definition: Pipeline script from SCM
 	1. SCM: Git
 		1. Repositories
-			1. Repository URL: `https://github.com/eclipse/omr.git`
+			1. Repository URL: `https://github.com/eclipse-omr/omr.git`
 			1. Advanced -> Refspec: `+refs/pull/${ghprbPullId}/merge:refs/remotes/origin/pr/${ghprbPullId}/merge`
 		1. Branches to build: `${sha1}`
 		1. Additional Behaviours
@@ -101,7 +101,7 @@ Configuring Jenkins to pull the pipeline scripts from Git on z/OS is a non-trivi
 Fetching changes from the remote Git repository
 Cleaning workspace
 ERROR: Error fetching remote repo 'origin'
-hudson.plugins.git.GitException: Failed to fetch from https://github.com/eclipse/omr.git
+hudson.plugins.git.GitException: Failed to fetch from https://github.com/eclipse-omr/omr.git
 	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:894)
 	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161)
 	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
@@ -114,7 +114,7 @@ hudson.plugins.git.GitException: Failed to fetch from https://github.com/eclipse
 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 	at java.lang.Thread.run(Thread.java:748)
-Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://github.com/eclipse/omr.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
+Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://github.com/eclipse-omr/omr.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
 stdout:
 stderr: fatal: Unable to find remote helper for 'https'
 ```

buildenv/jenkins/refRepoUpdater.groovy

@@ -55,7 +55,7 @@ def refresh() {
     dir("${HOME}/gitcache") {
         sh '''
             git init --bare
-            git config remote.omr.url https://github.com/eclipse/omr.git
+            git config remote.omr.url https://github.com/eclipse-omr/omr.git
             git config remote.omr.fetch +refs/heads/*:refs/remotes/omr/*
             git fetch omr
         '''

compiler/README.md

@@ -104,7 +104,7 @@ extensible class representation (see [*extensible classes*](../doc/compiler/exte
 At present, the use of the `TR` namespace for the public API is largely aspirational
 as much of the code appears as it did when it was first contributed.  The epic to
 track the work to migrate components of the OMR compiler public API to the `TR`
-namespace is issue [#3519](https://github.com/eclipse/omr/issues/3519).
+namespace is issue [#3519](https://github.com/eclipse-omr/omr/issues/3519).
 Throughout the current compiler code, you may encounter references that are in
 the global namespace but whose identifiers are prefixed simply with `TR_`.
 This is inconsistent with the namespace convention just described and they are

compiler/codegen/OMRRealRegister.hpp

@@ -72,16 +72,16 @@ class OMR_EXTENSIBLE RealRegister : public TR::Register
       } RegMask;
 
     // PseudoRegisters are the union of all hardware backed registers (ex. GPR0)
-    // and constructs such as TR::RealRegister::NoReg or TR::RealRegister::AssignAny. 
-    // These pseudo registers are used to assign register dependencies during the 
+    // and constructs such as TR::RealRegister::NoReg or TR::RealRegister::AssignAny.
+    // These pseudo registers are used to assign register dependencies during the
     // Register Allocation phase. The enum below is meant to hold all pseudo registers.
-    // However, to avoid compilation failures, we cannot include 
+    // However, to avoid compilation failures, we cannot include
     // codegen/RealRegisterEnum.hpp again. In order to include it twice, these two enums
     // must be scoped. However, not all of our minimum compiler toolchains support this
-    // feature yet (MSVC 2010). So we only include PseudoRegisterEnum below, and cast any 
-    // RegNum to RegDep when using it to set a register dependency. If MSVC 2010 support is 
+    // feature yet (MSVC 2010). So we only include PseudoRegisterEnum below, and cast any
+    // RegNum to RegDep when using it to set a register dependency. If MSVC 2010 support is
     // no longer required, then this can be cleaned up by using scoped enums instead. An issue
-    // to track this is open here: https://github.com/eclipse/omr/issues/2590 
+    // to track this is open here: https://github.com/eclipse-omr/omr/issues/2590
     typedef enum
        {
        #include "codegen/PseudoRegisterEnum.hpp"

compiler/optimizer/FieldPrivatizer.cpp

@@ -497,7 +497,7 @@ bool TR_FieldPrivatizer::containsEscapePoints(TR_Structure *structure, bool &con
          // privatized must be of the expected type in the loop, and that
          // ensures any conditional access in the original loop is handled
          // correctly.  This follow on work will be performed under OMR issue
-         // <https://github.com/eclipse/omr/issues/6199>
+         // <https://github.com/eclipse-omr/omr/issues/6199>
          //
          if (currentNode->exceptionsRaised()
              || currentNode->isTheVirtualGuardForAGuardedInlinedCall()

compiler/optimizer/RedundantAsyncCheckRemoval.cpp

@@ -1289,7 +1289,7 @@ void TR_RedundantAsyncCheckRemoval::getNearestAncestors(TR_StructureSubGraphNode
 
 void TR_RedundantAsyncCheckRemoval::markAncestors(TR_StructureSubGraphNode *node, TR_StructureSubGraphNode *entry)
    {
-   return;  // Disable it for performance. For more details, refer to https://github.com/eclipse/omr/pull/1138
+   return;  // Disable it for performance. For more details, refer to https://github.com/eclipse-omr/omr/pull/1138
 
    if (node == entry)
       return;

compiler/optimizer/ValuePropagationCommon.cpp

@@ -3961,7 +3961,7 @@ const char* transformedTargetName (TR::RecognizedMethod rm)
 #ifdef J9_PROJECT_SPECIFIC
 /**
  * Can be called from doDelayedTransformations when nodes may have been removed from the tree. Issue 6623
- * https://github.com/eclipse/omr/issues/6623
+ * https://github.com/eclipse-omr/omr/issues/6623
  */
 void OMR::ValuePropagation::transformObjectCloneCall(TR::TreeTop *callTree, OMR::ValuePropagation::ObjCloneInfo *cloneInfo)
    {
@@ -4069,7 +4069,7 @@ void OMR::ValuePropagation::transformObjectCloneCall(TR::TreeTop *callTree, OMR:
 
 /**
  * Can be called from doDelayedTransformations when nodes may have been removed from the tree. Issue 6623
- * https://github.com/eclipse/omr/issues/6623
+ * https://github.com/eclipse-omr/omr/issues/6623
  */
 void OMR::ValuePropagation::transformArrayCloneCall(TR::TreeTop *callTree, OMR::ValuePropagation::ArrayCloneInfo *cloneInfo)
    {

compiler/z/codegen/OMRCodeGenerator.cpp

@@ -290,7 +290,7 @@ OMR::Z::CodeGenerator::lowerTreeIfNeeded(
       TR::Node* index = NULL;
       TR::ILOpCodes addOp, subOp, constOp;
       // Need to track if lowered trees are internal pointers
-      // For context: https://github.com/eclipse/omr/issues/4929
+      // For context: https://github.com/eclipse-omr/omr/issues/4929
       bool isInternalPointer = false;
       TR::AutomaticSymbol *pinningArrayPointer = NULL;