From bfaf6439ab7676cd8089889936b772b2be694dce Mon Sep 17 00:00:00 2001
From: agibsonccc <adam@konduit.ai>
Date: Tue, 9 Mar 2021 21:57:50 +0900
Subject: [PATCH] Update

---
 .../src/main/java/org/nd4j/ir/TensorNamespace.java   | 12 ++++++++++++
 .../nd4j-backend-impls/nd4j-native/pom.xml           |  1 +
 2 files changed, 13 insertions(+)

diff --git a/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/ir/TensorNamespace.java b/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/ir/TensorNamespace.java
index 434bda3a8..a0899ddbe 100644
--- a/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/ir/TensorNamespace.java
+++ b/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/ir/TensorNamespace.java
@@ -5411,12 +5411,14 @@ public final class TensorNamespace {
      * Serializations can either use one of the fields above, or use this
      * raw bytes field. The only exception is the string case, where one is
      * required to store the content in the repeated bytes string_data field.
+     *
      * When this raw_data field is used to store tensor value, elements MUST
      * be stored in as fixed-width, little-endian order.
      * Floating-point data types MUST be stored in IEEE 754 format.
      * Complex64 elements must be written as two consecutive FLOAT values, real component first.
      * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
      * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
+     *
      * Note: the advantage of specific field rather than the raw_data field is
      * that in some cases (e.g. int data), protobuf does a better packing via
      * variable length storage, and may lead to smaller binary footprint.
@@ -5655,6 +5657,7 @@ public final class TensorNamespace {
   /**
    * <pre>
    * Tensors
+   *
    * A serialized tensor value.
    * </pre>
    *
@@ -7010,12 +7013,14 @@ public final class TensorNamespace {
      * Serializations can either use one of the fields above, or use this
      * raw bytes field. The only exception is the string case, where one is
      * required to store the content in the repeated bytes string_data field.
+     *
      * When this raw_data field is used to store tensor value, elements MUST
      * be stored in as fixed-width, little-endian order.
      * Floating-point data types MUST be stored in IEEE 754 format.
      * Complex64 elements must be written as two consecutive FLOAT values, real component first.
      * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
      * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
+     *
      * Note: the advantage of specific field rather than the raw_data field is
      * that in some cases (e.g. int data), protobuf does a better packing via
      * variable length storage, and may lead to smaller binary footprint.
@@ -7766,6 +7771,7 @@ public final class TensorNamespace {
     /**
      * <pre>
      * Tensors
+     *
      * A serialized tensor value.
      * </pre>
      *
@@ -9080,12 +9086,14 @@ public final class TensorNamespace {
        * Serializations can either use one of the fields above, or use this
        * raw bytes field. The only exception is the string case, where one is
        * required to store the content in the repeated bytes string_data field.
+       *
        * When this raw_data field is used to store tensor value, elements MUST
        * be stored in as fixed-width, little-endian order.
        * Floating-point data types MUST be stored in IEEE 754 format.
        * Complex64 elements must be written as two consecutive FLOAT values, real component first.
        * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
        * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
+       *
        * Note: the advantage of specific field rather than the raw_data field is
        * that in some cases (e.g. int data), protobuf does a better packing via
        * variable length storage, and may lead to smaller binary footprint.
@@ -9102,12 +9110,14 @@ public final class TensorNamespace {
        * Serializations can either use one of the fields above, or use this
        * raw bytes field. The only exception is the string case, where one is
        * required to store the content in the repeated bytes string_data field.
+       *
        * When this raw_data field is used to store tensor value, elements MUST
        * be stored in as fixed-width, little-endian order.
        * Floating-point data types MUST be stored in IEEE 754 format.
        * Complex64 elements must be written as two consecutive FLOAT values, real component first.
        * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
        * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
+       *
        * Note: the advantage of specific field rather than the raw_data field is
        * that in some cases (e.g. int data), protobuf does a better packing via
        * variable length storage, and may lead to smaller binary footprint.
@@ -9130,12 +9140,14 @@ public final class TensorNamespace {
        * Serializations can either use one of the fields above, or use this
        * raw bytes field. The only exception is the string case, where one is
        * required to store the content in the repeated bytes string_data field.
+       *
        * When this raw_data field is used to store tensor value, elements MUST
        * be stored in as fixed-width, little-endian order.
        * Floating-point data types MUST be stored in IEEE 754 format.
        * Complex64 elements must be written as two consecutive FLOAT values, real component first.
        * Complex128 elements must be written as two consecutive DOUBLE values, real component first.
        * Boolean type MUST be written one byte per tensor element (00000001 for true, 00000000 for false).
+       *
        * Note: the advantage of specific field rather than the raw_data field is
        * that in some cases (e.g. int data), protobuf does a better packing via
        * variable length storage, and may lead to smaller binary footprint.
diff --git a/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-native/pom.xml b/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-native/pom.xml
index 420a620b0..f237480b2 100644
--- a/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-native/pom.xml
+++ b/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-native/pom.xml
@@ -219,6 +219,7 @@
                             <classOrPackageName>org.nd4j.nativeblas.Nd4jCpu</classOrPackageName>
                             <copyLibs>true</copyLibs>
                             <configDirectory>${project.build.directory}/classes/META-INF/native-image/${javacpp.platform}${javacpp.platform.extension}/</configDirectory>
+                            <outputDirectory>${project.build.directory}/classes/org/nd4j/nativeblas/${javacpp.platform}</outputDirectory>
                         </configuration>
                     </execution>
                 </executions>